4 ms·
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
by Joeri 12y ago
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.
- jacquesm 12y agoWith 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.
- emodendroket 12y agoIf that's really the case you could easily just cut out features you don't intend to use.
- scott_karana 12y agoReally? What about cross-cutting features like logging, sessions, debug hooks, et cetera? That's a non-trivial refactor right there.
- emodendroket 12y agoWell, true, although, from your list, it's hard to think of application where you wouldn't want those things.
- akurilin 12y agoExactly. And rolling your own is pretty wasteful when most "off the shelf" ones are good enough for most use cases.
- deleted 12y ago[deleted]