Isn’t this flawed anyway? If an application communicates with Claude Code over ACP (like Zed), it works fine?
Instead of using SDKs, this will just shift the third party clients to use ACP to get around it - Claude Code is still under the hood but you’re using a different interface.
This all seems pretty idiotic on their part - I know why they’re trying it but it won’t work. There will always be someone working around it.
Well they don’t have to wait for Rust in the way they said - they’ve already been forked by Turso which has been moving along for a while now. I wouldn’t mind hearing from them how that’s been going.
But I will agree with the overall sentiment - in most places I’ve worked in software when I thought to myself “fuck that customer”, I was wrong. It was actually our fault because we weren’t meeting their needs or didn’t set a clear boundary on service expectation we were willing to provide to them.
So I see it as more “respect the needs of your customer and be prepared to part ways amicably”.
If you want to call that love, sure. But I think some customers can be abusive as well so I don’t agree with that word choice.
I work in a vertical right now where prospective customers are desperate to switch from the incumbent because of abusive lock-in contracts and poor service levels for obscene pricing based on ancient processes. So, overall, I have to agree with Brian’s sentiment even if I think it comes off as too idealistic.
This is like saying you don’t like nails because you don’t understand how to use a hammer though. Developers are not understanding how to use the hints properly which is causing you a personal headache. The hints aren’t bad, the programmers are untrained - the acknowledgement of this is the first step into a saner world.
> Among the requirements of the DMA is that Apple ensures that headphones made by other brands will work with iPhones. It said this has been a block on it releasing its live translation service in the EU as it allows rival companies to access data from conversations, creating a privacy problem.
This sounds bogus right? If all the headphones can do is transmit audio via first party operating system features how is this creating a data privacy issue? How are headphones going to exfiltrate data unless they have their own Wi-Fi connection or application that can serve as a bridge? Just disallow both.
We all work at companies and know how it works - you get away with what you can. You bet wrong and nobody will believe otherwise. If it was a mistake, it’s fireable.
You could make money off of this if you are able to pair willing manufacturers to realistic and popular ideas that get generated. It could become a real market place.
Hilarious project.
Edit: I did both Mouthwash Ramen and Time Machine to the Present. I’m now addicted to this, thanks.
I understand the user pool comment but don’t understand why you wouldn’t be able to have a rust layer that’s the same as the Python one API-wise.
I say this as a user of neither - just that I don’t see any inherent validity to that statement.
If you are saying Rust consumers want something lower level than you’re willing to make stable, just give them a higher level one and tell them to be happy with it because it matches your design philosophy.
I reached this conclusion pretty quickly. With all the hand holding I can write it faster - and it’s not bragging, almost anyone experienced here could do the same.
Writing the code is the fast and easy part once you know what you want to do. I use AI as a rubber duck to shorten that cycle, then write it myself.
Difference between work and personal. For personal, you’re right because there is nothing to bootstrap off of.
But in corporate it’s provisioned to a user account that exists first.
My personal bootstrap is two Yubikeys (for redundancy) that contains the password and 2FA for my Proton Pass. This plays the role of what IT would in a company with a user directory.
PHP is a DeLorean. I think I encountered 10 segfaults in it within 1 year which is a complete joke. This was only two years ago.
It also includes breaking changes in point releases which is a nonsensical maintenance strategy - this is in stark contrast to the reputation of stability in a Corolla.
While PHP may have some strengths, it immediately fails this particular comparison.