Readit NewsFor this reason I would strongly advise, in the spirit of https://wiki.postgresql.org/wiki/Don't_Do_This, that you Don't Do Materialized Views.
Sure, Differential/Timely Dataflow exist and they're very interesting; I have not gotten to build a database system with them and the systems that provide them in a usable format to end users (e.g. Materialize) are too non-boring for me to want to deploy in a production app.
I don't understand this part. We didn't use different sources of lead to make leaded gas and lead pipes, no?
I'm well aware of what's available out there as online content (it's no farther than a Google or youtube search).
Do you think what's out there as online content is what's truly possible if we had a million more Amiga enthusiasts?
That's my vision of what's to come in, say, 10-20 yrs. Imagine every Amiga game played and recorded by many (AI) users from start to finish. Every tactic explored, and cool strategies figured out. I for one would watch this.
Imagine vibe coding becoming more and more possible with 68k assembly. And having 1000x Amiga (AI) developers producing cool demo, intro and game material. New material. Novel and cutting edge material. At massive scale.
I believe this is the future we're headed. I for one am very excited about it.
----------
Re: A physical museum.
No, an Amiga or Commodore focus cannot be found anywhere in Silicon Valley or in United States. Even Computer History Museum (CHM) in Silicon Valley has very little Commodore content.
I live <1 mile away from the original Amiga offices in Los Gatos. It's a bit of shame that there's so little Amiga or Commodore in CHM.
Yes, you can have AI tools vibe code up "new" 68k assembly for old machines, but you're never going to see it find genuinely new techniques for pushing the limits of the hardware until you give it access to actual hardware. The demoscene pushes the limits so hard that emulators have to be updated after demos are published. That makes it prohibitively expensive and difficult to employ AI to do this work in the manner you describe.
Don't mistake productivity for progress. There is joy in solving hard problems yourself, especially when you're the one who chose the limitations... And remember to sit back and enjoy yourself once in a while.
Speaking of, here's a demo you can sit back and enjoy: https://youtu.be/3aJzSySfCZM
Cleetus McFarland ran a car on brake-clean which has really low octane rating so sure anything works if you care about nothing. https://youtu.be/0hYOgGYQ_c8
American big block naturally aspirated engines will be tuned for crap fuel, if you've got a modern efficient turbo engine you should buy premium fuel to not ruin your engine.
Editorialized: US "gas" is cheap crap
from https://en.m.wikipedia.org/wiki/Octane_rating
It just lets higher performance cars achieve higher compression ratios. I believe technically this means it has a little bit less raw combustion potential the higher the octane rating. But none of this actually matters in practice as long as you feed your car what it asks for.
Instead, they're just disappearing _all_* goo.gl short links. The overwhelming majority of which are benign links made by users who were promised a super stable URL link shortening service backed by the Google brand.
*edit: Not all, but nearly.
> All other [active] goo.gl links will be preserved and will continue to function as normal. To check if your link will be retained, visit the link today. If your link redirects you without a message, it will continue to work.
https://developers.googleblog.com/en/google-url-shortener-li...
> As a parent, I’m pleased that I’ve given her the tools to put herself through college hustling poker games, and then go work at a proprietary trading firm.
which is presumably written with the same sardonic intent as any other Matt Levine work.
Like making state machines easier than channels. (Rust is sort-of good at state machines compared to C++ but it has one huge issue because of the ownership model, which makes good SMs a little clumsy)
Or making it slightly inconvenient to do I/O buried in the middle of business logic.