News for hackers. Stuff that matters.

A comment on Memory usage of a toy C# server and client with 500K concurrent connections on. Parent comment

Re:Memory usage of a toy C# server and client with 500K conc... by roganartu on Saturday January 26, 2019 @04:53PM (#19008747)
> Javascript has it now but you need to be use libraries which support it too

This applies just as much to Python asyncio so I'm not sure it's a good suggestion from that perspective. You can use an executor to wrap things that don't support asyncio but that doesn't really qualify as good asyncio/await imo.

[ Parent | on HN ]
Re:Memory usage of a toy C# server and client with 500K conc... by nicoburns on Saturday January 26, 2019 @05:14PM (#19008869)
Yes, although it also applies to C#... so it doesn't actually make much sense as a criticism. Although I guess maybe there was a point in time where Node libraries hadn't all transitioned to Promises yet.
[ Parent | on HN ]
Re:Memory usage of a toy C# server and client with 500K conc... by lkschubert8 on Monday January 28, 2019 @07:30AM (#19016941)
I still see a fair amount of node libraries that either haven't converted to promises, or their documentation makes it unclear if a function with a callback has a promise based alternative.
[ Parent | on HN ]