Re:Do Not Learn Frameworks – Learn the Architecture
by akurilin on Friday April 03, 2015 @03:31AM
(#9314747)
It's a possibility, which is why you need to evaluate how much the community likes the project, how much they depend on it surviving, how many people would be likely to keep it afloat in case the core devs peace out, how active the core team has been over the long and short terms etc. There's a whole art to picking OSS tooling for your team, none of it is devoid of risk, there's no free lunch.
Obviously, it'd also be totally OK for us to help maintain it with the rest of the people who care, that's a big part of it. Given how much you end up reading the source of frameworks once you really start using them (at least in my ecosystems), you're one step away from starting to change them.
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.
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.
And then Haskell's Yesod gets abandoned when the core devs move to shinier things and nobody else is bothered, like several Clojure web frameworks that were touted back in the day...
And you realise that maybe updating your own framework when and were you needed it, was not that big of a deal actually....