812 karma · joined October 3, 2016
This is fully 100% OSI compliant source code with an approved license (Apache 2.0). You are not entitled to anything more than this.
> Banning encrypted messaging (almost passed)
It's a positive thing that it was brought up and struck down. EU is the actually the one you should be thanking because most European countries would ban it.
> Cookie pop ups
Malicious compliance by websites, but at least users have a choice of opting out of tracking. Again, a positive thing.
> Various regulations harming open source (discussed before on HN)
The most recent changes are so watered down that it basically only applies to commercial open source companies that are turning a profit. It's helping users more than it's harming the open source community.
If they decide to ban these kinds of messages, and only enforce link tracking, that would be directly in conflict with the ruling.
In practice, you can make both as complicated as you want, but SPA seems like a simpler starting point.
It's not man-in-the-middle, it's man-on-the-end. If your chat app wants to spy on you, there is nothing you can do, but at least it becomes obvious and easy to analyze because it's client side code. It's not a counter argument to interoperability. You need to trust both sides, the same way web works.
It's like saying quantum teleportation [2] is BS, just because you don't like the SF sounding word "teleportation".
https://blog.research.google/2022/11/making-traversable-worm...
Of course the field can be continuous, even if the weight is exactly some rational number. "Discrete steps" just means that the value differences in gravitational waves is also discrete. A bigger problem, where relativity clashes with QM, is stuff like singularity and superposition. We don't have an answer for that yet.
It's actually amusing that, just few weeks ago, people here on HN were arguing on why are we trying to quantize gravity and that it makes more sense for it to be non-quantum.
Why is your default assumption that physicists haven't tried to make it discrete? You need to break Lorentz invariance to have the universe be discrete, which is an effort that's worth a Nobel prize.
> Doesn’t seem like we have a good reason for it
We have many good reasons for it.
https://www.forbes.com/sites/startswithabang/2020/04/17/this...
From the article: "If space is discrete, then the principle of relativity is wrong"
That, however, doesn't mean that spacetime is not a continuum.
Or a transfer of power from US-centric companies to actual sovereign bodies. I don't want to live in a cyberpunk world. This sounds good to me. Note that browsers are still allowed to remove them if they are compromised.
Last week I logged into my e-gov website by confirming a push notification on my authenticator app that's tied to my e-ID card to download my birth certificate. No copy pasting needed. Random websites now even support logging in without passwords by using your smartphone passkeys.
I am sure they can make it work for a simple yes/no (over 18) challenge-request scenario.
> Plus, not everybody has a smartphone. Not everyone accepts Android or iOS at their current implementations. Do those people remain without access to the www?
We are talking about adult content. The alternative is having that content banned. Many democratic countries have already done that, like South Korea. I don't prefer this scenario.
I don't necessarily agree we need this, but to claim it's impossible to do this in a secure way is ridiculous.
- if you are CPU bound, work stealing will be better for most cases
- if you are IO bound, thread-per-core might work better, but again, you have enough CPU headroom that the performance doesn't really matter
IMO, work stealing is a better default to encode into language API
The analyzers are part of the build, they work everywhere (command line, VS code). Either way, I am glad we finally agree that async await "works fine" for modern .NET.
> so I don't know, maybe I actually already read them?
I did, I even responded to your links with the official conclusion from the NET team on those issues. Now maybe your turn to read?