a couple years ago it felt like the iPhone just worked. currently, it's so buggy i can't ignore it. some of these which i encounter every day:
- screen is dimmed when unlocked, then after a minute or so, goes to normal brightness
- touch screen does not work when receiving calls, so i can't answer. same for alarms, where i have to use the volume buttons to snooze the alarm, then touch starts working so i can manually clear it
- alarms not going off, or just being silent. so many time's i've woken up next to my phone being completely silent with the alarm interface being active
- keyboard not appearing sometimes causing layout issues
- using reduced transparency in Apple Music causes a huge empty area to appear in the bottom bar where the dynamic (?) "current song playing" appears
- rearranging icons on the home screen feel like it's a 50/50 chance moving the icon actually succeeds. the other half of the times, the icon just returns to where ever it was before
- re-arranging the control center do not register, or actions are delayed and makes it so un-intuitive what is going on
some design things which are intended which annoy me so much are:
- plugging in a charger will force show you the battery, so you can't use your phone for a few seconds
- hold and dragging the keyboard spacebar to move the cursor has some delay until the keyboard returns to normal, and tapping the spacebar again (when i need to place a spacebar) resets the delay
iMessage and AirDrop is so convenient, and the integration with AirPods is super clean. i would really like to continue using iPhone, but every day i feel somewhat depressed over how laggy iOS is :(
> Although our investigation is still ongoing, our early review indicates that your personal data has been accessed, which may include:
Identity information:
> - first name, last name, date of birth, gender;
> - Contact information: email address, home address, telephone number, if provided;
> - Passport information: passport number, country of issue and expiration date (not including copies of the documents).
A pair of mathematicians are sitting in a park chatting. There’s a snack shack near by, and while they’re talking, three people walk into the building. Some time later, four people walk out, and another couple walks in. A bit after that, two more people walk out. One of the mathematicians notices this and comments to the other, “you know, if one more person walks into that building, it’ll be empty.”
AWS just renamed their Security Hub service to Security Hub CSPM and then created a new service named Security Hub that is related but completely different than the original service.
And there's AWS S3, and there's AWS Glacier. And there's AWS S3, Glacier storage tier, which isn't Glacier. Which is OK, because Glacier is going away, and you should use S3, Glacier tier. Unless you're already using it, in which case you can still use it. So you still have to know Glacier and Glacier, while both storing your data, aren't technically the same thing.
But if you think that's bad, you haven't seen the name change shenanigans Microsoft pulls in Azure.
Maybe not in a few thousand years, but given the deceleration of the Earth’s rotation around its axis, mostly due to tidal friction with the moon, in a couple hundred thousand years our leap-day count will stop making sense. In roughly a million years, day length will have increased such that the year length will be close to 365.0 days.
I therefore agree that a trillion years of accuracy for broken-down date calculation has little practical relevance. The question is if the calculation could be made even more efficient by reducing to 32 bits, or maybe even just 16 bits.
The calendar system already changed. So this won't get correct dates, meaning the dates actually used, past that date. Well, those dates, as different countries changed at different times.
Wouldn’t it be accurate for that as well? Unless we change to base 10 time units or something. Then we all have a lot of work to do.
But if it’s just about starting over from 0 being the AI apocalypse or something, I’m sure it’ll be more manageable, and the fix could hopefully be done on a cave wall using a flint spear tip.
And count Planck time instead of seconds.. it's not as impossible as it may sound. You'll need more than 128 bits but less than 256 bits even if the epoch is the Big Bang (I can't recall exactly how many bits are needed, but I did the math once, some years ago). And it'll be compatible with alien or future time systems too, in case what we call a second (currently defined by caesium-133 periods) changes.
obviously not related at all, but enough to make me go "hm, this looks familiar" :)
reply