

Then simply write it in a text editor without saving it into a file, it’ll be lost after closing the program.
Then simply write it in a text editor without saving it into a file, it’ll be lost after closing the program.
Can you point to a specific law that the EU has passed in this direction?
Cos according to the article all attempts to pass something like this that have been presented in the EU have been blocked. By the EU.
An alternative title could have been: “EU Possibly The Only One Who Has Been Explicitly Rejecting Backdoor Mandates Until Now”
Sure, proposals keep being presented… but I feel it’s kind of a bit early to call the EU “greatest threat” just because yet another attempt has been made. Specially when you compare it with many other places where they apply things like this without batting an eye.
I’m not saying we (Europeans) shouldn’t push (yet again) to make sure this also fails… but the title of the article is a bit misplaced, and after a history of successful rejections I feel a lot more optimistic.
interoperability == API standardization == API homogeneity
standardization != monopolization
Yes, although Ctrl-M
would be the “Carriage Return” character (\r
). For the “Line Feed” newline character (\n
) the Control combination would be Ctrl-J
. Both of them would normally produce a new line when you press them on most terminals.
That’s why if you open in nano/vim a file with Windows style EOL (/r/n
), you might see a strange ^M
symbol at the end of each line.
True, but then you have bigger problems than just the journal.