>why not just keep it voluntary, why force it on people?
People hate learning new tools, even if they are more efficient. People would rather avoid doing things than learning a tool to do it efficiently.
Even in this thread you can see simeone who is / was a Vim holdout. But the improvement from Vim to IDE will be a fraction of the difference compared to AI integrated IDEs.
Most companies I've worked with don't care if you use vim or an IDE.
I've worked with people using vim who wildly outproduce full teams using IDEs, and I have a strong suspicion that forcing the vim person to use an IDE would lower their productivity, and vice versa
>I've worked with people using vim who wildly outproduce full teams using IDEs
This is not due to the editor. Vim is not a 20x productivity enhancer.
>forcing the vim person to use an IDE would lower their productivity
Temporarily, sure. But there productivity should actually go up after they are used to it. This idea of wanting to avoid such a setback and avoiding change is what keeps people on such an outdated workflow.
Did people force React? Cloud infrastructure? Microservices? You get it.
I know there are people still using PHP 5 and deploying via FTP, but most people moved on to be better professionals and use better tools. Many people are doing this to AI, too, me included.
The problem is that some big companies and influential people treat AI as a silver bullet and convince investors and customers to think the same way. These people aren't thinking about how much AI can help people be productive. They are just thinking about how much revenue it can give until the bubble pops.
> Did people force React? Cloud infrastructure? Microservices? You get it.
Actually, yes; People forced React (instead of homegrown or different options) because its easier to hire to, than finding js/typescript gurus to build your own stuff.
People forced cloud infrastructure; even today, if your 10-customer startup isn't using cloud at some capacity and/or kubernetes, investors will frown on you; devops will look at you weird (what? Needing to understand inner workings of software products to properly configure them?)
Microservices? Check. 5 years ago, you wouldn't even be hired if you skipped microservices; everyone thinks they're gooogle, and many startups need to burn those aws credits; thats how you get a dozen-machine cluster to run a solution a proper dev would code in a week and could run on a laptop.
Forcing react, cloud infra and microservices makes a lot more sense than forcing certain development tools. One is the common system you work, the other is what you use to essentially edit text.
Its basically the same. It abstracts away a layer of complexity, so you focus on different stuff. The inherent disadvantage of using these shortcuts/abstractions is only obvious if you actually understand their inner workings and their shortcomings - being cloud services or llm-generated code.
Today you have "frontend programmers" that couldn't implement a simple algorithm even if their life depended on it; thats not necessarily bad - it democratizes access to tech and lowers the entry bar. These devs up in arms against ai tools are just gatekeepers - they see how easy is to produce slop and feel threatened by it. AI is a tool; in most cases will improve the speed and quality of your work; in some cases, it wont. Just like everything else.
> If one person writes code only in react and another only in vue, in the same product, you have a mess.
Huh? quick example - a customer-facing platform with a provisioning dashboard, and a user dashboard; they can (and should, for several reasons) be developed as separate applications, and will depend on different APIs. Are you saying having 2 distinct technologies on 2 distinct components of a product is a mess? Without any other details on the product?
A good example on the type of products with these separations are e-commerce systems; payment gateways; cloud-native SaaS solutions, etc etc etc.
I'm sorry to tell you this, but your comment just shows how deep your lack of experience is; any reasonable complex product using frontend technology will have different interfaces with different requirements, different levels of polishing and - frequently - maintained by completely different teams.
People hate learning new tools, even if they are more efficient. People would rather avoid doing things than learning a tool to do it efficiently.
Even in this thread you can see simeone who is / was a Vim holdout. But the improvement from Vim to IDE will be a fraction of the difference compared to AI integrated IDEs.