4 ms·

I agree 100% with this. Every framework has its pain points - that is why it limits you as a framework, as opposed to homerolling your own solution. The gain

by Bahamut 12y ago

I agree 100% with this. Every framework has its pain points - that is why it limits you as a framework, as opposed to homerolling your own solution. The gain you get is better support for foundational tasks and the ability to focus on the high level business requirements faster. There are very smart people working on the teams of all of these frameworks, available for free with an MIT license and supported for free - take advantage of it, but don't expect any of them to be perfect and expect to still be putting in hard work in understanding the internals of all of them.

coldtea 12y ago
>There are very smart people working on the teams of all of these frameworks Dunno, most of the JS frameworks have crappy design and mediocre implementations. Angular is not some shining beacon, it's convoluted beyond belief. Being a framework, and being from a large company doesn't mean much, nor it guarantees that the result reflects having been worked by "smart people". The SUN people were smart too, and yet we got the J2EE shit-fest of early to mid 00's. IBM also shipped it's share of crappy frameworks, Microsoft too. >and expect to still be putting in hard work in understanding the internals of all of them. Also expect those framework based skills to be obsolete 4-5 years down the line, when some other shiny framework comes along. Also expect to have to rewrite tons of your work, when the developers with ADD lose interest and go to rewrite the framework, like with Angular 2 (and I've relived these all over again with (Java) Struts 2, (Python) Zope 3, and tons of other stuff besides).