Yes, it is, because in your phrasing the fact that nobody else keeps time that way is the cause and lack of support in software the effect. The comment that I originally responded to is phrased as though lack of software support is the cause of weirdness.
I object to the latter since software is not the source of truth, the social practices it aims to encode are. It is perfectly reasonable to say that this particular practice is so rare that it is out of scope, but this makes tzdb a not quite correct approximation of reality, rather than reality an approximation of tzdb.
I agree with that take. It's also quite different from saying that it's weird because software doesn't support it, which is the claim I took issue with. Maybe I should've phrased my comment differently.
Maybe arbitrary was the wrong word. I understand that this is an implementation cost issue and I'm not saying that the decision not to pay this cost wasn't reasonable. My objection is not with tzdb, but with the characterisation of a real-life practice as weird just because software doesn't accommodate it. Shouldn't what people do be the reference for what is normal, rather than the rules encoded in software?
But whether standard software is able to express this system is up to the software, not the system, no? Why is this way of timekeeping weird, apart from the arbitrary decision not to support it?
Except it doesn't necessarily go towards (positive) infinity. Use a negative dividend, and you approach negative infinity instead. The same is obviously true if you use a negative divisor instead, and you get positive infinity again if both are negative. So division by zero is impossible because you can't meaningfully define it (in the general case).
Surely the logical pronunciation is the way you'd pronounce it in library, so a long 'ai' rather than any kind of 'i'? Though I personally always use the short 'i'. I was going to justify that by saying it's the same as /usr/bin, but that's also short for binaries, so should also be an 'ai'.
I believe GP meant that you can't have protocols containing numbers, using rot13 as the example protocol on port 76. Though, as msk-lywenn said, rot13 isn't a real protocol, which don't really have numbers in their names.
Who said anything about sticking anything into credit card terminals? And I'm not seeing any wires sticking out of the phone. I'd say it doesn't particularly look like a bomb either, but given recent events, that probably doesn't say much.
(Sane) web UIs in general should be fine, since they can just use the browser's JS engine. I don't think transmission is affected, at least it's not listed as masked.
You're right about firefox though, which is weird. Apparently node is a build dependency, but I can't figure out if that's something specific to the ebuild (that Arch's PKGBUILD does as well) or just generally something the buildsystem requires, but it's not listed as a dependency at https://firefox-source-docs.mozilla.org/setup/linux_build.ht....
147 packages don't strike me as that many, that's less than 1% of all Gentoo packages. I expected much more.
EDIT: And several of those packages are binaries. Apart from the *-bin packages, I've identified TeamSpeak, dev-libs/amdgpu-pro-opencl, Skype, and Slack. That leaves 138 packages.
Depending on your operating system, you might have (the option to remap a key to) a compose key. Then you can press compose followed by, for example, <= to make ≤. This also works for letters with diacritics on them, like "o for ö or 'o for ó, currency like =C for € or =L for ₤, or other symbols like tm for ™.
You might also be able to set up your own compose codes in ~/.XCompose, but that didn't work for me. Could be another casualty of Wayland or just some quirk in my setup.
The purpose of a business is whatever its owners want it to be. Typically, this is maximizing profit, but it could be anything, like getting paid for what you like to do.
> the foundation uses 5-digit dates to address the Year 10,000 problem
That just sets you up for the year 100,000 problem. The objectively better idea is to just parse years as regular integers, something that I'm confident people will figure out in the remaining 8 millennia until the problem actually hits.
At most a little over one year ago, I installed Signal Desktop to open a link in a message I had received on my desktop. This is, apparently, deliberately unsupported, since the app claims that "[f]or your security, chat history isn't transferred to new linked devices". So no, the user experience of WhatsApp is miles ahead of Signal, at least if you want to use a real computer.
Plenty of folk won't want adult content to show up in their search results. I'd wager that those that do are capable enough to check their settings, given that they should know concepts like safe search from google.
At least on old.reddit.com, underneath the searchbar is an expandable help section that, among others, explains the nsfw: search parameter. I'd hardly call that hidden.
Sure, that makes sense. Out of curiosity, do you know of any way to design a syscall ABI that's not C-like that was either used in the past or would have some advantages if a new OS adopted it? I imagine that lisp machines did things differently, but a) I don't know whether they had syscalls as such or simply offered kernel services as regular functions and b) they did have microcode support for tagged integers and objects.
I'm asking since I want to get into (hobbyist) OS development at some point and would love to know if there's a better way to do syscalls.