3 ms·
Why not both? Certainly everyone who creates a (somewhat serious) web framework is at least aware that they could also participate in the development of an exi
by jstummbillig 4y ago
Why not both?
Certainly everyone who creates a (somewhat serious) web framework is at least aware that they could also participate in the development of an existing on. If they feel there is something to gain by going from scratch, why not? I don't think the popular existing frameworks exactly suffer from under-contribution.
- porcc 4y agoThe incentives here seem strongly skewed towards having your name on a new framework for career purposes rather than improving the ecosystem at large
- jstummbillig 4y agoThat seems wrong, intuitively. If anything, having meaningful contributions to a long standing project go through should relatively advance your cause, not hinder it.
- porcc 4y agoIntuitively maybe. In practice definitely not. Creator of xxx with 100 stars has obvious and easily understood impact where "contributor" could mean anything
- XCSme 4y ago> Why not both? My point was that it's fine if someone starts working on a new framework, but personally I would rather have all that effort be used for developing services or tools that are actually needed and do bring value to the community. EDIT: To make it more clear, the issue is when the creators of such frameworks do believe they are going to change the world by recreating in a slightly different way something that already exists. If they are doing this for fun or to get experience, it's all good, but very often those frameworks do seem to have the ambition of becoming the next big thing and revolutionizing the way people are developing web apps.