3 ms·

Its basically the same. It abstracts away a layer of complexity, so you focus on different stuff. The inherent disadvantage of using these shortcuts/abstraction

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.

procaryote 1y ago
Not really... If one person writes code only in react and another only in vue, in the same product, you have a mess. If one person writes their react code in vim and another writes it in an IDE, you don't have a mess.
- aforwardslash 1y ago
  > 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.

procaryote 1y ago

Not really... If one person writes code only in react and another only in vue, in the same product, you have a mess. If one person writes their react code in vim and another writes it in an IDE, you don't have a mess.

aforwardslash 1y ago
> 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.