1,286 karma · joined November 4, 2019
source : https://www.zdnet.com/article/this-xbox-hdmi-cable-has-anti-...
There are some exceptions to the behaviour you describe, like for instance with C# which for the longest time only allowed value types to be annotated as nullable, and only very recently extended this to reference types, and only as an opt-in feature, and the type checker only throws warnings, etc. That would be a case of a language which is not "null safe" but provides faculties for accomplishing that.
I think this can be supported by the fact that these fancy language features have been successfully implemented for decades and are only now showing up in mainstream languages.
I think the sentiment behind the quote and its widespread use is correct however. It definitely does seem like the tradeoffs of null safety are worth it in the vast majority of cases. Most of us who use GC languages with massive runtimes sacrifice a lot more performance for a lot less value.
Someone at Twitter knew what they were doing. Let's hope they didn't get swept up.
For most people using social media outside of the context of a professional organization, it also means trusting whoever operates the instance, most of which will probably be less reliable and potentially trustworthy than Twitter was or currently is under Musk ownership.
As it happens, the implementation details of platform security are typically not secret. It's the keys that are. The "intellectual property" in question is only the solution to a very well understood but computationally infeasible problem. It has no use or worth beyond protecting the vendor's restrictions on your device. This has precisely nothing to do with the tech being proprietary. You could implement a platform monopoly with nothing but FOSS tech. I'm starting to think you don't understand the technology very well.
For instance, It's not terribly difficult for security hackers to blow the door open on these systems even when they're proprietary and no public documentation or datasheet is supplied. George Hotz famously published the private keys for the PS3 and was sued into oblivion. You'll find this isn't about technology at all, but law.
The "just buy a Jolla/Sailfish phone" argument is a non-sequitur. For starters, who says I haven't? That doesn't mean I need to accept that my friends and family are getting fleeced. Let's assume I'm also purely self-interested, who do you suppose they go to when they can't get basic computing tasks done because it conflicts with their hardware vendor's interests?
I still fail to see how engineering your own cryptographic monopoly and abusing it is different from abusing any other sort of monopoly.
I can think of three reasons why someone would opt into that, as opposed to "buying an unlocked computer system". The first being lacking the technical knowledge to understand that your machine is sold to you pre-compromised. The latter two being exclusive titles and the fact that your social circle may coax you into that platform, both of which throw "personal choice" out of the window.
This isn't just about video games either. My career field doesn't require me to use Gillette razors.
In any case, if there isn't a legal distinction between a monopoly that forms through incidence and one that was purposefully designed and planted into an already thriving market, there ought to be.