That means you, like John Henry, are competing against a machine at the thing that machine was designed to do.
As I understand it, the difference is sports channels. Sportsball stars’ high salaries are paid from TV rights, and the subscription cost reflects that.
We don't police big tobacco very well on making their products more addictive. We seem to be fine with expanding gambling - where I live (not Nevada!) slot machines are everywhere. Nice restaurants even will dedicate corners to slot machines - not just seedy bars. Sports betting apps are all over streaming ads, and their legality is expanding even though when they are legalized in an area the divorce and loan default rates go up measurably.
Why would we regulate big tech if we don't bother with anything else?
The kids are just the latest victim of a long ongoing trend.
I’m pretty sure we do, in fact, ban under 18s from tobacco, alcohol, and real-money gambling.
> The paper had some profitable years under Bezos, sparked by the 2016 election and the first Trump term. But it began losing enormous sums: seventy-seven million dollars in ~~2013~~ 2023 [WaPo fixed this after posting], another hundred million in 2024. The owner who once offered runway was unwilling to tolerate losses of that magnitude. And so, after years of Bezos-fuelled growth, the Post endured two punishing rounds of voluntary buyouts, in 2023 and 2025, that reduced its newsroom from more than a thousand staffers to under eight hundred, and cost the Post some of its best writers and editors.
Note a report on another WaPo layoff, from January this year, describes a layoff as "nearly 100 workers, or 4% of its staff" [1] which would of course work out to 2500 employees.
'Newsroom' employees are journalists, editors, photographers, fact checkers, foreign correspondents etc; non-newsroom employees are jobs like ad sales, customer service, printing, distribution, HR, IT, legal, finance etc.
So the $100M loss isn't $125k per employee, it's more like $40k per employee.
Of course, given that the grandparent said "If they aren’t a crypto startup" - Axiom clearly doesn't apply.
The reality is licenses are all nonsense and none of it makes any sense. There could be secret patents nobody knows about. That precise wording written by American lawyers might not hold up in Chinese courts. There might be two compatible licenses, but one is 20x the length of the other; obviously some legal expert thought those extra words were needed - but are they? What's going on with linking and derivative works? Do you need to copy-and-paste the full legal blurb into every single file, or not? Why are some sections written in all caps, and does the reason for doing that apply globally? What if someone claimed to have the right to contribute code to an open project but actually had an employment contract meaning the code wasn't theirs to transfer? What's the copyright status of three-line stackoverflow answers?
The truth is nobody knows, and nobody cares. You and I won't get sued, probably, and if we do it's not like we'd have avoided it by reading the license. Might as well ignore it, like people ignore website terms of use and software click-through licenses and other legal mumbo-jumbo.
On the other hand, if you're the kind of gigantic enterprise that has policies on software licenses and a team of in-house lawyers and you can't use this software without greater license clarity? Well, you can get that licensing clarity with the enterprise version of the software.
According to [2] Uber drivers make $15 to $25 an hour, before expenses like fuel.
So while it's not normal it's certainly plausible that some people take taxis on a daily basis.
More broadly, as levels of wealth inequality rise in a given society, more people end up working in the personal service sector doing things like cleaning, food delivery, taxi driving etc.
[1] https://www.levels.fyi/t/software-engineer/locations/san-fra... [2] https://www.triplog.net/blog/how-much-do-uber-drivers-make
"I could make that in a weekend"
"The first 80% of a project takes 80% of the time, the remaining 20% takes the other 80% of the time"
Sometimes the start of a greenfield project has a lot of questions along the lines of "what graph plotting library are we going to use? we don't want two competing libraries in the same codebase so we should check it meets all our future needs"
LLMs can select a library and produce a basic implementation while a human is still reading reddit posts arguing about the distinction between 'graphs' and 'charts'.