Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
actualprogram
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
actualprogram
11y ago
The irony of this question should be apparent if you search for packages on npm today. How many "new projects" are there? In answer, why not create a new project? NPM INC controls npm, hasn't contributed it to the node foun
2.
▲
by
actualprogram
11y ago
io.js made a lot of noise about this, and has reached a "compromise" position that is indistinguishable to the end-user - or is LTS going to take V8 version bump over its 2.5-year life? No? Then take your scare quotes and bang y
3.
▲
by
actualprogram
11y ago
If by "match V8" you mean "skip most V8 changes"? V8 revs on par with Chrome, at a pace about four times what you say. Turns out that despite pillorying Joyent for sticking to V8 major versions, it is the only reasonably
4.
▲
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 &qu
5.
▲
by
actualprogram
11y ago
HA! Hahahaha. hahaa.... wheeze Acquisitions are thoroughly NDA'd. A few of the core team may have been told (but relationships are not universally cordial - recall that Strongloop and Nodesource are direct competitors). The io.js com
6.
▲
by
actualprogram
11y ago
Node's API stability is a wonderful and many-layered thing. While more and more of the API is moving towards stability in the colloquial "is this going to change between versions?" sense, it's still a mixture. See this s
7.
▲
by
actualprogram
11y ago
If you're concerned with stability, the best thing you can do is wait for the LTS release to come off the 4 branch. A quick glance at outstanding issues will show a number of integration bugs are still outstanding, and the new v8 was l
8.
▲
by
actualprogram
11y ago
Let's review the conditions of your example: no source, no debugger, two function calls And the assertion that // works as a strategy. There's only two things you could possibly comment out, so really the exam
9.
▲
by
actualprogram
11y ago
I can. It's long and tedious, because a lot of it is very simple things you learn very early on writing and maintaining software. You seem to be arguing that your example demonstrates the fact that you can localize a bug in the code wi