I think LLMs also kill off most programming languages. I think we’ll end up with a handful of languages that LLMs most proficient at writing for and the languages required for device or processor compatibility. The cost improvement for an LLM to emit a feature (with an engineer in the loop) is too much of an improvement. We’ll look at engineers coding in C the same way we look at engineers today who code in assembly.…
I've done a bit of experimentation with that. And the irony is Rust seems to fare best because of the error messages of the compiler. I have had a lot of conversations with Claude about it and it supports that theory.
Vibe coding kills open source
261–270 of 304 posts
Re: Vibe coding kills open source
#262Re: Vibe coding kills open source
#263Re: Vibe coding kills open source
#264Earlier quoted context omitted.
> What are you talking about? Illustrators and artists are not being replaced by AI or required to use AI to "keep up" in the vast majority of environments. I don't know what jobs have been impacted yet, but there will likely be pressure for all content creators and knowledge workers to use the tools to get more work done. We'll probably start seeing this in software development this year. The tools finally feel read…
> I don't know what jobs have been impacted yet, but there will likely be pressure for all content creators and knowledge workers to use the tools to get more work done. You claimed that it already happened to illustrators and artists, and while I am sure they use it one way or another, I don't think it transformed the industry. Now, I am not saying that it won't amount to anything in software, I just don't think it…
I really don't know what else to say.
Re: Vibe coding kills open source
#265Re: Vibe coding kills open source
#266Small bespoke personalized on the spot apps are the future with LLMs. The future will absolutely not be "How things are today + LLMs" The paradigm now for software is "build a tool shed/garage/barn/warehouse full of as much capability for as many uses possible" but when LLMs can build you a custom(!) hammer or saw in a few minutes, why go to the shed?
Re: Vibe coding kills open source
#267Earlier quoted context omitted.
But millions discussions are needed and will always be needed? "Create a copy of Amazon.com" ok, how did you want to handle 3pl fulfilment and international red tape? "No not that complicated, a minimal copy" How minimal? How many servers should I provision? How vertically integrated should we get? Etc. I really want to see someone build an app of any value with minimal decisions made.
Amazon is not one app, its hundreds of them bundled in some giant monster. You could easily replicate the store part of it minimally, at its core its just an index of products, a basket and checkout system. There are other parts that make up the whole thing of course. There is a lot of room between no value and trillion dollar company
Re: Vibe coding kills open source
#268Generative AI is a major setback to OSS licensing. I've been on projects where we needed to do a "cleanroom" implementation and vet the team has never viewed the source code of competing products. Now in the gen AI era, coding agents are IP laundering machines. They are trained on OSS code, but the nuances of the original licenses are lost. On the whole, I think it is a net gain for civilization, but if we zoom into…
It could be a net gain for civilization if it stayed open, decentralized and off the hands of private companies, but that's not at all the case. Only tecchies care or even know about open models
Re: Vibe coding kills open source
#269Earlier quoted context omitted.
> I don't know what jobs have been impacted yet, but there will likely be pressure for all content creators and knowledge workers to use the tools to get more work done. You claimed that it already happened to illustrators and artists, and while I am sure they use it one way or another, I don't think it transformed the industry. Now, I am not saying that it won't amount to anything in software, I just don't think it…
I can write, unit test, code review, and QA test new HTTP endpoints in all of 15-30 minutes. It's good code. I really don't know what else to say.
However, the complexity is still not handled super well, as you need to spend more time in code review and testing to make sure all edge cases are covered and the general module interconnection is decent. Ideally we want to modularize and make the breaking surface very small, but often it is not possible.
I think the next step is to fully remove people as accepting changes manually is just too brittle; I also think it is probably possible to do with the current tools but needs a very different approach from the current meta of highly specific docs.
Re: Vibe coding kills open source
#270I am a huge proponent of using AI tools for software development. But until I see a vibe coded replacement for the Linux kernel, PostgreSQL, gcc, git or Chromium, I am just going to disagree with this premise. If I am on a system without Python installed, I don't see Claude saying, oh, you don't need to download it, I'll write the Python interpreter for you.
> I am a huge proponent of using AI tools for software development. But until I see a vibe coded replacement for the Linux kernel, PostgreSQL, gcc, git or Chromium, I am just going to disagree with this premise. Did you read it? It isn't saying that LLMs will replace major open source software components. It said that the "reward" for providing, maintaining and helping curate these OSS pieces; which is the ecosystem…
It is in the title: "Vibe coding kills open source"
Clickbait titles beget clickbait responses.