If these ailments are completely abstract in both their scope and personal effects, it's easier to be convinced by emotional manipulators. Especially if you're part of the... let's say low empathy population.

You should really ponder the sanity of asking if a channel called “not just bikes” is a bike maximalist.

Not really. We know it’s not as much of a natural force as some would like it to be because there are places where the lobbies lost, and while cars are common and widespread they’re nowhere near as dominant as they are in, say, the USA.

NJB’s next video (currently available on nebula) is about exactly that, Amsterdam’s (/ De Pijp’s) resistance to cars and car lobbying.

Yes’n’t: https://github.com/apple/container/blob/main/docs/technical-...

> container relies on the new features and enhancements present in macOS 26. You can run container on macOS 15, but you will need to be aware of some user experience and functional limitations. There is no plan to address issues found with macOS 15 that cannot be reproduced on macOS 26.

The issues are around networking.

At the motor level it should be the same, in propulsion you’re converting current to torque and in regen you’re converting torque to current, with the same hardware. The high voltage wiring is the same and will set the same limit on current regardless of direction.

I believe bidirectional inverters are generally symmetrical as well, so that should not be a factor.

Which I reckon leaves two factors:

1. Battery C rates, afaik pretty much all chemistries have a higher discharge rate than charge rate, especially when trying to maintain them for a long time, so by that account regen power would at most be the same as propulsion (if the entire power train is sized for the battery’s charging rate).

2. Artificial limitations, obviously you could always artificially under-prop, though that seems unlikely outside of niche applications.

tldr: I don’t think so, except on a technicality (that you can artificially hobble propulsion).

Are you sure about that? A few comments above a commenter states that they don’t run inits at all (because they ran alpine), multiple people replied that it works fine if you give it an image with an init, and they acknowledged their error.

An unspecialised popcnt is half the dozen instructions, for specialised versions it’s 4 implementations ranging from half a dozen to two dozen bytes.

It does not actually make it impossible to query the wrong table it just tells you quickly when you’ve done so.

It would also logically be sent to “every” process on the machine, with the subsystem probably having a heuristic to skip processes which were already signaled and have not had significant memory increases since. The goal of an early warning is to cooperatively release memory (and maybe abort memory intensive computations), the kernel already kills processes “at random”, it does not need a second way to do that.

However it requires additional hardware to recognize patterns which benefit from prefetching, and every time the CPU prefetches data which ends up not being used it has both burned energy and memory bandwidth, and evicted data from the cache which might be needed (cache pollution).

cgroups v1 has a pretty nice API but it requires root. V2 does not require root but it’s a lot coarser and not as simple or reliable: https://unix.stackexchange.com/questions/753929/receive-a-me...

> You can be pedantic and say they aren't technically threads but that doesn't really matter from a programming perspective.

They are technically threads: they are independently scheduled, concurrent units of execution sharing an address space. They're just not OS (or kernel) threads. Hell, technically userspace threads (generally cooperatively scheduled) are the original, they predate kernel threads by a decade or two.

> even if you keep all your fields private, the constructor is still, inherently, public.

ShippingOptions and the literals / enums are part of the public API, so the user would just be writing

    ShippingOptions(Carrier.USPS, Conveyance.Air)

Dataclasses do have a `kw_only` option, but I'm not sure how well underscore prefixes would be understood as private parameters / a private ctor, whereas wrapping a clearly "private" type should be clear to everybody.

Glyph is not entirely correct on the "any class" bit as you can always break the default init path:

  class ShippingOptions:
      _ship: Literal["fast", "normal", "slow"]
      __init__ = None


  def shipFast() -> ShippingOptions:
      opts = object.__new__(ShippingOptions)
      opts._ship = "fast"
      return opts