3 ms·
The issue dates back to the release candidate of the second version of .NET Core, 8 years ago. Surely we can do better than "it used to be bad at x point in tim
by neonsunset 2y ago
The issue dates back to the release candidate of the second version of .NET Core, 8 years ago. Surely we can do better than "it used to be bad at x point in time and this can never be rectified".
I like my privacy more than the next guy, but you are not arguing in good faith (which is all too common, because people like to use much inferior technologies and make .NET a scapegoat, instead of learning better and ceasing idiotic self-sabotage)
Edit: Heh, in HN jail. In response to the comment - you should apply this logic to the languages steered by Google, Oracle and Apple. .NET is completely unrelated to Recall and whatever happens to it, it could have been as well a separate company.
- macintux 2y agoMicrosoft does not make it easy to give them the benefit of the doubt. See, for example, the Recall debacle. https://doublepulsar.com/recall-stealing-everything-youve-ever-typed-or-viewed-on-your-own-windows-pc-is-now-possible-da3e12e9465e https://doublepulsar.com/recall-stealing-everything-youve-ev...