> The virtual machines testing platform is nearly finished. Once completed, you'll be able to easily test your site on Windows, Mac or Linux. Check back soon.
Having an official VirtualBox (I assume?) image would be great.
Since they're not activated it's 30 or 90 days, I think. But you can just revert any VM changes upon shutdown and thus extend lifetime indefinitely (makes working in some environments quite a hassle, though – e.g. I'd have to re-setup the proxy every time I start the VM).
This reminds me that MS will support IE on Server 2003 until July 2015, and IE on Server 2008 (both R1 and R2) until January 2020. Yes, both R1 (based on Vista/NT 6.0) and R2 (based on Win7/NT 6.1), because R2 is considered a "minor release" while Win7 is considered a major release.
It's VHD (although relatively easy to make work with VirtualBox), but more importantly exe files. I don't know it cabextract or unrar can handle this. In either case, it needlessly unfriendly to non-Windows users.
That's not an official cross-platform image. I have used some tools that converts them to VirtualBox, but it hasn't been very reliable. As I said: Having official support for Linux and Mac will be great.
> "The virtual machines testing platform is nearly finished. Once completed, you'll be able to easily test your site on Windows, Mac or Linux. Check back soon."
I ran one of my problem child sites through it. Modern.IE seems more interested in ensuring my pages add a bunch of crap for IE10 and Windows 8 rather than finding painful IE8 compatibility issues. This is pretty much just a marketing site for IE10.
The scan results are grouped into IE compatibility problems, potential cross-browser issues and the last option you mention. I'm not sure the former two categories qualify as marketing.
[edit] I just find it odd that MS puts so much stuff on Irish domains, just because of the abbreviation. Surely they don't think they could possibly own this tld.
What's with this trend of companies and startups requiring customers to sign up with Facebook? Especially for developer and technical resources, for which it seems there's a healthy level of dissociation from Facebook.
What's worse is developer-level services that require Twitter to sign up, or sometimes even Github. Not all developers (see: me) have a Twitter or Github account.
The services are trying to provide you with easy access so you don't have that barrier of creating "yet another account". Depending on the service they're offering they'll pick a reasonable third-party that offers oAuth integration.
I'd say that GitHub auth for a service aimed at developers is a reasonable assumption to make.
The process of logging in with a third-party account takes about as much time as filling out a name, email address and a password into a form. Since I can even get my browser to auto-fill my name and email address and auto-generate a random password, creating "yet another account" (a couple of clicks, no typing at all) is actually less hassle for me than logging in with some other account and then going through a scary-looking authorization prompt. In fact, apart from Stack Overflow, I can't remember a single website where my identity is tied to another account of mine.
And to make things worse a lot of time after you go through the facebook/google/github login they still require you to pick a password for their service, which means the login was purely to get you to link your accounts to their services which just feels icky to me.
Sure support it as an option, but don't make it mandatory that you have a account with social media service X.
"I'd say that GitHub auth for a service aimed at developers is a reasonable assumption to make."
As long as its optional. I'm hosting my own Git repositories on servers I own, hosted in centers with fat pipes. I know devs working on sensitive stuff which shall never make it to any public / cloud / whatever. There are also developers who are not at all into the "open source" thinggy.
It's good if they conveniently allow GitHub for those who are using GitHub as long as they also offer other ways to login (say OpenID [even if it has its flaws] or good old email/password or whatever).
Not all developers have a Facebook account. And the ones that do don't necessarily want their professional activity tied to it.
Twitter has no official policy barring the same person from having multiple accounts (though Github does, for free accounts; thanks to niggler for the correction) --- so, if you want to keep your use of the service from being tied to your other online activity, you can just create a throwaway account. Facebook does; creating "throwaways" potentially puts your use of both Facebook and the other service at risk.
More seriously, neither is known for, say, tracking logged-in user activity on other sites (the way Facebook is known to do with "like" buttons).
What is the benefit for developers anyway? They get a bit more subscribers this way? But don't they lose like almost all control over those accounts to Facebook?
It's purely to make it annoying to repeatedly sign up for three month trials. If you'd like to pay BrowserStack money for their service, they will gladly take it without requiring a Facebook account. (It's a pretty nice service, by the way)
The sad thing is, if you implemented OpenID you can painlessly enable sign in to your site through Google, Yahoo, the StackExchange network and a myriad of independent openid providers, but no, we're going with Facebook guys.
Google/Yahoo/StackExchange/Flikr sign in with OpenID works exactly the same way that Facebook login works (to the user.) Your site presents a button, the user clicks it, and if it's the first time they get a popup asking to grant access, then they're logged in. Those four domains are pretty far reaching in terms of casual and technical users but now you can also provide a third option for even more technical users to use a custom OpenID, for virtually no additional cost in development.
Fantabulous. It's not a tool for developers, it's a tool for clients to unreasonably bash developers over the head with and to market MS's substandard browsers.
Already had one email going "URGENT!!!! COMPATIBILITY ISSUES WITH IE!!!!" on a site that renders and works perfectly back to IE6.
Total side notes, but I'm really enjoying this new design trend from Google and Microsoft. Clean, simple, and to the point. Helps take that "corporate" edge of Microsoft specifically.
Also I'm glad that, like Adobe, Microsoft is embracing more modern and standard practices towards web development.
I think it's a little sad that the most "modern" IE Microsoft can put out is still like 2 years behind Chrome in HTML5 features. Chrome 10 had more HTML5 features 2 years ago than IE10 has today, and the Blackberry 10 browser is actually even more ahead, and that's from a company that doesn't usually make browsers:
>and the Blackberry 10 browser is actually even more ahead, and that's from a company that doesn't usually make browsers
html5test.com does not test anything, it just checks that listed features are available. Blackberry 10 uses WebKit and they just turned on more experimental features than Chrome.
I've always found IETester to be a great "good enough" lightweight testing tool. No VM images to download/spin up separately or worry about expiration.
48 comments
[ 3.5 ms ] story [ 103 ms ] threadGet a free 3-month trial of Browser Stack sponsored by Microsoft. Normally you get a 15minute trial.
Just go to the Virtual Tools page.
> The virtual machines testing platform is nearly finished. Once completed, you'll be able to easily test your site on Windows, Mac or Linux. Check back soon.
Having an official VirtualBox (I assume?) image would be great.
What I'd like is MS to make Server 2003 images, rather than XP, for IE8. And 2008, rather than 7, for IE9 and IE10.
I won't use them (even though I remember something about cabextract being able to extract .exe files)
I won't spend a minute testing on IE except if needed.
Very much looking forward to this!
http://www.modern.ie/virtualization-tools
[edit] I just find it odd that MS puts so much stuff on Irish domains, just because of the abbreviation. Surely they don't think they could possibly own this tld.
Thanks. No.
I'd say that GitHub auth for a service aimed at developers is a reasonable assumption to make.
Sure support it as an option, but don't make it mandatory that you have a account with social media service X.
As long as its optional. I'm hosting my own Git repositories on servers I own, hosted in centers with fat pipes. I know devs working on sensitive stuff which shall never make it to any public / cloud / whatever. There are also developers who are not at all into the "open source" thinggy.
It's good if they conveniently allow GitHub for those who are using GitHub as long as they also offer other ways to login (say OpenID [even if it has its flaws] or good old email/password or whatever).
Twitter has no official policy barring the same person from having multiple accounts (though Github does, for free accounts; thanks to niggler for the correction) --- so, if you want to keep your use of the service from being tied to your other online activity, you can just create a throwaway account. Facebook does; creating "throwaways" potentially puts your use of both Facebook and the other service at risk.
More seriously, neither is known for, say, tracking logged-in user activity on other sites (the way Facebook is known to do with "like" buttons).
"One person or legal entity may not maintain more than one free account."
https://help.github.com/articles/github-terms-of-service Section A7
Already had one email going "URGENT!!!! COMPATIBILITY ISSUES WITH IE!!!!" on a site that renders and works perfectly back to IE6.
Also I'm glad that, like Adobe, Microsoft is embracing more modern and standard practices towards web development.
http://html5test.com/results/desktop.html
http://html5test.com/results/mobile.html
html5test.com does not test anything, it just checks that listed features are available. Blackberry 10 uses WebKit and they just turned on more experimental features than Chrome.