3 ms·

Everyone is posting layers upon layers of components and frameworks. It just seems so bloated, so hostile towards the developer. From my experience, the more i

Everyone is posting layers upon layers of components and frameworks. It just seems so bloated, so hostile towards the developer. From my experience, the more independent projects you include, the harder an application will be to maintain, let alone configure and build. Am I just old and cranky? Or is there reasonable justification to do this?

devopsproject 9y ago
> Am I just old and cranky? No, but you may be a bit too optimistic. By the time you hand craft your CSS and Javascript to support all the browsers and features you need, you will have created yet another framework: deedubaya.js > Or is there reasonable justification to do this? The browser was meant to display documents. We keep trying to make into an runtime environment.
matt_s 9y ago
I'm with ya on this. Although I mostly work on back-end, it seems like a lot of the front-end frameworks have many layered requirements to just use them. Things like compilers, build tools, etc. just to use the framework. If you are starting a project, like others said, it is probably small so start with the minimal you need to get something working. And start with what you are most familiar with. Developers like to evaluate things and analyze to the Nth degree because it can be fun to bike shed. In reality the technology for the most part doesn't matter, especially for web stuff.
GeneralMaximus 9y ago
If you're unfamiliar with a framework -- whether it's Django, Rails, Express, Angular, or React -- much of the structure it imposes on your code feels tedious, over-architected, bloated, or just plain silly. Once you've built a couple applications from scratch without using a framework, you begin to realize just how boring and error-prone things can get when you do them by hand. I want to get to the good stuff, the meat of my application, as quickly as possible. Knowing a framework inside-out lets me do just that. Maybe the next time you're forced into using a framework, start looking at how it's put together under the hood. It's educational and a lot of fun. And you realize just how much accumulated knowledge these frameworks contain :)

devopsproject 9y ago

> Am I just old and cranky? No, but you may be a bit too optimistic. By the time you hand craft your CSS and Javascript to support all the browsers and features you need, you will have created yet another framework: deedubaya.js > Or is there reasonable justification to do this? The browser was meant to display documents. We keep trying to make into an runtime environment.

matt_s 9y ago

I'm with ya on this. Although I mostly work on back-end, it seems like a lot of the front-end frameworks have many layered requirements to just use them. Things like compilers, build tools, etc. just to use the framework. If you are starting a project, like others said, it is probably small so start with the minimal you need to get something working. And start with what you are most familiar with. Developers like to evaluate things and analyze to the Nth degree because it can be fun to bike shed. In reality the technology for the most part doesn't matter, especially for web stuff.

GeneralMaximus 9y ago

If you're unfamiliar with a framework -- whether it's Django, Rails, Express, Angular, or React -- much of the structure it imposes on your code feels tedious, over-architected, bloated, or just plain silly. Once you've built a couple applications from scratch without using a framework, you begin to realize just how boring and error-prone things can get when you do them by hand. I want to get to the good stuff, the meat of my application, as quickly as possible. Knowing a framework inside-out lets me do just that. Maybe the next time you're forced into using a framework, start looking at how it's put together under the hood. It's educational and a lot of fun. And you realize just how much accumulated knowledge these frameworks contain :)