bernawil

  The inclusion of lambdas has shaken things a little

OOP brought the terrible idea of coupling state and behavior, so of course "global state" would be wrong.

Later in the fourth century there were lots of shenanigans around securing the grain supply for the capital which in that period had shifted to north africa. I don't think we can rule out soil degradation as the reason for the shifts in the productive regions across ancient history, like how Paestum turned into a swamp due to soil erosion.

Still, my understanding is that php-fpm spawns processes, not threads. What is "persistent" is the php-fpm daemon itself that's connected to nginx, but each request spawns a whole process which has to bootstrap your whole framework every time. That's the reason frameworks like symfony run almost mandatorily with something like opcache.

  I once asked Rasmus about this face-to-face, during one of his presentations, specifically his thoughts about the pThread extension (https://www.php.net/manual/en/intro.pthreads.php), and he responded that it was not required in a web context, as web servers already have threads per request so its a mute point.

  pretty hard to proceed with some code that works with a DB when the connection can't be established, so proceed with what exactly other than error handling? 

  is a synchronous thread, as described above above. By design.

  Team members in low-wage regions being in golden handcuffs and sticking around because of the compensation even when they are unhappy.

  A concentration of team members in low-wage regions, since it is a better deal for them, while we want a geographically diverse team.

Honestly, the whole thing is just a huge rationalization. They could just have said "we adjust for location because we can".

  - this rubber bands make standard masks comparable to N95s!
  - and how do they compare, then?
  - mmmh, bad. Comparably bad.

  Most GraphQL servers you simply point it at a database and it automatically makes your entire schema, including tables and fields that shouldn't be exposed to end users, readily available.

Auto-generated REST setups are aplenty too, and lately auto-gen tools offer both gql + rest. PostgREST/PostGraphile. Hasura does both too.

Then it's all the same as of how much work. In the server, each REST endpoint is a gql resolver.

As of auto-generation regards: yes, gql maps great to a relational model, so you can save a lot of effort going that route. But you know, there's auto-generation for REST setups too.

> run any query on the client side" is a terrible idea

that's a big mischaracterization. A typed query language that lets you tailor your queries a la carte doesn't remotely mean the queries "run on the client side".

  I've literally never changed the database engine on a project

   const doThing = event => {
     input.value = event.value;
     input.focus();
     sound.play();
   }
   button.onclick = doThing

  In contrast, it doesn't happen with a denormalized, UI-agnostic state:

The choice is pretty simple to me: keep the State normalized, de-normalize it in selectors for consumption in the UI. Those selectors will look pretty much the same as the reducers you'd be writing anyway.

the lesson there is not to grandfather privileges if you want to actually fix something.

  Wealth is accumulated income tax

  so even if you expect an additional tax that grows at the same rate? 

I live in a country that has experienced inflation over the last ten years and the reality is that income taxes have followed inflation but property taxes not, because the government doesn't update property book values as often. The result is that you can hold very expensive property while paying very low taxes. But this also happens in lots of other places: California and Proposition 13 come to mind.

If anything it's a tax on income.

  These functions accept state and other dependencies

  When I see a function, I expect it to be side effect free.

  async IO creates a thread servicing that IO request

Now Java and C# are different because they are compiled. You need a DI tool to do dynamic dispatch if you want to mock.