3 ms·
Actual problem: too many people have a hard time distinguishing between a simple website and everything else. Build tools are great for apps and "not-simple" w
by sublinear 2y ago
Actual problem: too many people have a hard time distinguishing between a simple website and everything else.
Build tools are great for apps and "not-simple" websites.
Once you get into building a ton of CSS into a theme according to corporate design guidelines, several similar pages that only differ by their contained sections in the body, all kinds of custom widgets to support, etc. then you need build tools.
Otherwise I 100% agree people misuse build tools and then complain that the build tools are bad.
I'm fully expecting a ton of push back from the "js sucks" crowd who don't actually do web dev.
- mhuffman 2y ago>Build tools are great for apps and "not-simple" websites. The problem is that bootcamps and similar use project generation tools even for hello world sites while baby-devs are learning. There is no nuance. In one respect this is like jumping into the deep end of the pool and gets you moving quickly, but in another it really leaves them spinning if something goes wrong. And unless ChatGPT or a lucky SO post can tell them, optimization, speed, and cost controls are off the table altogether.
- tommy_axle 2y agoThe thing is that even on a simple site with html and css while creating it there might be issues that you can quickly catch something that assists you... tools. The page looks broken? Oh, being able to lint that html or css will quickly find any issues stemming from that but hey those are tools to introduce. Not a build tool as in generating an artifact in this case but often checking is part of that pipeline to avoid errors. I agree that it's gotten pretty crazy for certain things over the years but there's a good balance in there somewhere and it's only natural to advance technologically speaking with the addition of tools.