Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
nrjdhsbsid
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
40 ms
·
151.
▲
by
nrjdhsbsid
10y ago
Java and c# manage threads+async just fine. You're overestimating the difficulty of using then together. In practice you just add the word async or await and go about things normally like in node. Js is single threaded because it was d
152.
▲
by
nrjdhsbsid
10y ago
Single threading was not intentional. It's because they used js, now they're trying to sell it as a feature. They've tried to implement threading several times but it's a huge change to the V8 engine and js isn't de
153.
▲
by
nrjdhsbsid
10y ago
That's just not true. With SSD's and cheap ram less time than ever is spent waiting on IO. Almost everything these days is CPU bound and it's only going to go more in that direction as the speed disparity between storage and
154.
▲
by
nrjdhsbsid
10y ago
Fortunes is not IO bound. Plaintext bench definitely is and node is around 8x slower than the fastest frameworks. Node is nowhere near raw netty performance in most situations and will never be. Js is single threaded, dynamically typed, an
155.
▲
by
nrjdhsbsid
10y ago
I feel you. My god js is still horrible. Why anyone would willing develop more than they have to in it is beyond me. Yeah we have ES(x) coming and typescript and node yay! All of the stuff coming to js has existed in better form in other ma
156.
▲
by
nrjdhsbsid
10y ago
Yeah but I doubt it will ever hit parity with c#/Java/go. The lack of static typing and other fundamental languages choices will keep it from ever being as fast as those. V8 and friends were built out of necessity not because js w
157.
▲
by
nrjdhsbsid
10y ago
Also still no multithreading, which causes callback hell in the first place
158.
▲
by
nrjdhsbsid
10y ago
Is this flamebait lol?
159.
▲
by
nrjdhsbsid
10y ago
It is non trivial to share state between node threads. The state is shuffled around outside of the VM unlike go, Java, and c#. In those languages, the overhead of sharing a variable are basically zero. In node you get sharing at basically t
160.
▲
by
nrjdhsbsid
10y ago
I beg to differ with node being the "best choice" for IO intensive ops. Java performance will be better on IO as well, as long as you're using NIO or something like EPOLL native bindings in Netty, which is asynchronous like n
161.
▲
by
nrjdhsbsid
10y ago
Just moved out of Chicago. Would not recommend. Besides the north corner and downtown the city and state are broke poor and crime ridden. Enjoy your insane taxes without much to show for it. Chicago is notorious for corruption and the massi
162.
▲
by
nrjdhsbsid
10y ago
Nonononono this is a horrible idea. Vanilla js is the whole reason all these frameworks were created. I guess if you don't care about the 1000+ hacks and workarounds to make your code everywhere you're right. Might as well call it