Hacker News Reader

Comment by jimnotgym | Hacker News Reader

There was a thread on here at the weekend criticising Windows 10 for not making enough progress, and also MS for not properly testing updates. I hope this silences those critics. A thoroughly tested change that is fully backwards compatible, but also adding genuinely useful new features. If you were wondering whether to upgrade to Windows 10 I think this settles it.

View on HN

Not sure how you go from "finally catching up with support of a basic text format that's around for decades" to "making enough progress". This won't silence anyone - it just shows that Microsoft is finally starting to do things it should have done 20 years ago.

I think the person you were responding to was being sarcastic.

I see it more as a platform war that's finally settled. No more Mac/Linux/Windows linebreaks, now we can at last talk about "Linebreak".

I mean there is only so many ways of putting together two different characters. Is it supposed to be \n\r or \r\n? Or just \n? Or mabe it's \r? So much of the last 35 years have gone to writing the wrong line endings for the intended platform...

Only if you ignore mainframes.

If you were wondering whether to upgrade to Windows 10 I think this settles it.

As long as the telemetry/phoning home is still pervasive and difficult to disable completely, no. Ever since ~2K/XP or so it's always been one step forward, many steps back.

Using a Google OS?

The criticism was that they had failed to test updates which proceeded to crash machines and break applications. That they managed to test this one feature is hardly a persuasive argument to the contrary.

The day I can set the font in cmd.exe without editing the registry is the day I will miss your sarcasm.

People don't actually use notepad, do they? The last reason I'd think of to upgrade a Windows OS is "I'll be able to use notepad".

Sure we do, quick editing txt, cfg and ini files.

Reply on news.ycombinator.com