My advice to @googlecloud ppl working on @nodejs stuff (CF, GAE): stop trying to solve "npm install" on the cloud. It's a minor win with far too many edge cases. Focus efforts instead on performance, performance, latency and latest runtimes. And performance.
-
-
Seems like whichever provider keeps pace with the latest node releases will gain market share. AWS has left an opening for GooG/Msft.
1 reply 0 retweets 1 like -
Replying to @southpolesteve @hichaelmart and
Nah... latest version of Node won’t save GCF or AF... current versions have loads of problems... in their defense they are reimplementing both
4 replies 0 retweets 0 likes -
Replying to @IamStan @southpolesteve and
AWS will be solving this soon, and even community fixes for getting Node 8 is mostly a matter of effort vs impossibility.
2 replies 0 retweets 1 like -
Replying to @ewindisch @southpolesteve and
For me the big advantage of Node 8 is an updated V8 and the performance improvements there... I’d still stay away from async/await for a bit...
1 reply 0 retweets 0 likes -
Replying to @IamStan @southpolesteve and
We have people using them at IOpipe with babel. My issue with babel is uncertainty of performance impacts and losing control over the ability to optimize code. But then, I'm an old school ANSI C vet.
2 replies 0 retweets 1 like -
Replying to @ewindisch @IamStan and
I've gone all in on async await. Highly recommend.
1 reply 0 retweets 2 likes -
All my code uses libraries that contain "blazing fast" in the readme. Enough said. No benchmarks required
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.