article: Why You Should Stop Using UI Frameworks
-
And why not? Your personal lib will be both streamlined and controlled by you. Maybe I'm a coding megalomaniac, but I'd much rather have control of as much of my code as possible.
-
I like Angular, but the author has a really good point when you get to V7 of it. And I can't keep up with upgrading Angular versions, finally coming to a road block on V7.2 or something, breaking my entire app when compiling because my .Net framework won't play nice with it. Constantly having to change NPM packages to fix an issue. I need to revisit my website when I get time again. I may just dump it and write a new one in something else. I'm working on a PHP App Upgrade for a customer and decided to keep it in PHP but went 7.4.14 using objects I wrote, plain vanilla JavaScript ECMA6, and Plain CSS that I wrote from scratch along with BootStrap 5. I'm almost a year in now and I've been able to code in peace without having to upgrade anything. This app should be able to run another 10 years without an update.
If it ain't broke don't fix it Discover my world at jkirkerx.com
-
Even if you forego the frameworks and use plain vanilla js, eventually you'll end up making your own helper classes / ui library to reuse functionality. Imo you may as well use something like Angular / React, etc. that is well tested and documented.
I actually agree with the article in some aspects. if the project scope is small to medium: stick with basics: JS/CSS easier to maintain over the years/developers. if the project gets to be large to stupid big: frameworks do help out in at least keeping things organized. but are a super pain when updating to a new(er) version. (if possible, we still have a Angular 1 project that no one wants to touch in fear of it breaking) I was surprised the article mentioned Handlebars.js, since it's not much of a framework and more of a lightweight approach to making html partials with some customizing if needed. I feel like this belongs also in the medium range of projects, help keep you organized but not get in your way of development. technically it's a backend server side renderer, but it's also easy to build a front end version of the same thing, takes about a day to build most of the features. where I work we have technically 3 types of projects: * basic html5/JS/CSS -when no DB is needed * ASP.Net core/JS/bootstrap -when DB access is required * React/bootstrap. The first two I enjoy working in, the projects are quick and fun, the last takes way more time to work out the features and layouts, and just feels heavy in final implementation.