Why the New V8 Is So Damn Fast
nodesource.com
Why the New V8 Is So Damn Fast
1–10 of 237 posts
Re: Why the New V8 Is So Damn Fast
#2I finally got a real hacker with a very good reputation and integrity. He turned my life around with an excellent work. I told him about my low credit score and the negative reports on my card which took him two days to tidy up despite his busy schedule just like he told me. Truth be told, I paid little for a whole lot of service, telling the world about him is a way to balance up. You can reach him via DARKWEBZZ@NULL.NET
Re: Why the New V8 Is So Damn Fast
#3As an internet user, I really enjoy reading about all these performance improvements in V8 / javascript.
As a ruby developer, I'm insanely jealous.
Re: Why the New V8 Is So Damn Fast
#4As an internet user, I really enjoy reading about all these performance improvements in V8 / javascript. As a ruby developer, I'm insanely jealous.
Just use Express.js or Sails.js, they're 1:1 to Sinatra or Rails. Join us!
Re: Why the New V8 Is So Damn Fast
#5As an internet user, I really enjoy reading about all these performance improvements in V8 / javascript. As a ruby developer, I'm insanely jealous.
Just use Express.js or Sails.js, they're 1:1 to Sinatra or Rails. Join us!
Not true unfortunately. Rails quality unreachable for current js frameworks. Well, i hope situation will change in the future
Re: Why the New V8 Is So Damn Fast
#6Why can't V8 deduce that the order of keys doesn't matter? It's pretty nuts that just rearranging the keys from { x, y, z } to { y, x, z } would cause a slowdown.
Re: Why the New V8 Is So Damn Fast
#7Why can't V8 deduce that the order of keys doesn't matter? It's pretty nuts that just rearranging the keys from { x, y, z } to { y, x, z } would cause a slowdown.
You can't deduce that; you'd need to show that the object is never passed to for..in or Object.keys or similar to be able to avoid storing the insertion order.
They could change the representation to not be insertion order dependent, and store insertion order in a separate data structure, but that has its own trade-offs.
Re: Why the New V8 Is So Damn Fast
#8Earlier quoted context omitted.
Just use Express.js or Sails.js, they're 1:1 to Sinatra or Rails. Join us!
Not true unfortunately. Rails quality unreachable for current js frameworks. Well, i hope situation will change in the future
With 2.6 JIT Ruby should be much quicker this fall. It'll be interesting to come back around once they have method inlining.
Re: Why the New V8 Is So Damn Fast
#9I used to believe that javascript was slow, C was fast and that there was no way to change this because of the way that javascript is interpreted and not compiled. But the more I've learnt about the benefits of "on the fly" / "just in time" optimising compilers, the more I'm convinced this is the future of computing. Being able to use multiple threads and hence multiple cores simultaneously to optimise what is actually a single threaded piece of code is quite amazing. And then being able to write code that is insanely portable and optimised on any platform is great.You can take advantage of SIMD, hyperthreading, multicore, large caches... without knowing if they're available ahead of time.
Sure, you won't beat C for low memory devices or hardware that you have complete control over but for 90% of use cases javascript actually makes sense and can be the most performant.
Re: Why the New V8 Is So Damn Fast
#10As an internet user, I really enjoy reading about all these performance improvements in V8 / javascript. As a ruby developer, I'm insanely jealous.
Just use Express.js or Sails.js, they're 1:1 to Sinatra or Rails. Join us!
Unfortunately Sails is nowhere near as good as Rails. Which is kind of strange given the size of the JavaScript community, and the fact that PHP has Laravel and Python has Django, both of which are comparable to Rails.
Amusingly given all the PHP hate, if you want a faster rails-like framework, Laravel might be your best bet.