skysight-inc/HackerNews huggingface dataset:
This is the wrong direction, we should be on standard time year round! Daylight saving time gives you more daylight during the hours people are awake, but only because it forces everyone to wake up earlier!

We already have major issues with e.g. making teenagers wake up earlier than most of their bodies are tuned for at that age. How much worse is it going to be if they have to get up an hour earlier in the winter? (Remember: what our bodies consider "early" is dependent on when the sun rises, and not the numbers we put on our clocks.)

And just to top it off, you'll be forcing a lot of kids to walk to school in the dark.

---

Edit: To be clear, it's not just children!

On weekends and holidays when people don't have to work, how much of the population do you think wakes up right when the sun rises, in order to maximize their daylight? I certainly don't have any data on this, but I would guess a large majority take the opportunity to sleep in.

Having extra daylight seems really nice at first, and it is. Unfortunately, shifting clocks doesn't actually create more sun, it just creates a societal mandate. My view is that we already start our workdays too early, particularly when you take commute times into account.
I don't know. I'm pretty good with this change. There is abundant evidence of activism in certain scientific fields in the last ten years (particularly on diet). Verifiable data seems like an appropriate hurdle to me for expensive and disruptive regulation.
Epic "you had one job" story.
If you care about it, consider Purism laptops with a hardware kill switch for camera/audio: https://puri.sm/products.
Should we eventually reach the point where there is a shortage of vaccine stocks it might make sense to revisit. As things are going it doesn’t seem likely though.
> No security is absolute, but that doesn't mean all security is worthless.

I'm not talking about absolutely secure measures here, I'm talking about watered down security measures.

Just like encryption that has backdoors, weakening 2FA by providing ways around it by design makes it completely worthless. And remember that this doesn't just apply to one user - it affects all users of a platform at the same time if you allow nonsense like this.

There's no trade-off to be had there - you either offer a more secure identification method or you don't.

To put it in a different and simpler context: a safety gate has to have certain properties. If you remove one or more of these, it ceases to be a safety gate and becomes a regular door. A reinforced door with a cheap lock is just as insecure as a cardboard door with a security lock and a second key under the doormat or hidden under a rock outside invalidates the usefulness of even a vault door...
I wrote a long blog post about the VexRiscv RISC-V CPU and how its design methodology is radically different than traditional RTL languages.

The VexRiscv is written in SpinalHDL, which is a close relative of Chisel.

The advantage of SpinalHDL/Chisel is that it supports plug and play configurability that’s impossible with languages like SystemVerilog or VHDL.

You can read about it here:
https://tomverbeure.github.io/rtl/2018/12/06/The-VexRiscV-CP...

That said: there must be at least 50 open source RISC-V cores out there, and only a small fraction is written in Chisel. I don’t see how the use of Chisel has held back RISC-V in any meaningful way.
Almost a yearly tradition: https://www.congress.gov/search?q={%22source%22:%22legislati...
Well Norway is a fraction the size of the US in population.

I would imagine that wealth, cultural homogeneity, and a very small population accounts for at least 80% of the explanation. So not the “whole” explanation, but the critical mass of why it works, sure.

It’s questionable to assume that Norway’s system could scale up by a factor of even 3x, let alone something sixty times the size. I’d be interested if it could produce results in a country like Spain or France with 50m people before calling on the US to simply do what Norway does but with 350m people.
I'm guessing this is similar to the old reddit/new reddit situation. The new approach is better for the devs in some way (new user acquisition, maintainability, extensibility, user retention) but not for the long term users, and they don't feel they can jettison the old users so this is thrown out there to keep the most vocal from complaining too much.
I always love a good Matt Levine quote:

If your expectation is that if you invest in a good business you will make money, and if you invest in a bad business you can go to court and complain and the court will give you your money back, then maybe your job is a little too easy.
> the majority wants to have laws to drive up EV sales

It's a representative democracy, so it's the voted–in government officials instead of the majority of people ;)

The difference does matter, because the cause and effect is inverted: the government is elected... And now it passes laws such as this.

It's not the population that voted so the government would pass these laws.
Fiddling with the clocks while Rome burns.
CIOs Don't Have Skills to Digitally Transform Their Existing Systems
I just put an avatar that's not my face.
Honestly, I'd like it if it went down earlier; it's fun to have a drink outside in the twilight and night hours while still going to bed at a reasonable hour (which is around 10, in my case).

I can do that in the winter, sure, but in the summer there's a distinct lack of snow, which is nice.
People aren't codebases, a broken refactor manifests itself not as total societal collapse (a "crash") but slow social disease, with people arguing about the cause. To get everyone aligned, we need a law, not just to tell everyone to be flexible with each other.
Until Europe also switches to DST permanently, which will almost certainly happen if the US does it. I reckon if any developed country does it then all others would follow within a few years at most.

I hate that it's permanent DST, though. Why make noon at one hour past the sun at its highest point? So annoying.
The JWT launch and deployment is going to be terrifying. Peeking between my fingers for that one.
If I may briefly add a minor point: It somehow irks me that the Venn diagram on the landing page and in the icon are not the same orientation (they are rotated by 180°). Any specific reason for that? :)
Taper bedtimes 10 minutes at a time over a week!
:)... I am not so far north (49th basically) and it's dark by 4:40 on the solstice for us.

For the summer solstice though it's light out till almost 10pm
> Information overload will cause great harm and push people to the extreme ideology, as we've seen in social media (facebook, twitter, google etc.) the self-reinforced bubble

Now that we understand this piece of information, is the best way to solve the problem more information, or to forget that we ever learned it?
#[...] is an attribute, more like @foo annotations in Java, not a comment. Comments do not use # in Rust
> the only industry where I've heard of it being used extensively is finance.
> For live events like press conferences or sports this is already solved with broadcasting.

16 million people watched that press conference on BBC TV, broadcasting is very efficent at getting live pictures out. The BBC did experiment with multicast in the past, but CDNs seem to be a more scalable solution ironically.

However in this specific case, the pictures actually left downing street via multicast (SDI form camera into encoder, MPEG-TS over multicast to the studio, back to SDI to get encoded on whichever output chain it is - Terrestial, Satelite, Cable, online)

Indeed the standard to replace SDI (2110) is built around multicast, broadcast certainly uses multicast a fair bit.
Hours are interlinked across society. If you drive your kid to school, you need that to roughly line up with when you go to work. Maybe you don't have this constraint, but your coworker does, so if they were to keep the existing hours, you have some incentive to keep the same hours too, etc.
You could have a no-moving-parts version by putting an LCD window in front of the camera that visibly blacks out. Paging Apple.
You can use anti-monopoly laws to do other things besides just breaking up companies. You can force them to not use their other entities to advantage themselves over competitors (promoting google services over others in search results). You can force interoperability and prevent shutting out competitors. You can prevent buying up new companies that compete with a google product. You could enforce a minim standard for consumer protection and codify rights to access for customers.

Many power companies have government enforced monopolies across the US. They also are heavily regulated and limited in what they can do to prevent them using their monopoly to extort, abuse, or neglect consumers.
Where I live it rises at 4am and sets at 10pm in the summer. I'd actually love to live somewhere where it is like that all year around, but maybe that's just because right now it's 9am - 4pm.
On its face, that looks like bad faith bullying by the CCP.
> I loved playing with Go, but eventually it feels like you're conditioning yourself to be ok with a lot of "bad" code. Tons of repetition, tons of boilerplate by other names.

Not well or hastily written Go is easily like that. I can only guess why you point out the repetition but when you look at well written Go code like in the Go std library, there isn't much repetition happening and it looks rather elegant. At the same time it can be quite some effort to create such code and might take several iterations. Documentation-wise I like the official documentation, it gives a lot of pointers why Go is how it is.

Also obviously it's not for every use-case. Where it works really well IMHO is where error handling is a vital part of the application. (And of course anything concurrent is quite a breeze)
Pretty much. All laptop webcams already have shutoff features to save power. Its just a question of trust.
Nice! I'm sure I'll find a use for this sort of integration in the near future. Thanks for including great documentation and a tutorial link on the github page.
That's an interesting use case -- though the language/interpreter is still in its early stages.

And nice catch on the scroll bars, will fix, thanks!
GDS is /government-digital-service [1]

[1] https://www.gov.uk/government/organisations/government-digit...
Surely you mean TAI? To hell with leap seconds.
Yes, it actually is illegal to arbitrarily discriminate people based on their ethnicity, political views or nationality (unless there is a specific law that allows that for a particular nationality, e.g. in case of a legal embargo)
Github is not outside US jurisdiction, and is required to enforce these laws even if the client is in Europe. They could be sanctioned by OFAC if they don't
The European Union had a poll: https://www.dw.com/en/eu-to-stop-changing-the-clocks-juncker...
Nothing is stopping them.

But that doesn't go far enough. I work on software that, among many other things, calculates durations between local times that have been recorded. DST is a constant thorn in my side.

And no, I can't "just use UTC". To be compliant, the software must accept input in local times.

If it's possible to shift working hours (which it is), then what is the purpose of DST anyway. I'd rather trade the one-time cost of eliminating it entirely than reliving the same mini-crisis twice a year. The upside of DST is nothing but inertia.
Long BTC...
There was a similar change in Russia and Armenia several years ago, and nothing fun or spectacular have happened. Only old computers without internet access had required manual update of clock settings.
IBM 1401: a User's Manual, for Orchestra and Tape
The TZ file changes multiple times a year already. It won't be a big deal.
Don't you solve at least half of this by putting a load balancer in front the service being hit (which is internal, so we control it), then the clients don't need to know which machines are up and working, you don't overload DNS packets with a bunch of endpoints, and the load balancer takes care of keeping track of which machines are available, and the clients don't need to share any state about the status of the individual remote machines.

I'm not sure what this piece is getting at ("don't do this thing that no one would do anyway"), other than ignoring 20+ years of well-understood scaling methodology, and listing a bunch of unrelated gotchas (at high enough traffic rates, you have to deal with running out of ephemeral ports even without the design outlined). This isn't a great modern example of the compounding effects of bad design.
These days, a braille display can be had for around $400-$600. We also have multiple manufacturers, with multiple models and prices you can choose from. I don’t see that happening with open source hardware.
Curious Marc (vintage/space electronics) https://www.youtube.com/channel/UC3bosUr3WlKYm4sBaLs-Adw
Matt Levine makes me laugh hilariously. How he writes so much funny stuff about such a dry topic is a true talent.

I'm so glad he is back.
I don't mind either way, but it does make a difference for coordinating meetings and for international commerce.

Adding 1 hr is advantageous because it will give the Americas (UTC -8 to -5, minus Hawaii and Alaska) an extra usable overlap hour for meetings with Europe (~UTC 0 to +2), and with Asia-Pacific (~UTC +8 to +9) for 18 weeks of the year.

Europe observes daylight savings, but Asia largely doesn't [1]

[1] https://en.wikipedia.org/wiki/Daylight_saving_time
Guternberg was late to the game for bloggers and writers, playing catch-up to Medium and countless headless javascript based CMS's more friendly to writing, they were obviously behind the innovation curve. But it also threw all the WP developers/agencies and companies that use page builders because to save time and money a curve ball. It should have been a plugin, the direction of WP as purely a blogging platform is a train that left the station many years ago.

The main driver or WP at this point is actually well designed themes and theme marketplaces, once again saving people tons of money and time.
I love this quote:

> A meeting on how to extend the GPY method was immediately organized at the American Institute of Mathematics in San Jose, California. As a bright-eyed and bushy-tailed grad student, I felt extraordinarily lucky to be there among the world’s top experts. By the end of the week, the experts agreed that it was basically impossible to improve the GPY method to get bounded prime gaps. Fortunately, Yitang Zhang did not attend this meeting. Almost a decade later, after years of incredibly hard work in relative isolation, he found a way around the impasse and proved the experts wrong. I guess the moral of my story is that when people organize meetings on how not to solve the Riemann hypothesis (as they do from time to time), don’t go!
I appear to be a dissenting voice on this, but I think Gutenberg is a remarkable accomplishment and a great editor. (I say this as someone who is actively developing an editor for my own app.)

It's a drastic shift from how Wordpress has traditionally worked, but that doesn't make it bad.

Most WP visual editors / page builders are terrible. They produce bloated code, huge page sizes, poor SEO. Gutenberg does all this stuff right. But it doesn't try to be a full-fledged design environment either.

The shift is painful, of course. It's incompatible with many existing sites. But I compare this to Apple's shift to OS X, or Microsoft's move away from Windows XP, or any major tech company that has had to shift away from a wildly successful product lest they become irrelevant. The transition sucks at the time, but looking back it always becomes obvious how necessary the shift was.
If a user runs afoul of policy, the action was not arbitrarily discriminatory.
How is this damning, exactly? It's a very specific set of library quirks that are kind of expected -- Chmod doesn't do much on Windows. Arguably, maybe Chmod shouldn't be in the core library if it can't do everything on every OS/architecture combination, but I am not sure that damns the language. It does the best it can, but doesn't deliver a POSIX overlay for Windows. (The complaint continues into a discussion of build tags, to make Windows-only code compile only on Windows. Again, what's the alternative here? If you want your program to do different stuff depending on the platform, there's going to be some sort of conditional to apply that.)

There is then a discussion about monotonic time. The author immediately knows they want monotonic time, but there is no method that specifically returns that. Instead, go embeds the wall clock and monotonic time into a time.Time when you create one with time.Now. It uses the wall clock time for display, and monotonic time to compute the difference between two timestamps. This is not what the author expected, but it ultimately allows them to do what they want. (There is then a complaint about how when you boot a Raspberry Pi without giving userspace any time to start up, the time is set incorrectly, and Go doesn't help. Well... yeah. You can add a hardware RTC if you want the time to be correct as soon as the i2c subsystem comes up, or you can wait for NTP, or you can live with the wrong time. Not sure how any of this involves Go -- it does expect the OS to do OS things for it.)

If you were going to write a damning critique of why to never use Go, it would probably be something like "this dumb library uses channels, sync.Mutex, and atomic.AddInt64 all in the same code and it deadlocks and runs out of memory" or "I installed the most popular ORM on Github and it prints colored text to the console when there is a database error rather than returning an error from the function". I think the linked article totally misses the mark on what problems people are likely to encounter with Go. Let's be honest -- 99% of programmers have no idea that their OS has a monotonic clock, and are quite surprised (and have no idea how to fix it) when start := time.Now(); time.Sleep(time.Second); fmt.Println(time.Since(start)) prints a negative number. But... with Go they don't have that problem. Pretty interesting.
Go can be nice for simple domains where performance is very important. In most cases like that, I'd use Rust, though.
I would love to see a speciality DST-themed, NIST-designed (for 50:50 surety) U.S. coin to be used in such a case.
I am not working towards tenure or any kind of academic career. It’s just something I want to do, and my partner is supportive. Thanks for your concern though!
This is a US bill, not Canadian. Does Canada use US law to set their time ones?
Go's slices don't act like what I thought were called "non-owning references"(Rust's &/&mut [T] or C++'s std::span<T/T const>), which reference memory whose lifetime is bounded by something else (like a vector or array or shared pointer). Instead it's "shared ownership" where memory is referenced by one or more slices (and no single owner) which can reference and mutate the slice simultaneously, and it's freed by the GC sometime after all the slices are gone.

This reminds me of Numpy's ndarrays, which act more like "owning containers" (which may sometimes share ownership and alias) than "non-owning references".
US sanctions are just adding to the troubles of the Iranian people, I should say.
The legal basis is that the US has a big stick, and so all countries must follow us laws, or they'll nuke your capital, rape your children, destroy all your infrastructure, etc.

In this case, it's just leaving you to starve, so you're pretty well off on the whole vs other things Americans will do
Monadic error handling like in ML work-alikes, Rust etc. would be a good start. Adopt:

• https://github.com/rebeccaskinner/gofpher

• https://speakerdeck.com/rebeccaskinner/monadic-error-handlin...

I've been talking to the local Go user group. No one even knows about that concept. This continues a pattern of general ignorance/lack of looking beyond one's horizon I've noticed.
I had the same thought. Presumably, as long as you hold one EU citizenship you're still eligible, even if you're also a UK citizen.
I didn't know they didn't have time zones. Are people there just used to the fact 8am will look very different depending on which region your in?
You can't ask me to quantify my reasoning and then throw out wild unsubstantiated claims out like:

> Following the status quo path will likely result in significantly more people dying

Besides, the clinical trials _are_ quantified. The issue is we don't have data for the potential changes.

Armchair speculation of "maybe half will work" != data
Epic Games just bought a North Carolina mall for its new headquarters
How We Overcame Data Leakage to Build Churn Prediction
We already had that last year here in Denmark :)

https://www.cnbc.com/2019/08/12/danish-bank-is-offering-10-y...
Don’t we have that already? Mandated by the ECB
My .02... My body seems to be on Summer time anyways (ie in the winter I am up at 4am instead of 5am) and crashing at 7:30-8:00pm (instead of 9pm) so I prefer permanent DST (which BC, WA, OR and CA have all agreed to in principle).
Maybe it's the time when you can save up some daylight for a rainy day. Those are your daylight savings.
Cool to see Nissan on the charts there, common Nissan lets get some electric sports cars :)
Meanwhile, in the EU: https://www.theguardian.com/world/2019/mar/26/european-parli...
> I am here to tell you that those practices are wrong, at least for the U.S. They are a form of detainment without due process, contrary to the spirit of the Constitution and, more important, to American notions of individual rights. Yes, those who test positive should have greater options for self-isolation than they currently do. But if a family wishes to stick together and care for each other, it is not the province of the government to tell them otherwise.

If we had widespread ebola or if coronavirus was as deadly as smallpox I don't think many people would be making this argument, and we already have plenty of case law.
There's not a significant difference between a 0% and a -0.125% mortgage. If one doesn't cause weird changes to the housing market I don't expect the other to.
The biggest difference is that /e/ is one of the few OSes that has MicroG pre-installed, which allows apps to make use of some features of Google Play Services (e.g. push notifications, map widgets, and COVID-19 exposure notifications) through a FOSS client. MicroG lets users turn on/off some of these features, and does not support Google's APIs for ads or analytics.

https://microg.org

https://github.com/microg/GmsCore/wiki/Implementation-Status

LineageOS does not support the mechanism (signature spoofing) that enables MicroG to replace Google Play Services. The developers of LineageOS consider signature spoofing to be a security risk:

https://review.lineageos.org/c/LineageOS/android_frameworks_...

It is up to users to select the OS that best meets their own privacy, security, and usability needs.
Covid Alert Canada 1.1.6 (iOS 12.5 added)
A couple of years ago I moved everything over to my brother who resides in Dublin just in case I lost my long standing domains. It seems I could in theory update this back to my home address in Northern Ireland given this: https://blacknight.blog/brexit-and-eu-domains-again.html - does anyone know if that's actually the case? I found the potential loss of yet another part of my EU identity thanks to Brexit a real kick in the teeth :(

Edit: I guess as I hold an Irish passport I'm entitled to own an EU domain. Though I remember messaging EurID at the time (https://twitter.com/EUregistry/status/1086252921380065285) and they didn't seem to know for sure - but that linked page now says a Union citizen, independently of their place of residence - so that probably covers me. I feel for any UK only citizen losing theirs :/
So regular, you could set your clocks to it...
> Defaults are powerful!

No kidding! Just look at where we are with personal data. The default is opt-out - it should be opt-in. And for consent, the default is 'assumed' consent - it should be 'informed' consent.