That's where most of their budget comes from I think.

Is it not? Designers keep designing but everyone says they prefer Windows XP.

I've heard this POV before. Personally, I'm glad there's a DAW option with a no-frills approach to UI. I don't want a flashy or "inspiring" UI. Everything should be within arms' reach and do what it says on the tin. All the creativity happens in the audio domain. I prefer to use my ears.

Some people like Reason for instance, but I find that its UI innovations just get in my way.

On HN?! Inconceivable!

Perhaps to facilitate a dynamically generated schema.

Browser updates? Most of them.

The latest version of Android Google Chrome requires Android 10. But to keep getting updates you need Android 11.

Running a browser on an OS that doesn’t get security updates doesn’t sound like a winning combination.

More winning than updating neither

Not all meetings are status reports. There is also the working meeting where people figure stuff out.

Maybe some day we'll collectively figure it out. I'm confused how people are getting so much success out of it. That hasn't been my experience. I'm not sure what I'm doing wrong.

Try using the brainstorming and execute plan loops with the superpowers plugin in Claude Code. It encapsulates the spec driven development process fairly well.

Ok, done.

I thought about it. Still seems kind of pointless.

That doesn't seem any better than typing "rhythm guitar". In fact, it seems worse and with extra steps. Sometimes the thing making the sound is not pictured. This thing is going to make me scrub through the video until the bass player is in frame instead of just typing "bass guitar". Then it will burn some power inferring that the thing I clicked on was a bass.

To be fair, it's one of 3 ways to prompt