agrajag
Billionaires obviously get a disproportionate amount of income per year, but it’s far from 20% of all the world’s GDP. To make your math work that would assume they got all the wealth in a single year.
It’s a little hard to tease out how much of this is due to the demographics of Republicans and Democrats changing. There’s been a significant shift in education level between the two parties recently, and this may have offset some of what would otherwise be broad based decreases.
The broader decrease in faith in higher education is still quite clear signal though.
They might not be about to die, but they're not exactly healthy either.
This is true for anything that you buy. I’m not sure why being able to drive a car into the Manhattan CBD deserves special treatment. It also already has an excellent subway system that millions take daily.
You can’t means test virtually everything
It’s not 10,000x harder to patch that 10,000x more machines, but it’s not 1x either. Easily 10-20x harder, if not more.
We’ve had humans in orbit on the ISS continuously for decades, sent probes to the edge of the solar system, landed multiple robots on Mars, and revolutionized our understanding of space and physics with space telescopes.
The biggest obstacle to space exploration was a contracting that didn’t bring down costs, and the thing that makes space so exciting now is high cadence low cost launches
Tipping is only a thing because we’ve normalized it. If you pass a law against it, it’s no longer normal, and customers will mostly stop giving them, even without highly intrusive enforcement mechanisms.
The real challenge is getting a government to want to forbid it, because people who receive tips care about them a lot while those that don’t, don’t. Until you solve that nothing else matters. Maybe tipping will go so far that the balance shifts.
I’d be okay using someone else’s chromebook though, at least you know what data you’re giving it.
Sure, one page doesn’t matter, but thousands will.
[1] https://twitter.com/searchliaison/status/1689068723657904129...
[1] https://www.foodnavigator-usa.com/Article/2022/12/02/Amai-Pr...
The mentality that housing is an investment good has created a lot of perverse incentives (buy as much house as you can, you'll make more money!), that we really need to curb so that we can lower the cost of housing for everyone. Housing needs to be a consumptive good, where much like cars there's incentives to drive prices down and keep overall spending on the sector low.
Even over thousands of years when an hour of drift is accumulated there won’t be a manual adjustment - people will have just gotten used to different times of day having sunlight, with generations having been born and died with mean solar time happening at 11am.
Eventually the rotation of the earth may change enough that drift accumulates too quickly and leap time needs to be added, but that’s only going to be true thousands to tens of thousands of years in the future.
They’ll stop being CO and will never be promoted, but will finish out their Navy career in a job where they can’t hurt anyone, and will have almost no impact once they retire and go into civilian life.
They’re not going to do time in the brig unless there’s willful misconduct.
As for why life sucks so much, leadership has let there be too much to do with too few people, and inflexible systems.
A lot of this is directly attributable to the success of the Commercial Crew program.
TV is also very passive, but most content still requires thinking about a narrative for an extended period.
I hear the argument that we have to deal with this eventually to keep time in track with mean solar time, but the adjustments are so small that I don’t see any real impact on regular people.
From a software development perspective this seems monstrously more complex than just muddling along with the current situation even with leap seconds.
First, consider the question of "what do unix timestamps mean?" The answer is UTC, except just be broken during the second where there's an extra leap second added or removed, and don't try to represent it. They neither represent TAI nor UTC perfectly, and have no way to encode a leap second, but they are very space efficient to store needing only 8 bytes.
Now, we want to start converting our systems over to TAI, great! To do that we need a format to efficiently store a unix time in a binary representation. For this exercise let's use Jan 1, 1970, and so when we call it we get a value today that's equal to unix time plus 37 (the current offset between TAI & UTC). Awesome, now we need a new function to call it in every single language we use, and then migrate all callsites over to it. Try not to miss any places where someone's passing unix time as an int64 instead of, say, a time_t. If you call into libraries that return timestamps make sure you shim them so that you can convert those timestamps from UTC to TAI.
Now, we have the problem of how to store those int64s. We can't store them in place of our current timestamps, they'll be 37 seconds off. So let's add a field to all databases where timestamps are stored to store the TAI version. Additionally, every RPC is going to need to send along both TAI & UTC during the migration process, so change those too. We can't just ignore cases where we need an integer representation of time, either - those have historically been the places where systems break during leap second changes.
I hope this gets to a little bit of why it would be extremely non-trivial to use TAI in place of UTC right now. If you're storing your time as, say, a string representation with a time zone built in you're right, it's actually generally not that bad, and time zone information is frequently encoded in the string. It's _extremely_ difficult to deal with once you move to a representation of time where the timezone isn't directly encoded in a timestamp.
A major issue with Hubble & JWST comparisons is just that they're designed to look at different wavelengths of light. A lot of what JWST will see is completely invisible to Hubble, and no amount of observing time can compensate for that.