4 ms·
The problem isn't necessarily web developers, or certainly not all web developers. Thanks to constant penny pinching, very little gets developed from scratch in
by he_is_legend 5y ago
The problem isn't necessarily web developers, or certainly not all web developers. Thanks to constant penny pinching, very little gets developed from scratch in-house anymore - instead everything is put together using a myriad of third party code (often cheap third party code) that does things in very opinionated ways, meaning all of their dependencies become your dependencies, and every time you add another third party lib you get more dependencies. So you end up with a gigantic base of dependencies - none of which can easily be eliminated because its just a giant house of cards.
The alternative is every shop building their own functionality from scratch, with the result being 100s of competing libraries all doing very similar things but slightly different.
What needs to happen is the same as in most industries - end users / customers needs to realise the real cost of things and pay that full price. No more cheapest possible solutions. No more making do with lowest common denominators. Pay more money for better solutions.
- acabal 5y agoThe point is that front-end libraries are not as critical as most of today's web developers think they are. Sure, you can use a well-known templating library on the back end to assist in constructing HTML before you output it. But once the HTML is in the browser, 90% of it is page-based documents with some CRUD sprinkled on top. Front-end libraries are rarely required given modern HTML/CSS and modern back-end languages like PHP/RoR/Python or even JS, and it's front-end libraries that are the causing the bloat. There's no need to develop from scratch: Use third party libraries on the back end to output plain HTML/CSS on the front end.