Isn't this anti-news? I vaguely remember they have stopped introducing leap seconds until further notice because they cause too much trouble with today's computing systems. On my phone now and did not research it, as I say vaguely remember. Now we are 37 seconds off. Nobody of us will have to worry that Christmas is around Easter time. We can leave that problem to future generations much more responsibly than many other problems.
That the notice comes every 6 months is just to meet the letter of the original international treaty.
I have a German bank sccount that can be used with a standalone code generator, that uses the chip on your bank card.
I have a Finnish bank account that use a completely standalone, purely time-based code generator.
Alternatives exist. But with current know your customer requirements it's increasingly difficult to open new ones if you are a foreigner and/or non-resident.
In Finland many news outlets had the same headline, but needed to correct it. It's the last big operator who closed their network. There are still a couple of smaller local operators that have not yet stopped. Finland traditionally had many local phone companies and a few have obviosly survived.
Yeah, 2010 CDs were still pretty visible. Not sure how many people still ordered them, but at least they were always distributed at events. Don't remember when it started to no longer fit on a CD.
Well written. But does not change the fact that Microsoft acts as an ugly monopolist in a user-hostile and developer-hostile way in their market space. And delivers at most mediocre products.
This text repeats things that I have read many times before, maybe
because it's heavily AI assisted as other have suspected. But it fails
to answer my questions I have had unanswered for years.
Q1: Let's start with a single core machine. The explanations always say:
The scheduler does this and does that. As if the the scheduler would
be some external entity. In the single core machine there is only one
actor. The core that executes instructions. One after another. Where
the next one is either determined by the program counter or an
interrupt. I would really like a text that never changes
perspective. It's the CPU that does things (sometimes it executes code
belonging to the scheduler). It's never the scheduler that sits there
in an outside supervising position and can do things.
So lets take this pure user space while(1) task. The CPU jumps into
the timer interrupt code. The article says a flag will be set, but the
real preemption will happen later at a safe spot. So what code is
executed after the flag has been set? Where and how will it notice
that now we are at a safe spot to preempt?
Q2: The multi-core case. All texts write about "the scheduler". As if
we had n cores and 1 scheduler that supervises what they are
doing. But that's certainly not what is happening. I guess all cores
execute some scheduler code regularly (except the tickless ones, but
that's yet another story and rare on a "typical" machine). But how
does that work without creating a mess in the data structures? Well,
some synchronization primitives are probably needed. But how does that
scale for dozens and 100s of cores? I guess most structures are local
to a core and the global ones are modified rarely?
Maybe he doesn't. And I know that I don't (at least not in depth). And that's the frightening thing here. Using a protocol that many don't understand for access to valuable resources
Your 5 year old iPhone has how many cores, how many GBs of RAM?
I would need to search the specs, but a N95 has 1 core and well below 1GB. A factor of dozens in the specs, but still you can get good user experience on the old devices if the software is written in a smart way.
The lower resolution of the N95 acts in favor of performance. But admittedly against user experience.
Nice. But unfortunately these addresses are hard to remember and "nobody" recognizes them when reading examples. One of those "standards" that have been a great idea, but lack practical relevance.
We used Clearcase around year 2000 on HP-UX. I found it nice and powerful, but 90% of the developers did not understand it. Well, probably a similar statement holds for git.
Yes, Cloudflare. It says: Your browser is not supported. Use another browser or upgrade. I would upgrade if the vendor of this weaker embedded device provided something...
I know Cloudflare works fine on Firefox desktops and probably also on Android.
Sorry, I should proof-read my comments... Can't edit it anymore
It is not necessary to use cash anywhere because cards can be used really everywhere.
But if you don't want to use cards, it's still possible to avoid it for weeks in row. You can pay cash at most brick and mortar places and by bank transfer at most online sites.
That the notice comes every 6 months is just to meet the letter of the original international treaty.