The blog and the 11% for IE11 landing page both imply that if you complete the challenge, you will win the prizes described.
For instance, the blog entry says: "If you can get 11% better page load performance from your site, we'll send you and your team some 11 goodness." I'm no lawyer, but that sounds like a valid unilateral contract to me.
Similarly, the landing page says: "Show us how you got 11% better page load performance in your organization's home web page and we'll send you all this goodness."
But in the fine print, it says: "The first 11 organizations that meet the qualifications above will each receive the following: 11 pizzas (in the form of a $120 gift card), 11 year-long subscriptions to BrowserStack (ARV $240 each), and 11 copies of Parallels Desktop 9 for Mac (ARV $79 each)."
There's a heck of a big difference between "If you do this, we'll give you this" and "If you're one of the first 11 people to do this, we'll give you this."
The fact that there will be only 11 prize winners should be made more clear. After all, there is PIZZA on the line. And there's nothing like a pizza bait-and-switch to get developers angry at you.
Thanks. I hope you'll also update the landing page of the challenge.
A little more feedback, which I hope you'll take as constructive:
As I said above, there's quite a difference between "if you do this, you'll win this" and "if you're one of the first 11 people in the United States to do this, you'll win this."
As I see it, if I have any chance of winning the prize, I've got to drop everything right now and scramble to complete the challenge, and even then, who knows how many other people are doing the same thing?
So, my incentive has just dropped from, "This is exciting! I have a decent shot at getting pizza!" to "It's extremely unlikely that I'll win. Why bother?"
I would therefore suggest that you look for ways to increase the value proposition to developers. I'm not saying you have to spend millions -- but maybe find some creative ways to reward developers outside of the first 11, such as by featuring some of the success stories on your blog.
Wow. No, you're not the only one. Those are some of the worst compression artifacts I've seen in an actual image that wasn't just a compression demo that I've seen in years.
It would be nice if Microsoft would fix the issues with IE11. Like all the sites that work with IE10, that don't work anymore with IE11. Their solution was to issue an IE11 upgrade blocker with a shitty manual install routine.
Internet Explorer has been and continues to be hostile to the web. It easily makes my job as a web developer at least 50% more difficult which translates into costing my employer more money.
As far as I'm concerned, we as developers need to make a concerted effort to force Microsoft to either adopt WebKit or release a version of IE that is 100% standards compliant.
Diversity of implementations on the web is vital for continued innovation. Though it's less important that IE stick with the Trident engine now that Blink and WebKit 2 have diverged, we should celebrate progress and encourage participation in the standards process - things IE has gotten a lot better about especially in the last two iterations.
You have to scroll down quite a ways before you find feature differences between the browsers, and it's not quite clear which (except maybe Chrome) is the best. If we remove feature drafts, it's a good deal closer.
> IE9/IE10/IE11 dont even render the same page the same way
One could argue this is because each version is better than the previous. "Better" being relative here.
> they make money by making their os obsolete
This touches on a possible source of the problem. Their insistence on tying browser upgrades to major releases of Windows proves they care more about the revenue from the OS sales than they do about not breaking the web.
I'm encouraged that they have automatic updates now but the jury is out as to whether they'll make use of it in the way Chrome and Firefox have.
I agree that diversity of implementations is vital. However, Microsoft has continuously proven its inability to provide an implementation that can even remotely compete. I don't care if its WebKit, Blink, or Servo. But any one of those is better than what Microsoft has insisted on plaguing us with in Internet Explorer.
Now, with regards to IE11, you may be right. And I hope you are. I SINCERELY hope you are!
But with every subsequent release since IE7 I've heard people say something to the effect of, "Its so much better than [insert previous version of IE]" and they were right. Except that; a) the previous version was so beyond bad that fixing one bug would've been a marked improvement and b) the new version STILL paled in comparison to all the other browsers out there.
So if history is any indication, IE11 will be incrementally better but it will still make my job unnecessarily hard and it will still prove itself to be hostile to the web.
Is this an issue with IE11, or an issue with sites built to work with the way IE10 handled certain things that have now been brought better in line with standards?
I know my team had to make an adjustment due to the user agent changes, initially our site loaded in IE11 by stating the user needs IE7 or greater.
Doesn't make up for the fact that I spent most of my time writing workaround for the stupid rendering bugs their "30% faster" browser introduces. Even just basic CSS layouts and constantly wrong in IE.
I know, I don't care if they are objectively the best browser (I doubt they are), my grudge against them runs too deep. I want them to fail. Does that make me a bad person?
Mildly better, at least I don't have to use a workaround to get transparent PNGs to work anymore. It would be alright supporting just IE11, but you're not, you're supporting IE7, IE8, IE9, IE10, and they all have their own weird bugs.
I'm not loyal at all to any browser. I swop and change (used to use IE, then went to Opera, then Firefox and now to Chrome), but when I hear obvious lies such as IE is 30% faster than any other browser I all of a sudden want to permanently leave IE alone
I noticed it was both obvious and trivial to add a web page to your home screen. Is that also the case on windows phones? Is it the case on any other phone? Or are webapps treated as second class citizens still on phones?
I would test for IE, but there's no native Mac client outside of virtualization. Until they match Chrome and Firefox, it will be the browser of graceful degradation for me :(
For instance, the blog entry says: "If you can get 11% better page load performance from your site, we'll send you and your team some 11 goodness." I'm no lawyer, but that sounds like a valid unilateral contract to me.
Similarly, the landing page says: "Show us how you got 11% better page load performance in your organization's home web page and we'll send you all this goodness."
But in the fine print, it says: "The first 11 organizations that meet the qualifications above will each receive the following: 11 pizzas (in the form of a $120 gift card), 11 year-long subscriptions to BrowserStack (ARV $240 each), and 11 copies of Parallels Desktop 9 for Mac (ARV $79 each)."
There's a heck of a big difference between "If you do this, we'll give you this" and "If you're one of the first 11 people to do this, we'll give you this."
The fact that there will be only 11 prize winners should be made more clear. After all, there is PIZZA on the line. And there's nothing like a pizza bait-and-switch to get developers angry at you.
reply