Re:Do Not Learn Frameworks – Learn the Architecture
by Joeri on Friday April 03, 2015 @06:55AM
(#9315186)
In the case where an open source framework loses its maintainer, in the worst case you are the maintainer. In that case you are no worse off than with your own framework, except that for a number of years the maintenance work was done for you for free.
[ Parent
| on HN ]
Re:Do Not Learn Frameworks – Learn the Architecture
by jacquesm on Friday April 03, 2015 @10:00AM
(#9315893)
With one small difference: you'll likely have a much larger attack surface because the third party framework was created to do much more than to just service your applications.
And all that code will need to be maintained now. That can get very costly.
Re:Do Not Learn Frameworks – Learn the Architecture
by emodendroket on Friday April 03, 2015 @02:01PM
(#9317358)
If that's really the case you could easily just cut out features you don't intend to use.
Re:Do Not Learn Frameworks – Learn the Architecture
by scott_karana on Tuesday April 07, 2015 @02:01PM
(#9335841)
Really? What about cross-cutting features like logging, sessions, debug hooks, et cetera?
That's a non-trivial refactor right there.
Re:Do Not Learn Frameworks – Learn the Architecture
by emodendroket on Tuesday April 07, 2015 @02:14PM
(#9335925)
Well, true, although, from your list, it's hard to think of application where you wouldn't want those things.