And the fact that you need to create a wrapper means that some programmers won't bother to do it, or won't know they need to do it. The default case handling timezones correctly will reduce potential errors.
Yoddel_Hickory
You should look at it, they say the implement RFC 9556 timestamps, which include tz info. In my experience it IS useful in real use, because a fixed offset timestamp can lose a bit of information.
For example, if you have a timestamp and want to add a few months to it, for example for a reminder, you will get a timestamp at the same time in the same offset. In many cases that will be wrong, because of things like daylight savings time, which change the offset of the timezone. You will get a timestamp an hour before or after the moment you intended, and it will be in the "wrong" offset in that timezone in that time of year. With timezone aware timestamps, they are aware that the offset will change, and will be able to give a timestamp in the future at the correct time and offset.
In this section, wouldn't be more realistic for
chrono
users to use timezone info around the wire instead of on the wire, rather than usingLocal
+FixedOffset
?
They do say that the difference is that chrono
users would need to keep out-of-band timezone information in addition to the datetime, whereas Jiff
does it in-band.
Termux, then you can navigate to the folder with cd
and list the content of the folder with ls
. You can save the output to a file ls > folder.txt
.
I have the 128 GB storage 8 GB RAM, it's still very usable. I often get annoyed with the small SSD, I'd assume 64 GB is way too small. Also if I remember correctly the 64 GB version has much slower eMMC storage, while the 128 GB and up have a real SSD.
There is a separate file you have to download, it's in the repo readme.
Yours is not at the top, so no longer true
Btrfs snapshots are great! All my filesystem is Btrfs, with subvolumes for root, home and var.
I'm using the Fedora immutable distros on many computers, it's great to be able to boot into a previous version of the system if issues arise. Not that issues arise, since most packages are installed as Flatpaks, in a toolbox or in a container. Makes the systems nearly unbrickable.
Yep, four of them, hence the "Q".
I think they meant the HTC entry in the article, not literally the HTC One phone.