Re:The IPv6 Numeric IP Format Is a Usability Problem
by na85 on Friday February 19, 2016 @09:57PM
(#11138520)
But then that user would be running Windows 10, which means they get to pay Microsoft for the privilege of having their data harvested and having an advertising ID assigned to their device.
Why any sane individual willingly chooses windows 10 is beyond me.
edit: Can't reply, but turning off the "phone home features" doesn't actually turn them off. It still phones home and you still get assigned an advertising ID. Sure, I could block it at the firewall potentially, but this is about taking an ideological stance.
Re:The IPv6 Numeric IP Format Is a Usability Problem
by ccoggins on Friday February 19, 2016 @10:50PM
(#11138711)
It looks just like yours on Win 10 under Chrome. I was curious and tried in Edge and it renders fine.
Also, the settings in Win 10 allow you to turn off a lot of the phone home type stuff. Other than that, my opinion is that 10 mostly feels like a more polished 7.
Re:The IPv6 Numeric IP Format Is a Usability Problem
by NetStrikeForce on Saturday February 20, 2016 @07:22AM
(#11139823)
Windows 10 on Chrome here, I see the same as the Windows 7 user above.
Actually, it renders perfectly on Edge; so the problem is probably with Google Chrome.
I'll address this point, the sibling comment already addressed the other point (it wasn't meant as a criticism, by the way).
It's true that Windows 7 still get updates. However, these are mostly security updates, or bugfixes. We don't expect it to get new features. In this case, unicode font rendering. It is likely (but not guaranteed) that a user running Windows 10 would see a much better result.