91–100 of 190 posts
Earlier quoted context omitted.
We should start referring to PHP as a "Composer compatible platform" and Python as a "PyPI compatible platform"
The huge collection of modules on npm is one of the strongest factors node.js has going for it, so it makes sense for them to emphasize that they're not breaking compatibility with this in forking node.
Earlier quoted context omitted.
Please don't rely on require hooks in libraries. They are kind of evil in applications already (because they amplify the "synchronous require" problem). Test your library against a version of 6to5, compile, publish, and remove that paragraph in font size 48 from your README.* (*) I hope you add such a paragraph when your library relies on a global require hook that changes the default behavior of require for all .js…
What is 'the "synchronous require" problem'? I've never run into issues with the CoffeeScript require hook, for example.
Earlier quoted context omitted.
I would make a strong cut between "application code" and "library code". For the former compilation to ES5 is overkill because the author of the code controls the runtime. For the latter the library either has to contain a long list of "tested with the following versions of the following runtimes and with the following versions of the following ES6-to-ES5-compilers" or it should be compiled pre-publish into a format…
Once those steps are literally just "use iojs", I think the calculus is a little different, no?
Earlier quoted context omitted.
I felt like he got thrown under the bus with that whole uproar, and was glad to see him in there.
With 1098 commits to libuv, which represents 35.2% of all commits to that project and the most number of commits from any single individual, and 1409 commits to node (13.8%, 3rd after Ryan Dahl and Isaac Schlueter), I'd say that him "getting thrown under the bus" is a huge understatement of what happened.
Still, the inclusion shows that not all bridges are burned, which makes me happy.
Earlier quoted context omitted.
What is 'the "synchronous require" problem'? I've never run into issues with the CoffeeScript require hook, for example.
With a lot of files app startup can be delayed and the event loop be blocked. Which messes with timeouts among other things. The problem is that each file is loaded from disk and parsed in series without any level of parallelism (no real way around that in a pre-ES6 world). With CoffeeScript you put the time it takes to compile to JavaScript on top of that. If you have a big app with a lot of CoffeeScript files, it m…
Earlier quoted context omitted.
It will be interesting what Joyent will do with its 0.11 unstable branch and how popular io.js will get.
The merge between the current 0.10.35 branch and the 0.12 branch is almost done ( https://github.com/joyent/node/milestones/0.11.15 ), we can expect version 0.11.15 within then next few days. 0.11.15 will be a release candidate for 0.12. On the other hand, they've been saying that 0.12 will come out 'soon' for over a year, so this too may take longer than I expect.
By comparison, @nodejs announced on Dec 17th, 2014 that 0.11.15 was "tomorrow", but still haven't released anything: https://twitter.com/nodejs/status/545349270241435648
...Okay, normally I roll my eyes at people asking "What does this do" but Christ this is ridiculous. From the FAQ: > What is io.js? > io.js is a JavaScript platform that is compatable with Node.js & npm. What does that even mean? Edit: Thanks for those answering. I started figuring out what it was, but sometimes folks really need to learn that "A correct definition" is not the same as "a useful definition". However,…
It's a fork of node.js with ES6 support. The goal is a faster release cycle and an updated V8 engine, plus an "open governance model" as opposed to Joyent's domination of node.js prime. https://github.com/iojs/io.js Current Project Team Members ============================ Isaac Z. Schlueter Ben Noordhuis Bert Belder Fedor Indutny Trevor Norris Chris Dickinson Colin Ihrig Mikeal Rogers Rod Vagg
Hmm. Lets hope the spork gets spooned so that no projects get knifed. If not then I guess we have to hope for a knork so we don't get stuck with a couple of chopsticks.
Glossary
Forking : Creating a fork to intentionally diverge from main-line development.
Spooning : Merging a fork back into the main line of a project
Sporking : Creating a fork that you would really like to become the next main-line version but you kinda have to prove its awesome first (sporks are pretty awesome)
Knifing : Action killing a project, abandon hope :(
Knorking : A fork replaces the original project which dies off i.e. a fork knifes the original
Chopsticking : Two forks vie for popularity splitting the community and becoming lone chopsticks. Chopsticks need to work together to make stuff happen!