4 ms·
I suppose it could just be coincidence that the io.js fork didn't just disable, but did non-trivial work to remove facilities that allowed for competing (and to
by actualprogram 11y ago
I suppose it could just be coincidence that the io.js fork didn't just disable, but did non-trivial work to remove facilities that allowed for competing (and totally open source) profiling & debugging tooling.
Certainly casts a "community governance" spat in a bit of a new light when suddenly the major movers behind the fork turn out to have a significant financial interest in it.