I feel this mostly is a side effect from lack of domain knowledge. Most of the time this has happened to me, it's because I myself did not cleanly know how a problem should be solved to begin with. If you have a clear picture of what you want, approximately what syntax goes where and why, thats really when LLMs shine in my experience.
They aren't proposing to replace git though. They are just attempting to make it simpler for developers to follow changes applied by an LLM in an ergonomic fashion. Not saying it will work well but I'm happy to see someone trying a new approach here.
I’m building an in-terminal IDE over at https://github.com/paradise-runner/toast that does this. No AI, no telemetry, just a text editor that has it all baked in and is easy on the eyes.
Then go get a text editor? They’ve been around for decades. Use sublime text for all eternity. Why even complain here when what you want is a solved problem?
I'm not satisfied with any of the text editors I've used (I've used all the big ones for a few years each).
Zed was a promising new direction I.e. VSCode minus the bullshit. But it's not getting the polish / productionisation it would need to actually be a better editor than the others. And now it doesn't look like it will.
Try Gram. It's a fork of Zed which changes a few things, one of which is that all the AI stuff is disabled by default. I was interested in it because it doesn't download language servers without asking you (unlike Zed). Ultimately I'm kind of on the fence between it and Sublime, but it's a lot better than Zed imo.
They're a VC backed company, they aren't building for the user at all. The VC is their user.
Just need to see reality for how it is in the tech industry, products aren't made for users anymore they're mostly a ritual to please the VC gods. Bonus points if you're disruptive and a net-negative toward society.
No, a company will always build whatever they think will make them more money. If you want an editor without the bullshit try Sublime as it has a history of staying that way, or the good old Vim and emacs.
The more complex the more fragile. The simpler the solution the more robust. This, I feel, is an overall truth to software development. And simpler solutions, as far as I know, are usually the more useful ones.
I think we can have complex things, but they can be simple (to use, to understand, to manage). But it is really hard to make a complex thing simple. The straightforward way is to make it complicated, and most items remain that way.
When we're lucky, that complexity is mostly locked behind abstraction and you only occasionally have to care. Of course those you usually discover at 3AM on a Saturday
I've read that privileged ports was created as a trust model, so users connecting to a service using a privileged port would know that service was started by root on that server and therefore could be trusted. I always felt this was a bit wierd though, maybe I was missinformed, or maybe priviliged ports was already a thing and was just leveraged this way?
I can understand that feeling, but remember that just because you have been handed a new powertool you mustn't always use it. Life is not about optimizing everything. It makes redundant work faster, where you fully understand from the outset how to write something, but this just frees you up to learn and explore new things, and work on stuff just for the fun of it, like this.
Agreed that life is not about optimizing everything. I do enjoy writing code by hand when the framework or language is delightful to work with， it's just that HTMX isn't that choice for me. The h-attributes model doesn't fit the way I think. Also, my original point was more that once agents write most of the code, "delightful to hand-write" stops being the main criteria for picking a framework.
Not so much about language design as how easy it is to take a defensive position on something we are comfortable with when it's challanged. This prohibits growth.
When someone suggests you have been doing something the wrong way or has a new idea, it's usually better to hear them out and take what knowledge you can from them, even if they weren't actually trying to help you.
Not an expert, but, when you give Claude, or any AI agent a query it will usually need to do research, use various tools, execute commands etc. and all of this accumelates text in the conversation thread. Each subsequent query in a thread submits the entire conversation to the API, potentially consuming an unnecessary amount of tokens. Compression attempts to solve this by removing irrelevant information. For example, the entire output from a CURL query and how the AI thought about it might not be needed, having the resulting outcome might be enough. Since compression is also performed by the API though it may be worth it, or not, it always depends on the situation at hand. This is my understanding of it anyways.
I have the same CPU in my primary system, and if you can afford it, it’s so choice.
A big surprise for me, having owned both a Ryzen gen 1 & 3 previously, was that this time my system posted without me needing to flash my BIOS or play around with various RAM configurations. Felt like magic.
While I cannot see a way to effectively stop companies from collecting data from you (aside from avoiding practically everything), that doesn’t mean we should do nothing.
DuckDuckGo aren’t perfect, but I think they do a lot to all our benefit. Theirs have been my search engine of choice for many years and will continue being so.
