Fishrock123

9 ms·

1.
by Fishrock123 11y ago
"V8 Major versions"
2.
by Fishrock123 11y ago
Haha, that was fun. :P https://twitter.com/minetweeter_/status/606481421633482752
3.
by Fishrock123 11y ago
Recruiters: No thanks.
4.
by Fishrock123 11y ago
Location: Canada Remote: Must for at least short-term Willing to relocate: probably not, not to USA Technologies: Node.js + all related things js Portfolio/Resume: https://searchbeam.jit.su/about Email: fishrock123 at
5.
by Fishrock123 12y ago
npm stands for "no problem meatbag", not "node package manager" ;) It's the package manager for javascript and will continue to be. The module system in io.js is not going to be changing anytime soon.
6.
by Fishrock123 12y ago
Yes. It is arguably larger news for io.js. However, that io.js ships with v8 4.1 is quite a large step ahead for dependants, not just for language features, but also under-the-hood stability and performance. Of course, there is also everyth
7.
by Fishrock123 12y ago
For posterity to anyone who still reads this, the spork thing is mostly my fault. And it sort of caught on. I do website and irc stuff for io.js and I had trouble describing what the project was in relation to node.js. So I called it a spor
8.
by Fishrock123 12y ago
More info will be added shortly to http://iojs.org/ See also http://nodeforward.org/ There is a lot going on, and it is a little difficult to keep track of everything, for sure. Just know that io.js will be
9.
by Fishrock123 12y ago
I would like to mention that Netflix could have consulted the express maintainers (us) but didn't. Source: myself - https://github.com/strongloop/express/pull/2237#issuecomment...
10.
by Fishrock123 12y ago
This also needs to be available for commit threads, I think. See: https://twitter.com/Fishrock123/status/476133688506609664
11.
by Fishrock123 13y ago
Using this framework right now -- it is quite excellent. Full of features, and with great, constant support. Also, it runs ontop of the Pixi.js renderer, meaning it is super, super fast.
12.
by Fishrock123 13y ago
... Why didn't I know this before? Thanks for sharing!
13.
by Fishrock123 13y ago
I find the title kind of ironic, given that sweet.js is still a compiler. :P However, it is true it would be better to have one standard-ish compiler that can just execute whichever macros you throw into it. That being said, you still run i
14.
by Fishrock123 13y ago
Bullcrap.
15.
by Fishrock123 13y ago
Qrafter (pretty much the best qr-code reader in existence) out-performs on this test. I was able to scan at least two that the author said weren't scannable. https://itunes.apple.com/ca/app/qrafter-qr-code-bar
16.
by Fishrock123 13y ago
That's what I was thinking. Seems lightly odd.
17.
by Fishrock123 13y ago
Definitely a Nexus phone. I would wait for the 5 if possible, it should be out soon. (Or just get a 4, if you can.)
18.
by Fishrock123 13y ago
I found this line in The Verge's interview with Tony Fadell (Nest's CEO): "And if the Protect senses a carbon monoxide problem, it’ll instruct the thermostat to shut off your furnace." That is of utmost importance. That
19.
by Fishrock123 13y ago
Front-End: I'm used to jQuery + Jade, but possibly something fancier like angular/ember, or even meteor. Middle: Node.js + Express (unless using meteor). If not node, then Sinatra. Database: MongoDB, Redis if necessary.