3 ms·
My position on web development for even consulting projects is just to not use build processes as much as possible. I still end up using them for things like JS
by andrewmcwatters 6y ago
My position on web development for even consulting projects is just to not use build processes as much as possible. I still end up using them for things like JSX, but I don’t bundle anymore, nor do any web projects I build require installation out of the box.
I’ve found that by doing so, I can just basically ignore, for years on end, all of the peddlers pushing how their projects make development easier or faster or some nonsense.
You know what’s easiest and fastest? Flat files in a good directory structure with some getting started template.
That’s it. The fastest build times are the ones that don’t exist. Period.
Web development is as complicated as you choose to make it. Very few fields work like this.
- shakow 6y ago> Very few fields work like this. Quite the opposite; I would argue that webdev is basically rediscovering the whole shebang, but decades later. Modern webdev with transpilation, linking, pruning, compilation to WASM etc. starts to dreadfully look like the classical native development paradigm.
- jhgb 6y ago...which is essentially cargo cult programming, since browsers work in an entirely different way (perhaps with the exception of WASM because of how it's designed).
- andrewmcwatters 6y agoYeah, and basically none of that is necessary. Which is my point exactly.