4 ms·
I'm not really happy to hear about this. To me, it demonstrates that the JS Foundation continues to focus on the wrong priorities. They've thoroughly neglected
by EB66 8y ago
I'm not really happy to hear about this. To me, it demonstrates that the JS Foundation continues to focus on the wrong priorities. They've thoroughly neglected their stewardship responsibilities for a number of different open source projects. They've seen a reduction in sponsorship/funding for maintaining projects and they've pulled back from GSoC and other events that were essential in drawing in new open source contributors.
On top of all that, they've piled on bureaucracy and alienated many important long-time contributors: https://github.com/globalizejs/globalize/pull/703 https://github.com/globalizejs/globalize/pull/703
Despite their slogan "The Center of Gravity in the Javascript Ecosystem", these days, the JS Foundation is largely an irrelevant organization. I see this merge as a last ditch effort to retain some sort of relevancy. They've abandoned their roots as a center of innovation. I see no effort to pivot their existing dying projects to compete in today's JS ecosystem dominated by component-based SPA frameworks.