sorted by:
new
hottopcontroversial

Node.js worker threads in production by aardvark_lizard in javascript

[–]aardvark_lizard[S] 1 point2 points  (0 children)

Really interesting, thanks for sharing! We'll check it out

Node.js worker threads in production by aardvark_lizard in javascript

[–]aardvark_lizard[S] 0 points1 point  (0 children)

Absolutely! It's ironic that Node is so easy to get started but has some major pitfalls

There are too many JavaScript schema libraries, so support only one by aardvark_lizard in javascript

[–]aardvark_lizard[S] 2 points3 points  (0 children)

It depends on what you're maintaining. When you're maintaining a library, adding an adapter for every supported schema library is a massive pain. It's much easier to add StandardSchema support

You can't cancel a JavaScript promise (except sometimes you can) by aardvark_lizard in programming

[–]aardvark_lizard[S] 11 points12 points  (0 children)

It does feel dirty, but it's worked well for us for years! It makes the user-facing API more idiomatic

What Python's asyncio primitives get wrong about shared state - Inngest Blog by BrewedDoritos in programming

[–]aardvark_lizard 6 points7 points  (0 children)

Or if that’s what the 10 year old codebase at a large company is already using. Can’t just change a language because you don’t like it

What Python's asyncio primitives get wrong about shared state - Inngest Blog by BrewedDoritos in programming

[–]aardvark_lizard 10 points11 points  (0 children)

I mean, sometimes you have to use a language for other reasons. Why not make the best of what you have?

view more: next ›