> It is commonplace now that young people at the workplace produce 5x as much as their older colleagues.

This does not sound connected to any reality I have seen, and seems facially ageist.

I don't think that is true for older workers living today, but it was true on the 50s. The GDP per capita went up by more than 4x and yet it is those 50s people who have had an easy time owning a home.

Call it what you want. I see it all the time. And not many new slacker type jobs are being made, for young people to do the same. Every generation probably has the same percentage of people who don't do anything. The difference is that such a person who is young is a "neet" on unemployment, while such a person who is old collects a nice paycheck from a job.

SQL also turns 50[1] today, I think that it has much wider active usage today than many of its contemporaries.

[1] Archive of "SEQUEL: A STRUCTURED ENGLISH QUERY LANGUAGE" https://web.archive.org/web/20070926212100/http://www.almade...

It's great how the very first SQL query in that paper is still completely valid and runs on countless implementations:

> SELECT NAME FROM EMP WHERE DEPT = 'TOY'

I'm not sure how much funding they were getting from their partners, but one of the most tech focused on the list* was VMware who were recently acquired by Broadcom and have been going through a lot of cost cutting, perhaps this was one of the impacted areas?

* https://womenwhocode.com/about shows VMware, The Home Depot, DraftKings, Boeing, SiriusXM currently. Of those VMware is the biggest pure tech/coding company on that list (IMO).

The following page provides a good overview for the US https://www.uscourts.gov/services-forms/bankruptcy/bankruptc...

Your personal observation may be influenced by other factors.

Looking at this data from the US you can see that as family income increases, the birthrate drops - https://www.statista.com/statistics/241530/birth-rate-by-fam...

Interesting, I used https://ossinsight.io/analyze/JiaT75 to identify contributions from the account used by author of the backdoor. It looks like the account made other potentially problematic contributions to other projects.

The disabling of ifunc in this PR against Google's oss-fuzz project maybe one way they tried to prevent this particular backdoor being flagged by that tool? https://github.com/google/oss-fuzz/pull/10667

There is a related issue for LLVM/clang by this person:

https://github.com/llvm/llvm-project/issues/63957

I am curious, why don't this clever hacker create multiple accounts instead of only this "JiaT75"

With respect to:

> My guess is that this is a big-retail liquidation of devices Apple is ready to move on from, and not a new long-term price point. We'll see!

I think this may have staying power. It provides a nice way of selling to a lower tier segment without impacting their higher tier offerings. It provides an on-route to the Apple computing ecosystem for those on slightly lower incomes who would otherwise have to go with the equivalent Windows laptop. Winning at that level gets people deeper into the Apple ecosystem earlier, and more likely in the future to stay in that ecosystem if their economic situation changes (classic example would be budget conscious students)

Good points, and there is precedent right in the Apple ecosystem.

I think it's brilliant that "last year's model" (iPhone, iPad) drops down the good-better-best chain with every product refresh. No new R&D or tooling, still a great product.

There will always be a steady supply of last years' models. And customers to buy them. Apple just has to feel confident that a $700 M1 isn't cannibalizing their $1200 M2s or the upcoming M3s.

They are obviously not the only one, developers worked on the original code and made it available under the MIT license. The author of the PR has the right to make the change and run it on their own system, they are also free to share that change to others. The project is free to reject that change for whatever reason.

I am no fan of the syntax of SQL, however the authors solution of making SQL more procedural is (imo) correctly identifying an issue but then reaching for the wrong tool to fix it.

When I am authoring SQL, I find the declarative and relational concepts extremely powerful and well suited to the problem I am solving.

I agree with you.

Changing SQL to a description of how you'll get the data would make a query incomprehensible to me.

As long as I am allowed to write keywords in capital case I am fine with the syntax. I kinda like it. It smells like the 70s.

I enjoy how it builds on previous success WITH its use of regex. There is nothing quite LIKE ideas from the 50's haunting you in your sleep.

   SELECT age FROM Customers WHERE Country='Mexico'

Could be written something like:

   table.customers.filter(c=>c.country == "Mexico").age

The filter is kinda ugly, there is this strange assumption there to be only one Mexico in country.

Clearly the most advanced approach is this:

  //customer[country="mexico"]/age

1999!

Amazon provide multiple database offerings in their cloud, it was still a multiple year effort to move off Oracle:

  Migration Complete – Amazon’s Consumer Business Just Turned off its Final Oracle Database

  Today I would like to tell you about an internal database migration effort of this type that just wrapped up after several years of work.

https://aws.amazon.com/blogs/aws/migration-complete-amazons-...

I'm aware.