Apple pages are _completely_ unusable because of this. If I go to product page I am unable to navigate it to extract information about the product. I give up and leave.
Try to skim this page to get a sense of how much information is on the page. You can't. 90% of the scroll time is stuck in useless animations.
Every time you scroll down you have to wait for the page to render. We've somehow recreated the dialup experience with single page apps.
Your brain is trained on how scrolling works on 95% of pages. Breaking that patterns causes tons of cognitive overhead. You now have to do a double-take every scroll action when you just want to absorb the contents of the page.
I get your preferences, and I am tempted to agree with you because there is a lot to hate about Apple.
But… this website is an ad. It’s not a product spec sheet. It’s not meant for you. It’s meant for people who don’t know a lot about computers or the web, and it’s meant to make them feel something about the product. Its goal is not to present data clearly. And as much as we may hate it, it does a brilliant job at what it’s trying to do. I think dismissing that because you are too deep into the “right way to make websites cult” is so shortsighted.
Not really. The equilibrium of removing daylight savings will result in schedules somewhere between DST and Standard Time. This just gets you there faster.
The trade off of having 30-minute time zone offsets probably isn't worth it, but this solution isn't immediately "stupid."
Actually the only intelligent solution is to abandon discrete time changes to & make this a continuous adjustment. We need to adjust the clock continually, ongoingly, to appropriately track the light of the day.
While we're at it, everyone deserves 12h of daylight, so clocks should use exact position to automatically and continuously adjust so that 6:00 is always sunrise, 12:00 is always "high noon", and 18:00 is always sunset. :-)
Some will argue that the minutes should correspond to sun angles over the (eastern) horizon, so you know what kind of hat to wear for a given appointment time. In the tropics, you can have this 6:00..12:00..18:00 daytime a couple times per year. Elsewhere and elsewhen, your clock should asymptotically approach a morning time corresponding to the sun's zenith, then jump to the corresponding afternoon time as the sun starts descending again.
However, after a gathering of stakeholders, it will be determined that everyone can pretend to be at the right tropical latitude to have the sun pass overhead. We will simply add "grocer's quotes" around each clock display or written timestamp, indicating that it is aligned to a hypothetical high noon. Largely thanks to these grocery clerks, we'll never have to design clocks with correct asymptotic behavior for midnight sun and polar night observers.
Of course, the ISO timestamp format will also need to be updated, replacing the timezone suffix with a longitudinal coordinate. Many variants will be defined for using decimal degrees, degrees/minutes/seconds, or floating-point radians for this value. But most programmers will only bother to handle decimal degrees, and many will be lazy and use lookup tables. Clever hackers will decide to save space by discretizing with a formula like floor(longitude / nbins). After careful study, they will settle on the constant nbins=24.
Do you think the submitter intended this as an ad? His post history doesn't seem suspicious.
Or do you think article's author wrote this an an ad? He's a reputable academic who seems impressed with an AI tool he used and is honestly sharing his thoughts.
> Or do you think article's author wrote this an an ad? He's a reputable academic who seems impressed with an AI tool he used and is honestly sharing his thoughts.
Ghuntley used to be reputable on here, then the crypto money looked too juicy.
There are times when an em dash can be used in place of a semicolon, but I don't think that's the usual LLM usage. Instead it's replacing a replacing a comma, colon, or period.
Unless you're talking about restructuring your sentences to allow for a semicolon; that's fine.
For example that semicolon could have been an em dash, but I don't think it's the type that LLMs over favor.
My interpretation of LLM em-dash use is that it's like an aside, which is pretty much always going to be weird if converted to a comma since the punctuation was providing un-relatedness information.
It's hard to take complaints about UI consistency seriously when the cursor is changed for no reason at all (with a barely-different hover state, too).
Doesn't matter. Rich enough to afford most products, as pretty much the only market other than the US. And more people. Biggest addressable market for most things.
And yet Apple, Microsoft and Netflix make significantly more revenue from the US than the EU. It's almost as if the EU is not actually a bigger market.
You must never drive on a curvy roads then. Every car I driven waits until the approaching car is fully around the corner, blinding them for a full second before dimming, instead recognizing the headlights around the corner and dimming earlier.
Newer cars with matrix LED headlights account for this, such as the Volkswagen ID series. The brights not only "blot out" the shape of the cars around you, they also rotate when turning or going around a curve, so that you never accidentally point them at oncoming traffic.
It's quite magical and weird to observe in real time. When driving past oncoming cars, you can see a halo of darkness around each car. There are videos on YouTube that show the effect pretty well.
I don't even know what a Chevy Bolt looks like! Maybe the problem is every other model.
It's not hard to know when a car is approaching from corners / hills; there's light before they get there. I have fun manually adjusting the brights; I drive automatic transmission, lighting is the only fun I get.
https://www.apple.com/macbook-neo/
Try to skim this page to get a sense of how much information is on the page. You can't. 90% of the scroll time is stuck in useless animations.
Every time you scroll down you have to wait for the page to render. We've somehow recreated the dialup experience with single page apps.
Your brain is trained on how scrolling works on 95% of pages. Breaking that patterns causes tons of cognitive overhead. You now have to do a double-take every scroll action when you just want to absorb the contents of the page.
reply