burned.gif

Me 2

Yeah a "farmer" is not a literal farmer. It's slang for uneducated people aka peasants.

You are just digging yourself in a bigger hole :) Modern farmers are not anywhere close to uneducated peasants.

It's a poorly translated word written in a haste. A better translation would be "red neck" (I think?). This is translated from my inner Swedish thoughts and we don't have Californian wokeness here (especially not down here in Skåne). But instead of finding a new word I reformulated that section everyone is so upset about. It's fascinating how easy it is for internet people to assume worst intent in everything, and look for things to be offended by, rather than to read between the lines and adjust ones interpretation based on context.

If you read the section, applying context from what the project is about and where it is used, you should pretty easily grasp the overall idea that is: "compression sucks and is incredibly inefficient". It would be a much more interesting thread if people took that message and argued against/for it, technically. But now we are here arguing about some word usage that might be offensive if interpreted in a very literal way. Congratulations; we have reached peak cancel culture. I hope you enjoy it while it lasts.

You find what you look for. If you look for humble posts they are there to be found. But you don't want to, so you won't find them.

That's why the library ships prebuilt binaries with no dependencies at all. No compiler is even needed.

Thanks

Hey, thanks for uWebSockets!

This is not going to fit in a single comment :)

I've been a swimmer for 15 years and I had to get used to floating boogers and used band aids and I can just imagine how much dingleberry I have swallowed over time!

Node.js is very popular and some companies with lots of I/O still prefer JavaScript, they have their business logic written in it.

I have to agree... the fact is, Node isn't the best at anything in terms of raw performance and won't be. What it is, however, is good enough for almost everything.

Node/JS offer some serious advantages. An expansive ecosystem of modules for which to build applications quickly. A well-known scripting language that allows for fast development and turn over. A language that allows for less distraction and context switching when going from one layer to another in terms of full stack development. Allows for a complete feature set to be in a single language with less disconnect to the front end.

I won't say there isn't a place for other languages. I will say that applications created with JS front and back using Node as at least the direct API/middle tier tend to be up and running faster, and perform well enough for most tasks if horizontal scaling is already part of the overall design of the application.

It also does well for cross platform scripting and orchestrating CPU intensive tasks.

If it was just, "I wrote a custom network stack to make your Node apps run faster", that would be something, but Golang is completely irrelevant to the question.

That's a good title. Golang is referenced many times in the text though, it's even plotted in the two graphs.