![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
Not at all only. At times you have both IPv6 and IPv4 and other times you can still get IPv4 at no additional cost like when you run your own router or modem. The layperson will be given IPv6 by default, but it’s not the only thing you can get.
Not at all only. At times you have both IPv6 and IPv4 and other times you can still get IPv4 at no additional cost like when you run your own router or modem. The layperson will be given IPv6 by default, but it’s not the only thing you can get.
A fifth option there is
I find it unfortunate that the same line has different colours on each end. It would be much nicer to visionary see the path the lines take.
“Never” is a massive understatement. Especially in big cities, say Paris itself, it’s a nightmare to drive a car compared to just using public transportation. Even outside of cities it can be much nicer to relax on a smooth train ride rather than have to focus on driving the entire time.
Depends on where you live obviously.
The reason clocks use it, is to not make it look visually unbalanced. Most often they write 4 as IIII. I find it infuriating to break such a simple rule though.
But also, I’ve never ever seen VIIII.
Have you tried 7zip?
I think the comment was more about phases of the day. Like for example, your phone might come pre-installed with a sleep mode from 23:00 to 06:00, which roughly fits for most users. Should we use UTC everywhere, then you’d have to have different presets for different parts of the globe.
Or say you wake up just a bit after sunrise at 7am everyday and you fly across the continent for vacation. Now you have to change all your alarms because sunrise is suddenly at 3am.
Or what if you’re writing a book and you want to tell the reader what time it is: 15:00 will mean something else to readers around the world. And while you could attempt to cover it up with “15:00 in the afternoon”, there will still be a disconnect between your words/intentions and what the reader pictures.
UTC would be a bliss for programming and scheduling events in this funny little globalized world, but as animals we still base our days on the burning fireball in the sky and removing that connotation from our timekeeping messes with linguistics and clear communication.
I don’t think the system we have is perfect either, but I don’t think employing UTC everywhere is the way and I don’t have other suggestion either.
I’m in the niche of niches by using vsc with a vim plugin while being a dvorak user. I rely on vim’s langmap feature to get anywhere, but people implementing vim emulators blissfully ignore accessibility like that. So I went and implemented langmap in vsc’s vim plugin myself. It has minimal intervention into the existing codebase and a bunch of other people have been wishing for this for years. Yet, when it comes to merging… Silence.
True, but building the image is not the same as deploying to production.