sinpif

If the aim is to achieve a "flat" sound response, you could take it one step further and use a microphone to check how it sounds in a given space. Like Sonarworks SoundID. Some studio monitor speakers have this built in. Treat the room, position the speakers, put a microphone to the listening position and apply a (often wild) EQ curve until the response is flat (enough).

Because what I meant by that of course was power over money. You turn it on, put in the credit card info and let it rip, eh?

Wait a minute, so you (and your colleagues) deploy this thing, it tells you half the staff should go so the company can stay afloat. You GO?

I know it's a joke but...

Power is what makes them what they are, not knowledge or skills or empathy.

If you don't like what this thing tells you to do, you just won't. It's not going to fire you. Therefore it's not going to steer the company away from disaster, or towards something good. It will be just a talking box.

John Siracusa, for sure. He's not getting an EV. He's getting this.

Had a similar thought today - maybe we could finally get Linux drivers for more HW...

Migration churn adds up over the years but overall it's nice and site-specific code is usually so small it fits very nice in LLM context.. easy to work with.

Not hardcore enough.

On the other hand: you don't need glue when you 3d print the whole thing. Keep it simple with a single language.

It also means they must have started with the assumption that they were the best home for every type of studio, which, when you say it out loud, sounds very stupid. Second, how can a studio be "independent" anymore when owned by MS? Doesn't make sense. It's all just corpo speak for "we fucked up but we're still getting paid to fire you".

I'd be interested in 1) what makes a package "critical" 2) how do you take ownership if the original author is unreachable or not cooperating? Are you going to fork it and somehow make everyone switch to your fork, even on older LTS systems?

Yeah, well, that's just, like...

Time to optimize your software stack. Stop using slow interpreted languages & bloated "scaling" setups in favour of tightly integrated natively compiled systems.

Where else could they store their serialized PHP data structures? (just kidding)

Oh well, AI bros ruined it. I'm actually glad in some twisted way, because if more projects follow suit and close their development, it will again become an actual badge of honor to get on those teams. Having contributed to such projects will mean something.

No. From your tone it sounds like it's probably not as easy as you'd like. I don't really have a response to that. System customization is not something I'm interested in.

Does a 4 word prompt count? If so then I'm joining the effort right now.

I'm all for integration of system services if it helps bring a more cohesive OS. Interchangeability is a nice thing when building a system but I don't need it as a user.

More like "Designed by Apple in California, then copied as a cheap knockoff, never to be touched by a serious designer again".

It is vibe coded with a very good prompt.

Maybe it should say "designed in Zig" because most of the work & thinking was done using that language. The rewrite has no such history.

I'm aware of those platforms and have used them in the past. The tendency towards libraries is what bugs me. My preference would be a "Djan-go" framework, with the models, migrations, auto-admin, views, routing, caching, templates, all rolled into one cohesive framework that works out of the box. I don't want to make choices. I want to install it and start working.

I'm still on the lookout for a comprehensive Django-like web framework for go. That would be an instant hit for me.

Similar situation with Apple's Xcode Cloud.

Taken to an extreme, what's stopping us from going back to C? The security issues will be found and resolved, performance will be great and it will compile on all platforms that ever existed.

Maybe it's just because I'm more of a SwiftUI person, but in the example on the homepage, the event == 'Cancel' condition seems like a strange and fragile way to check if a certain button was pressed...

How many UI migrations has Photoshop gone through over the years?

The final three paragraphs really struck a chord with me. Nicely said. Thanks!

Agreed, this approach feels like folks at Microsoft still feel they have enough karma to burn. It's way past that.