171–180 of 217 posts
Earlier quoted context omitted.
With IE, a testing environment costs my company about $300 per developer. I.e., miniscule relative to the cost of actually having a developer.
Or another way of looking at it, infinity times greater than the cost of Chrome or Firefox testing environments.
You still need to test them in all supported OS.
I keep having font and layout issues across all OS, especially with customers that require pixel perfect layouts.
Earlier quoted context omitted.
Are you free to use those on non-Microsoft host operating system? I thought the last time I checked the host had to be Windows Professional. Also you have to re-download the image every 3 months, and get it set up again. I can't just toss a virtualbox image on my personal Ubuntu machine and test in IE6-8. I need a Windows computer to test my personal sites (which are barely worth development time.)
It is setup like a trial edition of Windows. It can be installed on anything really. Microsoft say the requirements are Windows XP and Above, but i did see code to convert from a VHD to a Virtual Box image. Also, you only need to download every 3 months if you want the latest, patched edition from MS. If you want to do it yourself, you can just recreate the image yourself (sysprep).
tl;dr the site works with IE9 and IE10. I find the style of writing of this post extremely obnoxious, was it really necessary to say the exact same thing with slightly different order in the words over and over? If your post is to be short because there's not a lot to say, don't extend it unnecessarily, get to the point, move on.
Earlier quoted context omitted.
The arbitrary restriction(not browsers; explicitly placed by the developers) is there to ensure people don't see a broken version. I don't know about the recent IE versions, but earlier versions needed won't center align when I say `margin: 0 auto`(have to do a text-align: center then reset it in child container), have a different boxing model, doesn't support min-height, won't support hover on all elements etc etc.…
It takes five seconds with Google to discover why centering doesn't work. Hint: you're probably missing a doctype declaration. If you're thinking of blocking multiple versions of a browser because of your own lack of knowledge then perhaps you're in the wrong industry. We went through this ten years ago. It was a bad idea then and it's bad idea now.
May be the doctype will fix it for newer version of IE, may be it won't(don't know about the newer versions; older versions need text-align:center). You are conveniently ignoring different boxing model, min-height, staircase effect, double margins etc.
> It takes five seconds with Google to discover why centering doesn't work.
I can find a work around doesn't mean anything. The point is IE does things differently causing extra effort on my part, and if I can avoid it, I will.
Earlier quoted context omitted.
Or compared to the cost of the developer's time for testing and writing code for it. It's annoying that supporting IE costs one Windows license. It's painful that it's so far from standards compliance.
Microsoft provides free Virtual Machine images for testing Internet Explorer. http://www.microsoft.com/en-us/download/details.aspx?id=1157...
I.e. they cost nothing but your time...
Earlier quoted context omitted.
The arbitrary restriction(not browsers; explicitly placed by the developers) is there to ensure people don't see a broken version. I don't know about the recent IE versions, but earlier versions needed won't center align when I say `margin: 0 auto`(have to do a text-align: center then reset it in child container), have a different boxing model, doesn't support min-height, won't support hover on all elements etc etc.…
If I were interested in buying something from your web site, I would be less likely to bounce somewhere else as a result of seeing an uncentered container than I would as a result of being told to upgrade my browser. P.S. Browser restritions are placed by developers, speed restrictions by police, and height restrictions by amusement ride operators. It's not the browser, the speed, or the height that's doing the restr…
Depending on the demographics(what do I lose if I don't support outdated IE and how likely is my customer base to be running arcane IE), the amount of effort required to make sure my site runs on arcane IE; your bouncing off somewhere else might not matter to me. I didn't say putting up a notice saying use a modern browser will ensure customers will comply - I am saying that might be a reasonable compromise.
If I, as a developer, decide my site supports a browser, I know I'm going to have to spend some time doing QA on that browser. Standards are cool, but I've run into enough FF and Chrome bugs that I always test. That being said, the cost of testing in IE is waaay higher than the cost of testing in FF and Chrome. Why? Because FF and Chrome are cross-platform, I and my fellow developers can test on our OS of choice. Wit…
VirtualBox natively supports VHD format, so stop shaving those yaks. Where is that $300 coming from? You run VirtualBox on your computer (free), install free VHD's (free), and free the free free with your free free (free).
The VMs are free if your time is free.
Earlier quoted context omitted.
Oh god, we might as well start asking why FF didn't support ellipse for what seems like decades. Everyone has different release schedules. IE is a lot more conservative because they support enterprise who are mighty touchy. Grow The Fuck Up Cry Baby. I'm all for IE6 and IE7 whining, they suck. I'm even for IE8 and the entire stop at XP whining. Damn MS for that. But you just sound like a total privileged prat who doe…
You're equating ellipses with things like websockets? Can someone either downvoted or kill this? I've never seen such an abusive and horrid comment on Hacker News!
Just thought you might want to know why nobody has been replying to you.
Earlier quoted context omitted.
IE's moving to a similar "rapid release" schedule with other browsers. Microsoft has played many sneaky pete tricks in the browser wars (such as supporting a CSS standard that couldn't be correctly implemented in Netscape's codebase) but you can't blame their release schedule entirely on that -- Windows users tend to be a conservative lot who are terrified that Microsoft will push something that will break their chea…
conservative lot who are terrified that Microsoft will push something that will break their cheap-ass intranet Due to...everybody say it with me...lack of standards support.
If an institution sticks doggedly to one version of one browser, then it stands to reason any intranet software is going to be optimised for nothing other than that.