kmacleod

The mass of unneeded cars will be at the periphery. The equivalent of taxi stands will have needed cars within reasonable distance.

Back in the PRT days we simply planned to store 1-2 vehicles in-station waiting for walk-ups, and if a drop-off comes in they just push out the waiting vehicles and they circle back. The efficiency remains crazy supportive of that model vs empty buses or trains.

I work in software deployment for large orgs. I use this technique to optimize. "How can I provision or deploy this with one package install, and launch instance." Typically take multi-page or multi-step deployments down to fully automated.

I discovered this recently as I tested an old idea I had to allow a dynamic language to use a C++-like vtable instead of an inline cache (like Objective-C or JavaScript does). It turns out modern CPUs predict an inline cache hit/miss result much better than always incurring the cost of the fetch in a vtable lookup.

Atom kinda does. Atom is a paged format, so a publisher can publish their entire history in their Atom feed and only the most recent page gets redownloaded to see new entries as they are added.

Small nit, as a legal vehicle, the constitution allows itself to be entirely replaced.

If your editor has a wiki mode (like Emacs' org mode) then maybe nothing. If not, then Obsidian is your browser and your editor is your editor. For example, git syncing between Android and desktop isn't working well for me, so I edit directly in github UI and browse in Obsidian. The fact that Obsidian works exactly like that is one of the biggest benefits of Obsidian.

I've created and managed five distributions for two companies. I've found RPM to have slightly easier tooling across the whole stack, from developers building individual RPMs/specs up through building and managing 1000s of RPMs across multiple releases. The Fedora build model makes a great reference and source of tools for spinning your own distributions.

My Tesla FSD v14 will wait for any pedestrian stepping or approaching stepping into the road.

As a district, aren't you also able to work with Google to enable research and educate modes in addition to the "give me the answer" modes?

The technologies I’d like to see tracked include post-scarcity economics, resource-based distribution, and needs-based allocation systems.

Not sure where you're getting your information from.

My FSD (v13.2) has driven unmapped roads, including gravel roads, hills, narrow roads, and switchbacks, in the backwoods of Tennessee. From watching the display, it clearly identifies the road features and navigates them.

The Free Software Foundation (FSF), as the author of the GPL and LGPL licenses, maintains that any software running in the same process space qualifies as "linked" under the terms of these licenses. This includes dynamic and static linking, plug-ins, loadable modules, and, in some cases, even interpreted code.

However, some developers who use GPL licenses interpret these requirements differently and permit certain uses that the FSF does not. A notable example is the Linux kernel, which allows proprietary kernel modules under specific conditions.

For proprietary software authors, the best-case scenario is having to convince a court that the license they accepted, by redistributing GPL-licensed software, permits linking without the obligation to disclose their own source code, as otherwise required by the license.