Locutus_

Ahhh, Vaxman still up to his usual shenannigans :-)

The answer honestly feels a bit lacking, and evasive.

I've had exactly the same situation, ~2M MAU service with REDIS as the only persistence system, all data being JSON serialized Pydantic models. The storage overhead was just terrible and cost real money.

This would have been a super nice to have back then.

I wonder though how much sense it would make to get something like this mainlined into upstream Pydantic? as having this downstream would give many continuity and dependency lock concerns. And having it as part of the main library would significantly drive adoption rate.

How is the write support now-adays, is it production quality now?

I used Kaitai in a IoT project for building data ingress parsers and it was great. But not having write support was a bummer.

I honestly zoned out when I saw how many and what steps where required before just wget'ing a image file.

Sorry, nope.

Well....toml isn't that much more than .ini files slightly brough up in feature support.

Again not great for bigger documents.

This also seems a bit like AWS Chalice reinvented, which might be a good thing as AWS has silently abandoned it.

Great read, but I honestly had wished the author had split it into several separate articles.

I had this literally happen to me a couple of months ago.

Slacking off while waiting for some performance tests to run (Shoutout to Locust.io!) with my big 27" screen full of terminals for each runner, server logs etc.

...And then on my laptop screen I honestly was just slacking off and reading Reddit.

'VP Of Technology' comes over "I dont know what you are doing, but it's the most impressive thing I've seen in a while".

...Yes sir!

Provision a VPS/VM/Cloud instance/etc, install your dev tools on it and use it over mush.

And remember for things like looking up git commands or even a lot of your dependency documentation, you do not need a web browser. Git comes with manpages, many libraries will have docs in .md or whatever in them.

....Atreides Management?

The financing arm of a aristocratic line running a personality cult and who have a nepo baby on the cards contemplating a little bit of jyhad as his ticket out?

....I Do sometimes wonder who comes up with these names.

The thought someone went from no programming background, taking a company internal course and then writes a GPU emulation layer in the 90's is just absolutely mad.

Super impressive!

M68k has the advantage that it has a fairly typical memory model.

Alpha's memory model has problems with providing atomic access to single bytes, which i'd imagine in a kernel is a bit annoying :-)

And then there's just the social aspect, m68k was used in the Amiga/Atari/Mac/QL/x68k, so there is a whole generation of us m68k fans who are willing to keep it alive.

Alpha has it's fans (me included!), but it's not exactly the same. So in a way it's no surprise it's slowly bitrotting away.

The ghost of the Alpha's infamously weak memory model coming back to bite it's undead self.

Linux on AMD64 happened.