Javascript is a dogshit language that everyone is stuck with. The best that we can hope for is the likes of typescript take the edge off of it. Even though it’s like smearing marzipan over a turd. At least it’s ok if you don’t take a deep bite.

Stole it? I think adopted is more apt. And curry isn’t one thing and varies from region to region in India. But Britain loved it so much that there is an Indian (or Pakistani) restaurant practically everywhere. And while Indian / Pakistani chefs have invented new dishes (e.g. chicken chasni is the best goddamned curry ever), I wouldn’t call it cultural appropriation.

British people love curries and other spicy things. For most people curries, biriyanis are going to be in the rotation. Even “traditional” British food will usually have things like black pepper, nutmeg, mace, ginger, cumin, cloves, mustard, bay leaves, juniper berries in it. More recently cumin, paprika, tumeric, coriander, curry powder might be thrown into dishes.

The clue was in “user facing bits”. UTC represents time as an absolute. If you want to show local time, or deal with daylight savings you run UTC through a function on its way to the user.

ISO 8601 goes from 1582 (Julian calendar adoption) but can go even further with agreement about intention and goes down beyond the millisecond. Not sure why I want an integer from the year 2000 which only represents seconds.

The sane way of dealing with it is to use UTC everywhere internally and push local time and local formatting up to the user facing bits. And if you move time around as a string (e.g. JSON) then use ISO 8601 since most languages have time / cron APIs that can process it. Often doesn’t happen that way though…

So people most familiar with a system have an affinity to it? Colour me shocked. I expect Windows users would want to return to Windows for their own reasons.

AI is certainly a very handy tool and has helped me out a lot but anybody who thinks “vibe programming” (i.e. programming from ignorance) is a good idea or will save money is woefully misinformed. Hire good programmers, let them use AI if they like, but trust the programmer’s judgement over some AI.

That’s because you NEED that experience to notice the AI is outputting garbage. Otherwise it looks superficially okay but the code is terrible, or fragile, or not even doing what you asked it properly. e.g. if I asked Gemini to generate a web server with Jetty it might output something correct or an unholy mess of Jetty 8, 9, 10, 11, 12 with annotations and/or programmatic styles, or the correct / incorrect pom dependencies.

Sometimes when I’ve torrenting from a public wifi I’ll get a malicious .scr file - but since I torrent from an Android phone it can’t do anything to me.

And downloading updates is a good thing. Means that the fresh installation isn’t vulnerable to something that was fixed between when the USB / DVD was pressed and the time the person installed it.

Linux has made leaps and bounds with usability and ease of installation but it’s no better than any other modern OS - which is a good thing. Installing Windows from a USB stick is not difficult - the simple path is literally, pick a language, select your wifi, choose who is logging in, click install and go grab a coffee. About the only difficulty if you can call it one is that some installs will ask for a serial number because it’s a commercial product.

Also, the number of questions & buttons during installation is one thing but the certainty of a functioning system is another. Linux is better at supporting old hardware, Windows is better at supporting new hardware. Choose accordingly if that matters.

I don’t even know what this graph is even supposed to mean. Bitch about Windows all you like but the installation process is typically very simple.

It doesn’t work like that. UTC goes forward always. Leap seconds are scheduled and known in advance. NTP time services will just smear time advancement a little to account for an additional second. Time never has to go backwards. This is how Google does it.

Leap seconds still make time go forwards, not backwards. NTP clients would also resolve small time discrepancies while still advancing forwards prior to the next time sync.

I didn’t say Unix time, I said UTC. And no it won’t report negative time, not unless somehow the system clock was modified while it was running…

UTC always goes forward regardless of the timezone and local time. That is why you should use it. To take my EPG situation above, I stored program start / end times in UTC so they would render properly even if DST kicked in or not during the middle of the program.

Yes as long as the rules are known, but it’s really just better to do things sanely and leave no margin of doubt.

True but so do most computers. Computers have a database of timezones and time offsets around the world. Depending on the UTC date and time, and your current timezone it will look up what offset to apply to show the local time. The database is very gnarly since rules change over time, e.g. maybe in the 70s some countries had longer DST to counteract oil shortages.

I once developed an electronic program guide for a cable TV company in New Zealand and I’d lose my mind if I had to use timezones. The basic rule of thumb was:

a) Internally you use UTC religiously. UTC is the same everywhere on Earth, time always goes forward, most languages have classes that represent instants, durations etc. In addition you make damned sure your server time is correct and UTC.

b) You only deal with timezones when presenting something to a user or taking input from a user

Prior to that I had worked for a US trading company that set all their servers to EST and was receiving trades through the system which expressed time & date ambiguously. Just had to assume everywhere that EST was the default but it was just dumb programming and I bet to this day every piece of code they develop has time bugs.

Rust isn’t really OOP like C#, Java or C++ - it has structs with functions that you could consider an “object” but there is no inheritance. Instead Rust uses traits which are a little bit like interfaces in some languages.

The way the kernel is using Rust at the moment is to produce safe bindings for modules to be written in Rust, i.e. you can create a module in Rust source which will be correctly loaded up, the code is safe by default and will have access to kernel services via bindings. I expect over time that more of the kernel will become Rust, but the biggest impediment right now is Rust relies on LLVM and LLVM only supports a subset of targets that a kernel could potentially support with another compiler like gcc.