redwall_hp

Da Vinci Resolve recommends 16GB for video editing and 32GB if you're doing Fusion compositions. Basic video stuff.

Blender definitely benefits from more RAM. The M-series Macs are good for doing renders. If you're a hobbyist or independent creator, you're more likely to be rendering on your laptop than having a fancy render farm. (That's exactly how the movie Flow was done.)

Musicians know software instruments can eat into RAM, and streaming things like sample-based instruments off of disc is non viable for real time audio. Real world use can have very large numbers of tracks with many software instruments and VST chains. Ableton is a minimum of 8GB for the DAW, and things like Kontakt will multiply that fast.

And people usually have Chrome, chat apps and other things open while they work.

But you can also get a "Pro" phone in safety orange for some reason. It's not even consistent.

Companies should also be legally barred from hiring for three years if they engage in layoffs. Mergers should also be off the table for the same period.

It's deleterious to the economy. As the recent Microsoft game studio apocalypse shows, mergers are also extremely deleterious. It would be better to have a dozen game studios employing people and competing rather than one shit company cutting expenses and reducing products going to market.

Its spiritual successor is the crown on the Apple Watch. I never swipe to scroll on the watch. It's way more fluid (and you get neat haptics) to twist the crown.

It's going to be great, between this and the Adobe totally-not-using-any-decompiled-code-wink clones: people are going to get sued into the ground and LLM code is going to become radioactive to corporate lawyers. Especially when they find out that they also routinely spit out GPL code verbatim.

It's going to be hilarious.

"We've always been at war with Eurasia." - Republicans

I'm fairly pessimistic about LLMs, but I do find they're a good research tool. If I can accelerate finding answers amid the slurry of Confluence, Slack, assorted other intranet places and the web, I can get back to thinking about the design and programming.

I have a user CLAUDE.md that tells it not to presume to modify any files, and a bunch of internal MCPs for our logging and monitoring tools, documents, git repositories and such, and I've been dabbling with writing skill files so it can access some other internal things.

So I can basically say "this thing isn't working because x, and it's probably related to y not having z" and it'll go off and find info buried in the corporate abyss.

Then other people yeet wildly awful LLM generated PRs over the fence and I lose my sanity from basically having fight a constant battle against a slow rot of software quality that will bite us later.

Fred Brooks wrote a whole ass book based on that premise, and people still haven't learned the lesson half a century later.

Sure, it did some meaningful things:

* Higher load on senior engineers who are about to burn out hard from fighting an endless battle against unreviewed slop people keep trying to yeet into production

* Less junior hiring and suppressed wages

* Culture of uncertainty and fear

* Computers are really expensive now

* Some people now live with diesel generators and gas turbines making their neighborhood hazardous to their health

And the LLMs exist to further those problems. People can't afford houses? Well, now they won't be able to own computers either. That's a feature, not a side effect. Once the K-shaped economy progresses enough, you won't even be allowed to use the LLMs. They'll exist only to be a tool for the new feudal class who owns you.

Unless you destroy their wealth now.