Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Comment: Important questions... (Score 1) 104 104

Can this be used to root your phone (as in, install SuperSU), and can this be done without tripping Knox?

Can this be then mitigated by a simple hosts entry for the domain used to check for updates? (Pretty sure the answer here would yes - if skslm.swiftkey.net points to 127.0.0.1, no rouge WiFi's DNS is going to be able to change that).

Comment: Re:HiDPI (Score 1) 186 186

Windows does render ClearType fonts into the subpixels BEFORE scaling up though, completely negating the subpixel rendering benefits, and actually making fonts look significantly worse as a result.
The whole scale-up solution for applications that don't declare DPI aware in the manifest resource would be a lot better if they at least reverted to greyscale subpixel font rendering first...

Comment: Re:HiDPI (Score 1) 186 186

It's because unless your app declares itself HiDPI-aware in the manifest file (Skype does not do this) then Windows will pretend that it's still 96dpi and then just scale up the UI 200% (for 192dpi screens). But it's not as simple as adding the line to the manifest file. You actually have to write your software without the assumption of 96dpi dialogs, and use the system API functions to query the proper scales. Most developers never seem to even know about those functions though, so you end up with a random mix of too-big and too-small things.

Even if Microsoft's scaling approach didn't render fonts into the subpixels BEFORE scaling up the 200%, it would still look really blurry and horrible compared to just fixing the code in Skype to actually take advantage of higher resolution. Apple's approach just gives you grey blurry edges around fonts and blurry graphics vs Microsoft's red and blue blurry edges around fonts and blurry graphics.

Comment: "You'll experience problems with your display" (Score 2) 374 374

Click the menu icon in the top left of the upgrade reservation thing, then pick Check your PC. On my VERY new Sony VAIO Flip 15, which came with Windows 8, I get the message "These devices aren't fully compatible with Windows 10" -> Intel(R) HD Graphics Family -> You'll experience problems with your display.

So what does this mean? If I let the upgrade happen on July 29, my screen goes black after that? How can such a new video "card" be unsupported? (It's the built-in display on the Core i7-4500U this thing has). Is it because I also have the Nvidia GeForce GT 735M on here, with that GPU-switching technology (Optimus?) that so many new laptops have now?

Comment: Why not Vista? (Score 1) 214 214

I don't quite get why the cut-off is Windows 7 and not Vista? The hardware requirements are basically the same from Vista to 10, and internally that would cover a free upgrade to 10.0 for Windows versions 6.0 to 6.3.
Not to mention getting home users off IE9 would be a big plus for the web in general (assuming you've already just dropped IE8 users like you should have).

Comment: Re:Is it really IE 12 or not? (Score 1) 133 133

As far as I know, it is IE 12 (Trident 8.0), but they consider it a fork, which means technically you can have different features and support in Edge 1.0 and a future hypothetical actual IE 12. Mostly what they did was *remove* all kinds of backwards compatibility stuff from Edge, so that you can't trigger IE10/9/8/7/5 (yes, 6 was not a choice) rendering modes anymore. You can't use VBScript, ActiveX, and all kinds of other non-standard stuff. IE10+ is already a pretty decent modern browser, very much on par with Firefox and Chrome, so you should expect Edge to be just as good, as long as you're writing standard HTML5 code.

I tend to include in the headers of sites I write recently, because it removes the button in IE that lets users toggle backwards compatibility mode, but lazy people could previously use that tag with IE=8 or IE=5 to force IE into backwards compatibility rendering modes instead of updating their sites with standards compliant code. I guess that will no longer work with Edge. It will only render in HTML5 standards mode and nothing else now.

Comment: Re:The first edition (Score 1) 133 133

If you write to HTML5/CSS3 standards, any web app written in the last few years can easily target IE9+ and work on Firefox/Chrome/Edge with no issues. It's only people who rely on huge bloated frameworks to provide backwards compatibility with IE6 that have issues with their stuff suddenly not working on IE10 or IE11.

Basically, right now, everybody needs to drop IE8 support, and you can pretty much stop using jQuery and modernizer and all that other cruft. If you drop IE9 support (which is really only Vista users), you'll quickly find that Chrome is the lowest common denominator to support.

Comment: Re:The first edition (Score 4, Informative) 133 133

Except it's really effectively Trident 8.0 / IE 12. Only, they forked it and removed all the legacy support from it, then left a copy of Trident 7.0 / IE 11 around in case you need legacy support still. So it's not really the first version of anything, and it's not like it's completely from-scratch code.

Comment: Re:Disturbing. (Score 1) 106 106

Just FYI, in Japan, it doesn't mater if it's true. You cannot post anything that would bring financial harm to a company. True facts or not, if you post negative things just to hurt a company, you're breaking the law in Japan. I don't see how Google can win this actually. Of course, they're free to keep showing the negative reviews in other countries.

"Silent gratitude isn't very much use to anyone." -- G. B. Stearn

Working...