Off topic, I guess, but color me unimpressed by the guy claiming he would fire someone for rejecting a pull request that does nothing but advance a political agenda.
Color me impressed, because the political agenda that's being advanced is gender equality in technology, which to me seems pretty worthy.
I haven't seen the commit in question, but it seems like there's a balancing act here between gender neutrality and avoiding awkward phrasing. It's just an unfortunate fact of English that being gender neutral all the time leads to awkward prose. Sometimes readability wins.
There is a big advantage to node.js that used to be mentioned a lot in its early days, but not much now. The advantage is still there, but it's only noticeable if a developer has experience in other server languages. The big advantage is that node.js had an asynchronous development model from the beginning. This caused all the code written since then to also be written using async. When a node.js project imports othe…
Or you could just step over Node, and grab on to Elixir[1]
I think any serious projects should have a CLA, or require sign off like the Linux project does, and suggesting a change is the only way to get around having to deal with that. For known contributors, yeah, it's a nice feature.
Perhaps you could name some website/app servers that aren't mostly i/o (or event-timing) bound? I wouldn't say the use cases are limited at all. You can always run multiple process instances, and communication between processes isn't really so different in practice than inter-server communication... Which just means you are scaling horizontally by design earlier in development.
I worked on some web-based project management software which was highly CPU-bound. A typical scenario would be the application querying a database for financial figures, doing a large amount of calculations on those figures and then generating an HTML report from them. I imagine any application with large amounts of business logic like this will be the same.
I would suggest that what you are describing is the exception to the rule... Most queries, in such a case could either be done in the database or pushed to the browser... Generally if you're doing something CPU bound that isn't video processing or gaming, you push that out of process through a worker queue anyhow.