Any updates about the Node leadership disaster news from the 10 days ago? That left a bad taste in my mouth about node.
Who cares? SJW left and the programmers stayed. Nothing will change from the release/code perspective.
Node v8.5.0
21–30 of 57 posts
Re: Node v8.5.0
#22Earlier quoted context omitted.
https://www.theregister.co.uk/2017/08/24/nodejs_forks_ayo_co...
tl;dr > On Tuesday, the thirteen-member steering committee came together to vote on whether to remove Rod Vagg, a TSC member and Node.js contributor, over his controversial statements on Twitter and GitHub that prompted complaints. They also voted on whether to ask Vagg to resign.
I am always curious about what the statement was. When it comes to SJWs they usually do not want to display that because it is often such silly things.
Re: Node v8.5.0
#23Re: Node v8.5.0
#24Any updates about the Node leadership disaster news from the 10 days ago? That left a bad taste in my mouth about node.
[deleted]
Re: Node v8.5.0
#25Any updates about the Node leadership disaster news from the 10 days ago? That left a bad taste in my mouth about node.
More a controversy than a disaster. The last commits [0] are only about governance model, discord link... There are some rebase but that's it. Nothing will probably come from this fork.
Re: Node v8.5.0
#26Any updates about the Node leadership disaster news from the 10 days ago? That left a bad taste in my mouth about node.
More a controversy than a disaster. The last commits [0] are only about governance model, discord link... There are some rebase but that's it. Nothing will probably come from this fork. [0] https://github.com/ayojs/ayo/commits/master
I find it ironical that people who take up pitch forks and accuse others of being a hazard to the health and growth of a project would, in lieu of having their demands met, do one of the worst actions possible against what they were "protecting": splitting the code base and the community with a fork.
Re: Node v8.5.0
#27Any updates about the Node leadership disaster news from the 10 days ago? That left a bad taste in my mouth about node.
Do you have a link so I can read about this?
There were several links posted on HN a few weeks ago. I didn't notice any that were inflammatory, but all were "flagged" and taken down regardless.
In most cultural matters, this community tilts quite progressive. However, "Codes of Conduct" are an exception case, in which the community's libertarian streak clearly dominates. I do not believe that the moderators approve of that deviation. It would not surprise me if this entire thread were likewise flagged and removed if this subject draws too much conversation.
Re: Node v8.5.0
#28> add fs.copyFile and fs.copyFileSync which allows for more efficient copying of files. FINALLY. I don;t know how long we could have come with this still being a thing you need a module for, or you have to code yourself. Hopefully we get `fs.mkdirp` and `fs.remrf` somewhere down the line. > Add support for ESM. This is currently behind the `--experimental-modules` flag and requires the `.mjs` extension. I don't like…
>I don't like the `.mjs` extension, but I understand the need for it, and I'm just glad that modules are finally here.
I read that a lot. Why do people don't like the new extensions?
Seems like the most elegant and programmatically more performant and less hassle free, solution to the issue.
Everything else looks like a terrible kludge.
Re: Node v8.5.0
#29Earlier quoted context omitted.
I probably don't understand what I'm looking at. I would like sendFile/sendFileSync - which would abstract over TransferFile on Windows.
The reason you're unlikely to see that in the node binary is presumably the same reason copyFile has taken so long: node aims to have a small core that enables a rich userspace. There's gotta be a very good reason to bog down the core with more stuff, since that equals less other stuff and more bugs. Some of the few valid reasons are ubiquity (which HTTP is, but Windows and sending files are not), or things that were…
>node aims to have a small core that enables a rich userspace
So, dogma?
Because copying a file fits right in any kind of "small core" -- and helps create a more dependable and usable "rich userspace" which doesn't need to reinvent the wheel 200 times for basic stuff.
Re: Node v8.5.0
#30Any updates about the Node leadership disaster news from the 10 days ago? That left a bad taste in my mouth about node.
What disaster?
Just some ranting person(s) taking their marbles and going home. Let's hope the door didn't hit them on their way out.
Otherwise, Node looks totally non-impacted and business as usual.