alexhultman

8 ms·

31.
by alexhultman 9y ago
Can you find this notice in their distribution? I have looked in their client UI and in their client tar.gz but I cannot find anything. I can however easily find my project in there (I would think the license would be nicely placed where th
32.
by alexhultman 9y ago
They are distributing both binary (no problem here) and source (problem).
33.
Tell HN: Discord is violating open source licenses
91 points by alexhultman 9y ago|46 comments
34.
by alexhultman 10y ago
I agree, this is one single factor that is constant in all apps: your long kept sockets will require far less memory which directly impacts the number of long polling clients you can have. Having fast throughput is just a bonus.
35.
by alexhultman 10y ago
What I mean with this is that any connection (socket) in Node.js builds on net.Socket which builds on uv_tcp_t which together requires a significant amount of memory (bloat). A socket in the networking stack of µWS is far more lightweight (
36.
by alexhultman 10y ago
I definitely agree the Node.js universe needs to take a better look at using addons. My opinion is that one should only use JS for the application logic, which requires high productivity, and only (or mostly) implement core modules as addon
37.
by alexhultman 10y ago
The pipelining benchmark is identical to that of Japronto (another, very similar thing posted here on HN a few days ago). Japronto's repo on GitHub holds the wrk pipelining script used. I haven't had the time to add configurations
38.
by alexhultman 10y ago
> I've found it trivial to make Python perform on the order of dozens of millions of requests per second [...] No, no you haven't. This is not a cluster of servers, this is one single thread serving 1 million responses per se
39.
More than one million requests per second in Node.js(github.com)
255 points by alexhultman 10y ago|86 comments
40.
NPM's new search algorithm is still horrible(github.com)
1 points by alexhultman 10y ago|0 comments
41.
by alexhultman 10y ago
You don't consider a 60x performance overhead reason enough? And yeah, thanks so very much for flagging this post!
42.
by alexhultman 10y ago
WebSocket++ was written at the same time as Socket.IO and performs about 30x better. I give credit where credit is due. I also criticize projects where criticism is due.
43.
by alexhultman 10y ago
µWS is not a Socket.IO killer. In fact, you can use µWS as the low-level engine in Socket.IO. Sadly I cannot (yet) present the pub/sub benchmarks of deepstream.io vs Socket.IO but I promise you: it will be hilarious. Other projects tha
44.
by alexhultman 10y ago
My keyboard would wear out if I listed everything wrong with Socket.IO. Simply put: it is one of the worst pieces of software I have ever stumbled upon. And the ratio hype-to-quality is off the charts. It's success lies in the fact tha
45.
by alexhultman 10y ago
This is what happens when a GitHub repo accumulates critical mass: people just follow after with no critical thinking. It's like the emperors new clothes.
46.
by alexhultman 10y ago
Thanks, I just finished the Socket.IO benchmark and wanted to show my findings (both in relation to my own project but also in relation to the existing alternatives) Socket.IO is simply a tremendous fuck-up no matter what perspective you ha
47.
Why you should never use Socket.IO(github.com)
41 points by alexhultman 10y ago|25 comments
48.
Don't bother counting those stars(github.com)
4 points by alexhultman 10y ago|1 comments
49.
by alexhultman 10y ago
But can it run Crysis? ;P
50.
uWebSockets 0.11.0(github.com)
7 points by alexhultman 10y ago|0 comments
51.
by alexhultman 10y ago
That's cool. Yeah WebSocket++ is a really good project and I do respect the author (I used it as point of reference when building µWS). So if WebSocket++ beats all other implementations by a large margin then µWS would obviously beat t
52.
by alexhultman 10y ago
You can register callbacks to the send calls so that you can keep track of the built up "to be sent" message queue.
53.
by alexhultman 10y ago
I test the user space memory scalability by connecting 1 million localhost connections on the same machine. Btw, 1.3 GB is for the Node.js addon - the native server does 1 million connections using less than 300 mb of user space memory.
54.
by alexhultman 10y ago
If you don't like it, don't use it.
55.
by alexhultman 10y ago
uws is a reimplementation of the ws interface, using fewer resources and providing better throughput.
56.
by alexhultman 10y ago
Call me when you can get 1 million concurrent connections using 1.3 GB of user space memory with ws. Hint: at 500k ws consumes all memory in my computer and the GC stalls are constant. My system start to freeze and my mouse cursor is no lon
57.
uWebSockets 0.10.0(github.com)
123 points by alexhultman 10y ago|27 comments
58.
by alexhultman 10y ago
I don't get it, why would anyone follow the advice of someone that is not actually hired by Google? That makes no sense at all. "Follow me, because..... because.... I WILL SUCCEED". I've myself been interviewed by Google
59.
uWebSockets 0.9.0(github.com)
73 points by alexhultman 10y ago|7 comments
60.
by alexhultman 10y ago
That's sweet of you. Also, Node.js people will need Node.js 6.4.0+ for Windows support (until patches land in LTS).

More ›