3 ms·
The developer must understand when it's time to use a framework. A small website with few pages doesn't need a frontend framework. But if you have to deal with
by dugluak 8y ago
The developer must understand when it's time to use a framework. A small website with few pages doesn't need a frontend framework. But if you have to deal with a large/complex application using a web framework is not a bad idea as they offer a lot of reusable components, you don't need to "reinvent wheels" using HTML & CSS.
- saagarjha 8y ago> The developer must understand when it's time to use a framework Frameworks are useful but not nearly as much as people might think. There are many cases where a static site generator (as a simple example, Markdown → HTML converters) or simple templating solution may be "enough", and they're relatively easy to understand as bells and whistles on top of HTML and CSS.
- pmlnr 8y ago> developer must understand when it's time to use a framework. The developer does. Do the project owner/manager/mid level personnel? That's a better question.
- yarrel 8y agoThere's no moral panic about project managers though. Their decisions do not affect the excesses of software development in any way, only those of software developers do. ;-)