3 ms·
Because eventually you end up rewriting a more brittle version of an established framework. Plus someone else may have to maintain it. Working out how your vani
by pipes 2y ago
Because eventually you end up rewriting a more brittle version of an established framework. Plus someone else may have to maintain it. Working out how your vanilla code works is worse than learning a framework because there's no help.
I lived this with an app made in 2012 that was all custom JS.
Plus how far do you want to take it? Write your own security modules? Create your own anti SQL injection code? The benefit of frameworks is you get free hardened code tested by millions.
But yes, I get it, gluing together Frameworks is depressing too. It just isn't fun.
- zambachi 2y agoJavaScript, HTML, and CSS have changed a lot since 2012. I think the problem is folks tend to think like engineers with all their widgets (e.g desktop development in the browser). Even Microsoft is going full TypeScript mode. Web development is DESIGN first. Think of it like a design project and suddenly the entire workflow changes. The CSS spec today makes all this stuff super easy people just don’t spend the time actually learning. In my opinion the Laravel and Rails developers get this right.
- techpineapple 2y agoIt also leads to the irony that eventually, you’ll build libraries that then have breaking changes and you’re managing both the library and all its versions and the applications that use it.