3 ms·
Community splits around concrete technical choices (e.g. NeoVim, and use of Lua as a scripting language) SOMETIMES survive and thrive. Forks that seem to exist
by StevePerkins 4y ago
Community splits around concrete technical choices (e.g. NeoVim, and use of Lua as a scripting language) SOMETIMES survive and thrive.
Forks that seem to exist for no clear reason other than disgruntled person(s) thumbing their nose at an upstream maintainer never do.
If this were meaningful, then there would be clear roadmap (at least high-level aspirations without dates) announced with the repo’s creation. Without that, this is little more than a gripe post on a Nim mailing list.
- elcritch 4y agoIt generally seems to the latter case with mostly disgruntled people with some areas where they were passionate. It doesn't seem to be "producing" anything, so it doesn't appear to be like NeoVim or similar. The Nim compiler/core seems to be progressing still and not stagnating.
- CJefferson 4y agoThe first such fork that came to my mind was the "egcs" form of GCC. Egcs thrived and in the end effectively took over the "main" GCC line.
- HelloNurse 4y agoThere is a chance that this fork could be similar to egcs, following the same trajectory as "Nim done better" evolving into "the current Nim variant/implementation". Conservative improvements like specifying some dark corners better can attract users (more than flamboyant novel features), and correction of bugs can retain them.
- rootlocus 4y agohttps://github.com/ayojs/ayo https://github.com/ayojs/ayo comes to mind.