The blog post gives an example of how the current approach makes dependencies incompatible.
> if someone publishes an alternative to serde (say, nextserde) then all crates which have added support for serde also need to add support for nextserde. Adding support for every new serialization library in existence is unrealistic
If I use serde, I cannot use a crate that only implements nextserde.
If I want to use nextserde, I lose the ability to use all the crates that only implement serde.
You'd be amazed at the times I've argued with people on HN that free speech infringement by the UK government has grown rampant, only for them to enact the next draconian law a month later.
UK is trying to be like Russia and China, where a minder will show up at your door if you post something the government doesn't like. Then people online will defend it because the investigation didn't turn into a full criminal charge or they say the people simply deserved it.
The reality is this will seriously chill speech broadly across the country regardless of either of those outcomes, and the technical costs of enforcement will be steep.
We don't have any pro-free-speech political parties, nor a written constitution unfortunately.
I mean there are parties that say they like free speech, but it never extends to the sort of speech they disagree with, or by people of the wrong colour/religion/gender etc.
You inspired me to look up RFC8366. That's a remarkable document, apparently written in English, where at least the abstract and introduction look like they might be the result of a particularly nerdy game of Mad-Libs. :)
I, personally, have never observed a pledge doing anything other than being heard, although I observed Lemon Pledge smelling unpleasant. But, in RFC8366, pledges can join domains!
(I assume that a manufacturer makes a device and the device somehow contains a "pledge" from the manufacturer that the device is what it says it is...)
You assume almost correct, the device is the pledge itself! RFC8366 is used (among others) in the BRSKI protocol family. For device attestation purposes in 802.1x Networks, a pledge comes with a manufacturer provided public key material, often a certificate but not always, that links it to the manufacturer via a publicly available trust root. In an exchange process, the customer - called the registrar in the specification documents - then asks for and verifies the pledge's key material before issuing their own domain certificates.
It's in essence an automated zero-trust-ish protocol for network join purposes :)
If it's due to tax it can't be used to advocate the pros or cons of market arrangements, since we don't know what the market would be doing in the absence of the tax.
It's because of the rules of the European Energy Market where all electricity has to be as expensive as the most expensive source.
So as soon as Germany lights up their gas powerplants, that follow gas prices (wars, etc), French nuclear electricity has to be sold for the same price.
Yes, but that's assuming that there should be a free electricity market.
The fundamental issue with electricity markets is that they cannot rely on any signal other than the electricity price to control whether a given plant will be running at a given time or not.
I think a real alternative would be to set-up an entity charged with negotiating prices with the electricity producers (which would also be a sort of partial reversal on the whole market thing in a lot of countries).
reply