My deaf father ALWAYS has his phone in speaker: calls, fb, youtube, you name it. Luckily, I was wise enough to give him a phone with a 3.5mm port and several corded headphones. He sometimes remembers to grab a headphone, other times I slip it by his loudspeaker when he is not paying attention.
That is at home. On the street he prefers to eat alone in a table than mind the volume.
I'd rather have it switch than do permanent DST. It's not good to wake up in total darkness if you can avoid it. Best would just be permanent standard time.
I'd rather have it switch than do permanent standard time. It's not good to end your workday in total darkness if you can avoid it. It's nice to wake up in early darkness and see the sun rise. Best would be permanent daylight time.
It’s always this argument with people, all totaled up against people’s overall health - as pretty much every sleep scientist agrees, kids actually being able to get to school because it’s not too cold (not to mention safety as far as light goes), and making night owl’s lives hell.
But yeah, you definitely need to drive home in the light instead of the dark for those two months out of the year or whatever. Definitely worth it.
I'm a night owl and daylight time does not make my life hell, kids don't walk to school in the US anymore, and yes, experiencing the daylight for 2 more months of the year is worth it.
Ok, well, I'm a night owl and it makes things significantly harder for me, and pretty much every single teenager in the US to boot. Kids don't walk to school, but they do wait for school buses. Late starts are already common in northern states due to cold, and some kids do in fact still walk to school in the morning, and that's way more dangerous in the dark.
Yeah, being awoken by an alarm in pure darkness is grim which, longitude 15 solar noon minutes west of where our timezone is set and at our latitude is very possible in winter.
With pure standard time we would never have sunset before 5 pm but daylight savings puts half the year's 7 am before the sun has risen, and if you are an early riser as I have become, before the dawn breaks.
It also gives us four months where it's very hard to get children to sleep after 8 pm and for me it's even hard to start winding down.
I think summer time is really non-optimal for most purposes, changing the clocks sucks, and most individuals that work do so for too many hours a day. It's a local maximum in terms of how we socially manage time and people mistake optimising our society towards it to be optimising towards a global maximum.
Imagine if there was no DST and someone said "let's change every clock...", I would think it's a classic XY problem.
I have lived at high latitudes and agree; funnily enough around that time of year fog and cloud cover often meant no sun even if you were out during the day, records of 62 days with no sight of the sun. Crushing stuff.
But the situation you describe is literally not physically possible where I currently live due to proximity to the equator and being west of the line of longitude our clock runs on during standard time, but DST demands we wake up in darkness.
How the workday in the modern economy is fundamentally unjust. You shouldn't have to sign away your ability to see the sun for a job (unless at extremely high latitudes or extreme weather conditions).
It's not a huge problem. Uuid adds convenience over reinventing that wheel everywhere. And some of those wheels would use the wrong random or hash or encoding.
You're talking about the hash-based UUIDv3/v5? I haven't found examples of those being used, but I'm curious.
Using MD5 or 122 bits of a SHA1 hash seems questionable now that both algorithms have known collisions. Using 122 bits of a SHA2/3 seems pretty limited too. Maybe if you've got trusted inputs?
I use these a lot. My favorite use case is templates, especially ones that were not initially planned in the architecture.
Let's say i have some entity like an "organization" that has data that spans several different tables. I want to use that organization as a "parent" in such a way where i can clone them to create new "child" organizations structured the same way they are. I also want to periodically be able to pull changes from the parent organization down into the child organization.
If the primary keys for all tables involved are UUIDs, I can accomplish this very easily by mapping all IDs in the relevant tables `id => uuid5(id, childOrgId)`. This can be done to all join tables, foreign keys, etc. The end result is a perfect "child" clone of the organization with all data relations still in place. This data can be refreshed from the parent organization any time simply by repeating the process.
I remember using them in a massive SQL query that needed to generate a GIS data set from multiple tables with an ungodly amount of JOINs and sub-queries to achieve ID stability. Don't ask :p
For those ~~curious~~ worried, no, this was not a security sensitive context.
Common one is if you want two structs deemed "equivalent" based on a few fields to get the same ID, and you're only concerned about accidental collision. There are valid use cases for that, but I've also seen it misused often.
v7 rough ordering also helps as a PK in certain sharded DBs, while others want random, or nonsharded ones usually just serial int.
Serdes time can be significant. There are use cases for the zero copy formats even though they use more space. Likewise bit-packed asn1 is often slower than byte-aligned.
Remember it's the first derivative. The title and chart suggested at first that there are fewer tech jobs vs the start, but really it must be way more.
I still kinda want to see this going back to 2000. That must be the biggest tech crash by far. 2008 and 2020 were overall market crashes, but tech was booming.
Pretty sure protobuf used a header to track field presence within a message, similarly to what this article does. That does have its own overhead you could avoid if you knew all fields were present, but that's not the assumption it makes.
reply