3 ms·
Am I the only one who's skeptical? Here's the scenario: I want to instrument my production system using free and/or self-built tools. So I take a crack at it,
by _greim_ 11y ago
Am I the only one who's skeptical?
Here's the scenario: I want to instrument my production system using free and/or self-built tools. So I take a crack at it, and discover it's poorly documented and otherwise hard to find good information.
Next step: I start researching and asking the community. I'm quickly directed to "N|Solid," but it's too expensive. So I keep working and eventually cobble together enough knowledge to be passably competent in the area.
I'd like to contribute my expertise back to Node.js in the form of documentation and code improvements, so other people can easily do it for free, but I seem to be hitting a brick wall. Oh, it turns out lots of core Node contributors work for NodeSource / N|Solid, and have zero interest in making this aspect of Node.js easier for people to do for free.
Maybe I'm just being paranoid?
- actualprogram 11y agoI 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.