3 ms·
Most apps are not staffed by 50-60 frontend engineers, so simplifying for solo devs (which is by definition the majority of developers) is worthwhile.
by zapt02 5y ago
Most apps are not staffed by 50-60 frontend engineers, so simplifying for solo devs (which is by definition the majority of developers) is worthwhile.
- vinnymac 5y agoMost applications are certainly not staffed by large teams, but the advantages would be best seen in large codebases. Most solo developers are working on much smaller TypeScript codebases, and won't experience many issues with the build system. TypeScript is the main language that I program in every day, and I don't see the advantages of this proposal outweighing the disadvantages.
- mekster 5y agoI would think the opposite. Solo devs are in the most flexible state and they don't care if they need to go through a bit of inconvenience for a slight boon to code quality but say you got several average devs who can only be taught on how to do these things, it gets annoying to set it all up and make sure nothing breaks or you'll be wasting time babysitting their environment.
- giraffe_lady 5y ago> they don't care if Bold to speak for the group of devs likely to have the most variety. Personally I hate twiddling with build systems and will happily write worse code to avoid it so what I do know.
- pjmlp 5y agoOn my solo projects, I never care about JavaScript build infrastructure, it is all pure vanilaJS. It feels so liberating not having to deal with the usual mess of JavaScript toolchains.