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.
You can implement it with templates and people do things like this often. In modern C++, it's even pretty easy to make this type of trick support `constexpr`.
Going back to the technical implementation part, depending on the C++ version, and being able to understand the target at compile time, no need to do it manually and hacky.
There is enough support in constexpr, consteval, concepts, and now compile time reflection, to do it automatically, assuming the dispatch target can be resolved at compile time.
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.
Possibly very much like Usenet. In the 80s there was a distributed "Slack-like" (for lack of a better description) distributed BBS network called Citadel (still some sites around now Internet based).
I wrote a UUCP clone and UseNet gateway for CitNet and made it available through a Citadel BBS "newsreader" to callers.
"uccico unidel ken bitsko macleod" still brings up some results[0]
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 experience over the years with a few Linux distributions is that rpm based distros always seem to give me more problems with dependencies and always seems harder to fix. These days I much prefer deb based distributions, mainly Ubuntu as I like their trade-off between stability and newer versions though I'm not a fan of snap packages.
I believe that's what they are doing. I was removed from the committee after sharing the studies I found so I'm just pushing the buttons they tell me to push at this point.
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.
reply