3 ms·
I love it. Not only were the tricks interesting (I'll have to explore those more to see if they scale in some projects I'm working on) but the advice rings exce
by BinaryIdiot 10y ago
I love it. Not only were the tricks interesting (I'll have to explore those more to see if they scale in some projects I'm working on) but the advice rings exceptionally true. Well at least in my opinion.
I've done web development for a little over 12 years now and the amount of times I've seen someone pull in a huge framework, fonts, tons of libraries just to make a simple page is astounding. I once worked at a job where they abused ASP.Net to such a degree that they were delivering a page to the user of over 70MB (about 60MB of that was only ViewState!!!) and while the application had its complex pieces that was only on a homepage that showed a very, very crude dashboard with only the functionality to re-order boxes. Boxes!
Frameworks have their place. Libraries have their place. They're helpful. But you don't need to bring them in every single time you write a web site or application. That code eventually has to be downloaded and viewed by a user and if you can do it with as few dependencies as possible your users will subconsciously thank you.
- JustSomeNobody 10y agoBecause developers today grow up in a world of computing abundance. They don't realize what it's like to develop on limited resources. There needs to be a balance between bare bones and throw everything at it that you can find on Github.
- lloyd-christmas 10y ago> I've seen someone pull in a huge framework, fonts, tons of libraries just to make a simple page is astounding... But you don't need to bring them in every single time you write a web site or application. I'm a back end developer. I learned JS in the context of Node. The amount of time it would take me to learn some useful CSS would decimate my ability to get something out the door compared to just pulling in bootstrap. It's often the case that there simply isn't enough to be done to necessitate hiring someone correctly suited for the job. Additionally, whenever I leave my company and they find someone to replace me, there's a strong chance that person knows bootstrap. There is a balance to be had with user joy and developer joy.
- welanes 10y ago> The amount of time it would take me to learn some useful CSS. What's with the myth that CSS is hard? It's perhaps the easiest thing about web dev. Learn flexbox, learn units of measurements, learn specificity, learn media-queries - 5 hours max (a week of lunch at the desk) playing around in JSfiddle, and you're most of the way there. Bootstrap is fine but pulling in a framework that has 656 classes seems a little unnecessary most of the time.