Node.js forked, Ayo.JS, is trying to find its way

By: (plus.google.com) +David Herron; Date: Sat Sep 23 2017 17:00:00 GMT-0700 (Pacific Daylight Time)

Tags: Node.JS » Open Source Governance » Ayo.JS

A month ago we suddenly had news of a hostile fork of Node.js, called Ayo.js, by Node.js team members upset over what they called Code of Conduct violations. Supposedly another Node.js team member was routinely harrassing people (a claim he has denied) and spoke against having a Code of Conduct. I don't know whether any of that is true. What's necessary is to check in with Ayo.js, see what they're doing, and if there is any compelling technical reason for their existence.

Going by the Ayo.js issue queue, that team is considering the same problem. Several issues are suggesting breaking changes with Node.js, that might produce a superior implementation. In one issue the folks are explicitly debating whether they should maintain one-for-one compatibility, or to strike out on their own.

Project home page: (github.com) https://github.com/ayojs/ayo

Also see Node.js has been forked over Terms of Conduct violations forming Ayo.JS project

The first thins I see is a warning that Ayo.JS is a fork from Node.JS, and that they haven't fixed up all the documentation, and therefore lots of links will point back to the Node.JS project. In other words, growing pains. There's lots of documentation, and perhaps not enough people to take care of these little details. And those details are very important to square away if they are to make anything of themselves.

I don't have any insider knowledge. I'm looking in from the outside, and asking questions. If I've come to a wrong conclusion, please point out what's off, and where we might learn the truth.

As they say - by their fruits ye shall know them. Hence, what are they doing in the (github.com) Issue Queue is a great indicator of where Ayo.js is heading.

(github.com) https://github.com/ayojs/ayo/issues/9 Asks about strategy for merging changes from "upstream project" (Node.js). In other words, lots of work is going into Node.js, and the Ayo.js project would like to make use of that work. The discussion is about the difficulty of pulling in upstream changes when there are also local changes. The resulting merge conflicts will be difficult to process, and doing rebase operations is also extremely difficult.

(github.com) https://github.com/ayojs/ayo/issues/19 Asks about bringing Fibers into Ayo.js core. As one of the responses pointed out, "Fibers are largely superseded by async/await and solve a problem ayo doesn't really have."

Comments in the thread claim that Fibers are much faster than Promise/async/await, and perhaps are easier to understand. I don't know about that. However, that they're considering this indicates a desire to commit large incompatibilities with Node.js.

(github.com) https://github.com/ayojs/ayo/issues/56 I don't understand the issue title, "Consider additive systems for importing ES Modules", but going by the discussion it's about dropping the decision to use .mjs for ES6 Modules, and .js for the traditional CommonJS modules. Instead it would use .js for both.

Upstream has decided to go woth .mjs and .js and have deeply studied the issue and decided on this direction. Some suggest that result is ugly - and for example the MacOS Finder will treat a .js file correctly, but give a blank icon for .mjs files. In other words the .mjs/.js decision is incompatible with other systems, even if its an excellent decision for Node.js. Except that the @std/esm supports ES6 modules with the .js suffix, showing proof that it's possible.

Again, I don't understand all the technical ins-and-outs, but it's a clear indication of willingness to implement breakage with Node.js.

(github.com) https://github.com/ayojs/ayo/issues/67 Here we go, navel gazing: "Define clear goals/motivations of the Ayo.js project"

  • "corporate domination of governance and organizational ossification that made a fork necessary"
  • "run a node-like project that prioritizes inclusivity/diversity while maintaining interoperability with Node.js"
  • "Ayo.js was created to break out of the organizational quagmire Node.js is in and to make aggressive changes to push the project forward technically. This will almost definitely eventually mean making non-interoperable changes; without allowing for this, Ayo is effectively chained to Node.js."
  • "Ayo.js was created to be a shadow-project of Node.js which is differentiated by having explicitly stated political aims (i.e. 'people over software' or similar). This project should keep interop with Node.js as a requirement to all development."

That discussion isn't finished, but it was pointed out the Ayo.js Values document clearly says the project's purpose is to create a new governance model.

In other words, it's not about technical issues, but governance.

Except the crew is also talking about breaking compatibility over technical issues. Their actual behavior is more than just establishing a new governance model.

(github.com) https://github.com/ayojs/ayo/issues/68 More navel gazing .. "Is ongoing interoperability with Node.js a requirement for Ayo?"

This points out that if all they do is establish new governance, there won't be any compelling reason to use Ayo.JS and it will all be a waste of time.

The issue points out the io.js fork did not have major breaking changes with Node.js. That's an important point since Node.js became hugely improved when the io.js and Node.js teams reintegrated.

Summary

It's too early to say where Ayo.js is going. There is a pull-and-tug between two factions, some that want to make large technical changes in order to adopt a favorite feature, and others whose goal is a better governance model.

Which way will they go?

« Electron considered harmful because it rides on Chromium Yarn versus npm, what's the big deal? »
2016 Election 2018 Elections Acer C720 Ad block Air Filters Air Quality Air Quality Monitoring AkashaCMS Amazon Amazon Kindle Amazon Web Services America Amiga and Jon Pertwee Android Anti-Fascism AntiVirus Software Apple Apple Hardware History Apple iPhone Apple iPhone Hardware April 1st Arduino ARM Compilation Artificial Intelligence Astronomy Astrophotography Asynchronous Programming Authoritarianism Automated Social Posting AWS DynamoDB AWS Lambda Ayo.JS Bells Law Big Brother Big Data Big Finish Big Science Bitcoin Mining Black Holes Blade Runner Blockchain Blogger Blogging Books Botnets Cassette Tapes Cellphones China China Manufacturing Christopher Eccleston Chrome Chrome Apps Chromebook Chromebox ChromeOS CIA CitiCards Citizen Journalism Civil Liberties Climate Change Clinton Cluster Computing Command Line Tools Comment Systems Computer Accessories Computer Hardware Computer Repair Computers Conservatives Cross Compilation Crouton Cryptocurrency Curiosity Rover Currencies Cyber Security Cybermen Cybersecurity Daleks Darth Vader Data backup Data Formats Data Storage Database Database Backup Databases David Tenant DDoS Botnet Department of Defense Department of Justice Detect Adblocker Developers Editors Digital Nomad Digital Photography Diskless Booting Disqus DIY DIY Repair DNP3 Do it yourself Docker Docker MAMP Docker Swarm Doctor Who Doctor Who Paradox Doctor Who Review Drobo Drupal Drupal Themes DVD E-Books E-Readers Early Computers eGPU Election Hacks Electric Bicycles Electric Vehicles Electron Eliminating Jobs for Human Emdebian Encabulators Energy Efficiency Enterprise Node EPUB ESP8266 Ethical Curation Eurovision Event Driven Asynchronous Express Face Recognition Facebook Fake News Fedora VirtualBox Fifth Doctor File transfer without iTunes FireFly Flash Flickr Fraud Freedom of Speech Front-end Development G Suite Gallifrey Gig Economy git Github GitKraken Gitlab GMAIL Google Google Chrome Google Gnome Google+ Government Spying Great Britain Green Transportation Hate Speech Heat Loss Hibernate High Technology Hoax Science Home Automation HTTP Security HTTPS Human ID I2C Protocol Image Analysis Image Conversion Image Processing ImageMagick In-memory Computing InfluxDB Infrared Thermometers Insulation Internet Internet Advertising Internet Law Internet of Things Internet Policy Internet Privacy iOS iOS Devices iPad iPhone iPhone hacking Iron Man iShowU Audio Capture iTunes Janet Fielding Java JavaFX JavaScript JavaScript Injection JDBC John Simms Journalism Joyent Kaspersky Labs Kext Kindle Kindle Marketplace Large Hadron Collider Lets Encrypt LibreOffice Linux Linux Hints Linux Single Board Computers Logging Mac Mini Mac OS Mac OS X MacBook Pro Machine Learning Machine Readable ID Macintosh macOS macOS High Sierra macOS Kext MacOS X setup Make Money Online Make Money with Gigs March For Our Lives MariaDB Mars Mass Violence Matt Lucas MEADS Anti-Missile Mercurial MERN Stack Michele Gomez Micro Apartments Microsoft Military AI Military Hardware Minification Minimized CSS Minimized HTML Minimized JavaScript Missy Mobile Applications Mobile Computers MODBUS Mondas Monetary System MongoDB Mongoose Monty Python MQTT Music Player Music Streaming MySQL NanoPi Nardole NASA Net Neutrality Network Attached Storage Node Web Development Node.js Node.js Database Node.js Performance Node.js Testing Node.JS Web Development Node.x North Korea npm NVIDIA NY Times Online advertising Online Community Online Fraud Online Journalism Online Photography Online Video Open Media Vault Open Source Open Source and Patents Open Source Governance Open Source Licenses Open Source Software OpenAPI OpenJDK OpenVPN Palmtop PDA Patrick Troughton PayPal Paywalls Personal Flight Peter Capaldi Peter Davison Phishing Photography PHP Plex Plex Media Server Political Protest Politics Postal Service Power Control President Trump Privacy Private E-mail server Production use Public Violence Raspberry Pi Raspberry Pi 3 Raspberry Pi Zero ReactJS Recaptcha Recycling Refurbished Computers Remote Desktop Removable Storage Republicans Retro Computing Retro-Technology Reviews RFID Rich Internet Applications Right to Repair River Song Robotics Robots Rocket Ships RSS News Readers rsync Russia Russia Troll Factory Russian Hacking Rust SCADA Scheme Science Fiction SD Cards Search Engine Ranking Season 1 Season 10 Season 11 Security Security Cameras Server-side JavaScript Serverless Framework Servers Shell Scripts Silence Simsimi Skype SmugMug Social Media Social Media Networks Social Media Warfare Social Network Management Social Networks Software Development Software Patents Space Flight Space Ship Reuse Space Ships SpaceX Spear Phishing Spring Spring Boot Spy Satellites SQLite3 SSD Drives SSD upgrade SSH SSH Key SSL Stand For Truth Strange Parts Swagger Synchronizing Files Tegan Jovanka Telescopes Terrorism The Cybermen The Daleks The Master Time-Series Database Tom Baker Torchwood Total Information Awareness Trump Trump Administration Trump Campaign Twitter Ubuntu Udemy UDOO US Department of Defense Video editing Virtual Private Networks VirtualBox VLC VNC VOIP Vue.js Walmart Weapons Systems Web Applications Web Developer Resources Web Development Web Development Tools Web Marketing Webpack Website Advertising Weeping Angels WhatsApp William Hartnell Window Insulation Windows Windows Alternatives Wordpress World Wide Web Yahoo YouTube YouTube Monetization