skysight-inc/HackerNews huggingface dataset:
Scheduling tasks on a system is done using UTC/local time which the system keeps accurate. Unix time is not used for that.
1. Last time I looked no African country was part of the EU, so not sure how stricter controls for EU nationals works in your plan
2. The Uk wasn't part of the EuroZone so not really on the hook for Greece etc.
3. "a few hits to the City and London area aren't necessarily a bad thing" why wold you think losing one of the most Profitable parts of THE UK a good thing, it won't move to other parts of the UK, it will go to Paris, Frankfurt etc.
4. The average cost for ANY company of ANY size to now gain a sponsor license to employ non UK staff now starts at about £20,000, there are now not enough people to do many jobs especially in cities, labour costs (and now inflation) have risen out of control in many sectors causing closures and many firms are just outsourcing any non in-person to other countries. Yes, it would be great to give jobs to "locals" but not Everyone can do Every job!
Large cloud providers smear time. A day containing a leap second has the normal number of Unixtime "seconds" but each is 1/86400 too long. The inaccuracy this introduces is relevant to such a tiny tiny percentage of use cases; who already have to deal with the extreme complexities of time at this accuracy that everyone wins.
I messed up the wording on the above comment - I'm only skeptical of all the "performative charity" that you see on social medial.
A lot of articles from Josh Comeau are very good at explaining things and are quite interactive. Last one about CSS Flexbox for example: https://www.joshwcomeau.com/css/interactive-guide-to-flexbox...
Pity. There were some good ones there. I'm actually a bit upset about this one document that described data centers and network topology. I have it somewhere on one of my computers, though. And soon only I and a few others shall have it. Haha!
Blame Milton Friedman.
People keep repeating Ada 83 features, as if nothing has changed.

Ada has free() via "Unchecked_Dealocation", which since Ada 95 is hardly directly called, beacause the language introduced support for RAII via controlled types.

Many data types like strings and vectors are capable of dynamic managing memory themselves, thus no need for the malloc()/free() dance like in C.

When stack allocations, or other kinds of allocations fail from those dynamic types, an exception is thrown, that can be caught and the same operation retried with smaller sizes.

With SPARK integration into standard Ada, formal proofs can be used to handle how memory and other resources are being managed.

Finally, due to Rust's sucess bringing affine types into the mainstream, Ada is also having a go into affine types, influenced by ParaSail experiment whose author now works at AdaCore (not to forget the remaining 6 Ada vendors still in business).
I see leap seconds as regulatory capture by astronomers :D Basically it's convenient for them to have civil time (UTC) never more than 0.5s from UT1.
>The exact way Unix time handles leap seconds* is complex and an unnecessary detail for this article, but it will suffice to say that (i) whenever a positive leap second occurs, a timestamp is used twice, and (ii) if a negative leap second were to occur, a timestamp is skipped.

Huh, I always assumed that Unix time just ignores them and ticks forward. I get why e.g. UTC needs them but why would it make sense for Unix time to account for them given how it's defined.
Although the CIA would appreciate that and it's part of their smear campaign against Wikileaks, I don't think a leak website should wait with publishing dirt on country X until it has collected dirt on all other countries in the world. That would make no sense.
It's called "the intrinsic web". Things like flexbox and grid with content-aware sizing will eventually make the breakpoints obsolete.
https://adactio.com/links/19047
I mentioned nicotine because in my experience nicotine is much better at releasing dopamine than caffeine does, thus improves focus more than the other. Coffee raises other neurotrasmitters with a little effect on dopamine.

That said, coffee and nicotine are two stimulants that go and feel great together.

Before I was diagnosed with ADHD, I used to chain vape whenever I was coding or before bed to calm down. It had a similar effect amphetamine has on me: holds my focus and calms my mind down, but with noticeable side effects such as high blood pressure, pulse rate and a house that smells of smoke or papaya blast.
Sure I understand the bug, but when that service is also a DNS provider then it should understand that when I change the DNS record to $bar then I don't want it to route to $foo any more.
Similar to what rodauth did, or active-admin - extracting mountable, shareable and reusable parts of your app to a separate thing.
That was my thought when considering the difficult and impossible tasks of converting to/from UTC-based timestamps. If we accept that UTC is only for human use then we should also accept that humans can't tell the time of day down to the second just based on their circadian rhythm and the Sun.

Given a TAI-based timestamp a hundred years in the future we can be pretty certain in saying "yeah it will be around lunch time" (assuming there is no major changes in the solar system that would probably have such an impact on the lives of every human that nobody would care about this event anyway).
Why don't you use the word treatment?
Is the military fully hardened? Seems like they have some more hardening to do.

https://www.military.com/daily-news/2021/02/22/air-force-wan...
It should be up to the user what font they want to use.
Synchronization between computers is hard.
https://www.gnu.org/software/coreutils/manual/coreutils.html...
Could it matter for high-frequency trading? Since these trades occur in milliseconds, I presume trading being off by a second would be considered very damaging.
That, while possibly true, is a different problem than "This is because you are the product, not the customer. The customer is the record company paying to get their artists music into your ears."
This could be done. What would be the source of data? Would it be updated in real-time?
Certainly it's interesting that Mutex<T> is a thing in Rust but the equivalent (a mutex in the form of a wrapper type) doesn't exist in C++. One rationale is that Mutex<T> in Rust is actually safe, whereas the C++ equivalent would be an attractive nuisance since it looks safe but would be easily abused and if any of the mutex's users abused it you're screwed.
Like the biden laptop story. We must hide information that can be used by far right republicans to prevent Trump from being elected and starting WWIII with say, Russia. Did I get it right this time hn ? :)
Craig Murray, who I trust, claims to have collected the information from a DNC insider in the United States. Conveniently, the claims of “Russian hackers” was never actually investigated (although the claim was repeated again in the Mueller report), it was just an assertion from CrowdStrike.
I can agree with this statement: "HTML provides a pretty face, but a lousy system-to-system transaction environment."

Imagine if we had something like JSON, but with a more standardized schema to e.g. describe something simple like a table of data. There is so much glue code being written that does nothing else than reformatting data to something an organization can actually use. Think what it would mean if every table on the web would be fully adressable with an URI, such that you can directly load it into whatever you want - pandas dataframes, tableau, a C++ vector, Excel, your next fancy executive board PowerPoint chart, whatever. Make it n-dimensional from the start and give the shape plus each column a type definition. I guess one can dream...
> On the other hand my parents who live in the countryside 2 hours away from where I live will be just fine.

Until the "have-nots", who until recently were really enjoying being the "haves", turn up with their guns.

That's when it'll all get very feudal and very nasty, as the people with guns suddenly realise that not only do they have power, they don't have those laws that used to stop them acting out whatever violent fantasies gun-owners enjoy, and shooting people will probably be the least of it ...

Have a nice apocalypse.
By that you mean the US has managed to indefinitely imprison an innocent journalist to silence the truth they didn't like.
This is what I have installed at my house, it works well.
I'd be happy to, this is (roughly) my git config.

https://github.com/CervEdin/gut/blob/config/.gitconfig

NB, that some are personal custom scripts, like git-branch-status, which I also publish in the same public repository.

It's very much opinionated and geared to my use but feel free to use it, submit feedback and/or PR
And the constructive point?

First of all, of course Democracy has nothing to do with any supposed "absolute defense of freedom", because it is a system of attribution of power, involving coercion - because a fine line separates balance of interests ("politics") and actual coercion. So, of course, if one empowered inadequate individuals the rules will be absurd and damaging - and this has been actually happening, and it is not surprising at all to an etiologic analysis.

But second, soon after Hammurabi started his reign in minus 1792 of the typical timescale, already since the framework established those many millennia ago power is limited - constitutionalism is very old. So, not only it is already well established that some will be empowered, it is also well established that they will not be fully empowered.

There is no lesson that, in general, "power limits freedom": there is full evidence that the current systems need much more R&D. To note that, you already had e.g. gerrymandering, which is very graphic, or the failures in quality citizenship development - kind of the opposite of the hopeful depiction in "12 Angry Men" - which is very pervading.
Unrelated, I'm sorry, but it sparked a memory from back in the days (1998-ish) when there was a banner-ad-system that cost no money, but it only advertised web sites, not products.

Basically, it meant that you created a banner for your web site, somehow (I don't remember how) included in your web page, and the banner system would advertise your web site on other web sites using the same "technology", and vice versa.

Thanks for triggering that memory! :)
> that monitored keyboard activity, your desk presence (via movement sensors on the desks!) [..]

Hoooooly toxicity. Good to hear you jumped ship, that sort of environment can't make for a good working environment.
I guess that means we now need to visit the internet archive to find those documents?
The Variety article seems to be the source for this article, and it seems to make it clear that the 900 figure is the number of signed copies.

Did anyone seriously expect an 80 year old man to sign 900 books?

Wait until they work out the role of the ghost writer.
Who is behind this move? That is the important thing. States, of course, or people that work for them.
Clocks are out of sync all the time, so any code that relies on precise timestamps needs some way to account for out-of-sync clocks anyway.

So if you store two timestamps, you can't rely that the actual time that has passed between storing the two timestamps is equal to their difference, since the clock might have been slow, fast, or might have been synchronised with another clock between the recording of the two timestamps.

I think dealing with leap seconds should work in a similar way as working with other clock synchronisation issues, so I really don't see the point of adding new types of clocks in unix.
If Unix time ignored them, the conversion between timestamps and UTC would no longer be possible with just arithmetic operations. You'd need a list of leap seconds and take them into account. Now one can argue if this is better or worse than the current solution, but it's not without its tradeoffs.
That is just a lie pushed by western intelligence agencies, popular because it deflects blame for a well-known electoral defeat.

But I did not say they were above politics. On the contrary, they had very strong anti war, anti establishment politics, which they were credible about from their long public history as non-anonymous actors. (Which is also why we laugh at your unsubstantiated accusations that he worked for Putin.)

DdoSecrets will never have that. God knows what they actually believe. They don't think it's important that you know, at least we know that.
> I don’t get the cult thing. I encounter way more people who hate musk, often times irrationally than I do big time supporters.

These things are not connected, it actually makes no sense to say that. I know many more Musk haters than fans but at least 2 of the fans I know are definitely into the Musk-cult where they believe everything Musk does is great, that he has no flaws and any perceived flaw is just a tactic for him to get even further. They really do subscribe to the Musk 4D-5D chess stuff.

That's a cult behaviour, they are just into the personality of Elon Musk with no regards to his actions. The successful outcomes of Musk validates, to them, anything he does, like he is an infallible demi-God.

That's the cult thing.

Really not sure why you are conflating with how many hate or love him, there's no connection to that, at all.
and what is this favourite wine?
Can it find all
Implementations of an interface or what interfaces this implements ?
I’ve just googled the department store near me and looks like they had a “Great British fair” last year.

https://www.ukft.org/hankyu-great-british-fair-2021/

Another fair ran by department store this year:

https://www.mistore.jp/shopping/event/nihombashi_e/british_5...

I’ve never been to one so maybe looking up Japanese YouTubers might be your best shot for this topic.
Yeah, how dare the little people try to get paid! Getting paid is for international megacorps, not puny individuals.
How do you find these projects, are you part of some sort of discord about these things? I'm interested in joining!
I've found having a device (I use a remarkable) where you can erase writing without making a huge mess makes it easier to improve as well. I tend to speed up which ruins my handwriting or my mind moves faster than my pen and I end up skipping letters. On paper I would have to use a rubber and the page ends up being an ugly mess, which makes correcting mistakes very unappealing. Having an electronic devices rewards fixing mistakes, because the page ends up looking better afterwards, instead of worse.
I agree that for many use cases the exact second is irrelevant, like submission times and things likes that. That being said, programmers do seem to expect, for example, that code like `(int)time(NULL) - previous_time` works and accurately gives the difference in time between now and whenever `previous_time` was given its value. This does work, but only 99.99% of the time. Then it breaks 0.01% of the time. For bug-free code it's important that the expectations of the programmer are in line with reality, and the problem with Unix time is that programmers' expectations of the mathematical properties of Unix time and the real mathematical properties of Unix time do not line up. This is what leads to the countless bugs involving leap seconds.

The fact that accuracy is often not important is also crucial to my proposal of legacy Unix time, because legacy Unix time would eventually go out of sync with the rotation of the Earth just like TAI. In almost all cases this would practically be an aesthetic bug where dates in old user interfaces would be a few seconds off from the real date, and therefore not particularly harmful.
Laying out larger graphs is tricky, often because the size simply stands in the way of generating anything that's useful to the viewer. To add to that, most layout algorithms prioritize optimizing certain criteria, while other parts of the visualization emerge from that; and if the human viewer chooses a layout algorithm because of one of the latter properties, they are often surprised that the result doesn't look like they envisioned (because, hey, the algorithm optimized something entirely different). We see this disconnect fairly often in our own customer support, but I haven't really found a good way of putting an explanation in writing.

Then there's generally the problem of larger graphs, which tend to devolve into a tangled mess and hairballs, simply because they often tend to be well-connected. If there's no way of pruning them beforehand, or perhaps grouping, aggregating or clustering (in a way that makes sense to the viewer, not necessarily only structurally), then it can be hard to get good result.
"become" is a standard approach in Erlang, Akka and other actor model systems (because it is included in the original actor model axioms by Carl Hewitt, "[a message can] designate the behavior to be used for the next message it receives"). We write state machines with that (on some events, you just 'become' another state with its own reactions to messages).
They make these for hvac systems, mines installed in the air return, fully enclosed it works well. When the heat or AC isn't in use, I just run the hvac system fan.
sillycross, please consider adding a rss feed to your blog. People do still use those.
I think the article should not have left out the observation that in case you want to get to local time from UTC, you can only do so with certainty for the past, the present and the near future, because there could always be a change in daylight savings time (DST) regulations for a given locale. In my eyes that makes UTC a tiny little less useful for some purposes. OTOH human schedules should not be affected. Even for a country like [Egypt] which apparently has no issues with changing DST regulations with a mere few days of notice, meeting at 1:00pm in Cairo on some given day in the future will always mean whatever the local time stipulates it to be, come the day.

OTOH I believe that for computers, adopting something like TAI for all timestamps would probably a good thing. Re-adjusting display dates for the past where needed is much less complex wrt leap seconds than it is for time zones and DST. The conceptual simplicity of TAI and the invariants afforded by it come with the slight disadvantage that "the future can not be predicted", but we already cannot predict the future of countries changing time zones and DST dates, so we'd not be any worse off in that regard.

[Egypt](https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt)
We only remove the domain from Cloudflare when the content is deleted. The main reason is to avoid broken links when users update their domain on GitBook.

Ex:
1. You configure docs.mycompany.com with your GitBook space
2. You share links to docs.mycompany.com on social medias
3. You update the domain to docs.anothercompany.com
4. It's better if the docs.mycompany.com links can continue working until you remove the DNS entry

In summary, we want the users to decide through their DNS config when GitBook should serve the content or not to avoid breaking links without an intentional action from the user.

Unfortunately, because of how Cloudflare doesn't use the DNS configuration to decide where to route the traffic, it causes issues atm. We'll look at what we can do on our side to mitigate this.
EDIT: This comment was corrected by numerous replies below and the original comment contained incorrect information. Thanks to all posters for the corrections.

Original comment:

> The simplified definition of Unix time is that Unix time counts the amount of seconds that have passed since the first of January 1970 (which is referred to as “the epoch”, similar to the first of January of 1 AD being the epoch of the Gregorian calendar). This is of course not the complete definition, since it does not take leap seconds into consideration.

I disagree with the statement that UNIX time is not the amount of seconds since the Epoch. Leap seconds never happened, they were added to UTC and UTC only in order to correct it for sunrise and sunset.

If we started an experiment on 23:00 and ended it on 01:00 the next day, but a leap second occured in the mean time, the experiment wasn't running for 7200 seconds, but for 7199 seconds. The leap second had nothing to do with time counting, a stopwatch would not add a second to the reading.

If we started an experiment on Epoch, the UNIX time tells us the amount of seconds this experiment has been running. If we added 86400 leap seconds in between, the experiment would count real time, not our made up time. One day wouldn't be added to the count.

As far as I understand it, that's what UNIX time is, and there's nothing wrong with that. It's a feature.

Please add your opinion.
> I wouldn't be surprised if they saw this as equivalent to jailbreaking

The difference is that jailbreaking compromises the security of iOS. Whereas some clever apple engineer has setup the M1 MacBooks such that each OS is completely isolated from each other (enforced by dis encryption and the Secure Enclave). The only thing a rogue linux install could do is delete macOS entirely. But there would be little incentive to do so. Installing malware or stealing data is completely blocked.
> Java is unburdened with the prevalent and obsolete features of async/await, properties, and its generics allow a flourishing ecosystem in exchange for a minor inconvenience.

I don't quite get the "unburdened" part. C# now has records as well[1], and it always had List<Object>. It may also get stackful coroutines as an alternative to stackless coroutine.

You could say that C# now has to deal with a lot of legacy code that's using properties and async/await and cannot be replaced with "superior" records and stackful coroutines[2]. That's all true, but Java hasn't been frozen in vacuum for the last 20 and 10 years (respectively).

While C# programmers created mountains of legacy code with properties, Java developers churned out mountains of legacy code using "Beans" with getters and setters, auto-generated by the IDE or Lombok. That's strictly worse.

At the same time during the last 10 years, Java programmers that needed Async I/O didn't just sit around and wait for Project Loom. They wrote callback hells, and then moved on to CompletableFuture or a reactive programming style. And all this code tends to be a lot messier than Async/Await.

In short, real world Java developers are just as burdened as C# developers by legacy solutions that predate virtual threads and records, and the Java legacy solutions are usually quite a lot uglier.

[1] Although I dislike their decision of permitting mutability, their records they are at least useful right now, since we don't have to wait another 5 years to get a with expressions.

[2] I completely agree with you that immutable equality-based types are superior, and that mutable data types probably shouldn't be baked in the language. But I disagree with the stance that stackful coroutines are superior.
Oh, look how smart you are!
It's also great advice for playing music instruments. The slower you go, the better you learn
Edit: My original comment is incorrect. Please read child comments.

Original comment:

Yes, to convert from UNIX time to UTC, you do need a list of leap seconds.
yes, you are right. Unfortunately, I cannot edit my post anymore :(
It has been replaced by a Publish button in the latest release
I would say the underlying assumption is that the EU will want a free trade agreement (or some variation of one) with the UK for their own benefit. And considering the mutual advantages here I think this is a fair assumption to make.
The Economic Organization of a POW Camp (1945)
I guess they leaked what they had; leaks are not bipartisan
Since UV can be pretty hazardous I’d like to add this video (courtesy of the inimitable Big Clive) for your consideration:

https://youtu.be/2T39BHvrHZ0 (“How to use a UVC germicidal lamp safely”)