In Europe, the numbers differ even more. Lighter weight cars typically 1.5-2 tons, a new London bus can be upto 18 tons when loaded - that's ~5-16 units of wear for the car to 104,976 units for the bus...

But this is all supposing we're optimising for road wear, which isn't really the point of a bus system.

To add to this list:

- Duplicate functions when you've asked for a slight change of functionality (eg. write_to_database and write_to_database_with_cache), never actually updating all the calls to the old function so you have a split codebase.

- On a similar vein, the backup code path of "else: do a stupid static default" instead of erroring, which would be much more helpful for debugging.

- Strong desires to follow architecture choices it was trained on, regardless of instruction. It might have been trained on some presumably high quality, large and enterprise-y codebases, but I'm just trying to write a short little throwaway program which doesn't need the complexity. KISS seems anathema to coding agents.

Fortnite: July 25, 2017 (Battle Royale mode launched September 26, 2017)

Apex Legends: February 4, 2019

Valorant: June 2, 2020

Overwatch: May 24, 2016

Call of Duty: 2003, Annual release

League of Legends: October 27, 2009

Dota 2: July 9, 2013

Roblox: 2006 (initially as DynaBlocks, rebranded to Roblox the same year)

Blame Claude 4 if any date is wrong...

You could pick some slightly less sci-fi measures like "number of trivially preventable deaths from diseases for which we have vaccines", for example.

I mean... that's what the title and context of the discussion thread is all about?

Simple accommodations can be made if needed and then there's no need to exclude people on old-fashioned prejudice.

Related to that, the Unix philosophy of simple tools that do one job and do it well, also applies here a bit. More typical workflow would be a utility to tarball something, then another utility to gzip it, then finally another to encrypt it. Leading to file extensions like .tar.gz.pgp, all from piping commands together.

As for versioning, I'm not entirely sure why your Debian and Ubuntu installs both claim version 6.00, but that's not typical. If this is for a personal machine, I might recommend switching to a rolling release distro like Arch or Manjaro, which at least give upto date packages on a consistent basis, tracking the upstream version. However, this does come with it's own set of maintenance issues and increased expectation of managing it all yourself.

My usual bugbear complaint about Linux (or rather OSS) versioning is that people are far too reluctant to declare v1.00 of their library. Leading to major useful libraries and programs being embedded in the ecosystem, but only reaching something like v0.2 or v0.68 and staying that way for years on end, which can be confusing for people just starting out in the Linux world. They are usually very stable and almost feature complete, but because they aren't finished to perfection according to the original design, people hold off on that final v1 declaration.

Think of it as if ChatGPT (or other models) didn't just have the embedded unstructured knowledge in their weights from learning, but also an extra DB on the side with specific structured knowledge that it can lookup on the fly.

Has saved us a number of times when having to deploy at a remote client with limited on-prem customisation for security reasons (ie. no to installing a big Postgres or other RDBMS solution).

Powerful tooling; all local to the environment and the data being worked on; SQL, so it's pretty close to a drop-in replacement compared to our old solution. Really great stuff and I was very happy to see the project gain the confidence to hit 1.0 a while back and now 1.1.

Congrats to everyone!

Those increased storage costs make the decoupled compute and the associated auto-scaling benefits almost irrelevant as far as the overall cost picture goes.

I may be in a position to open some of that up before it's lost.

Thankfully they also must've realised this was a stupid button and provide a 90-day cooldown period on deleted subscriptions... but why have the easy button in the first place?