Live data from Hacker News

Supporting IE Is Too Much Work

bartvanzon.com

71–80 of 176 posts

Re: Supporting IE Is Too Much Work

#71
post #3

I honestly think a lot of hacker types really do live in a bubble where they think it's still 2000, Microsoft is still the same evil company they were, Apple still can do no wrong, most people now use Macs "if they know what's good for them", RoR, node.js and Python are really the only valid technologies for back end development and so forth. Certainly plenty of folks out there using the aforementioned technologies a…

This is a lot of FUD style arguments please let me elaborate:

a) Developing on windows is absolutely attrocious. If MS wants me to develop on windows, PUT SOME FUCKING EFFORT INTO IT.

b) Developing for Chrome, I support ALL operating systems.

c) Developing for FF, I support ALL operating systems.

d) Developing for Opera, I support ALL operating systems.

e) Developing for Safari, I support OSX, Windows XP, Vista, 7, 8.

f) Anything webkit related is supporting the iPad AND Android Tablets, and iPhone, and Android. Even without a special experience.

g) Developing for Mobile is an effort. Unfortunately. If you want a truly mobile experience.

Let's talk about IE now:

IE 9 is only supported IN WINDOWS 7. That's right, no XP, an OS which every other browser other than microsoft's support. So there.

If I allow IE users to use my site, I don't care if I make a giant "we don't fucking support IE" banner, people will expect it to work. And I will be the bad guy. If they visit my site and no IE support "please take 20 seconds to install chrome". The business will dictate if those people not willing to install chrome/chrome frame (no admin access required) are important enough to support.

Now... ITS 20-fucking-12 and windows still has the biggest piece of absolute shit terminal tool possible, with no alternative in sight. Furthermore terminal programs that work in linux, work in mac, so you get REAL developer tools. There is nothing decent like that on windows. Many things I need for my program to run DOES NOT WORK IN WINDOWS, so it's on MS' head to make them work. Apple saw that having a fully custom OS meant developer alienation. That is why they made OSX. People immediately praised it for it's ability to run dev tools, and developers were happy.

Now. Apple does evil. Apple is 2x as evil as MS ever was or will be. However Apple currently innovates (or did). However I can't argue with the fact that they have good fucking hardware. Developing on windows means piece of garbage hardware, shitty laptops till maybe a few months ago, who still cant fucking get touchpads right. YES TOUCHPADS SUCK ON WINDOWS STILL, 2012! On mac, touchpads are pleasant. There I said it, Windows is a terrible operating system from a user experience perspective, and that includes hardware.

So now why would I support IE? Look at my list up top. Please tell me what MS does to make me want to support IE? What benefits I gain? I pretty much only get users who don't know left from right mouse buttons, and unless I'm facebook I probably don't care about them anyways.

Edit: I am in no way saying IE 9 is bad. In fact IE 9 has multi-process, something I wish firefox implemented already. Performance is good enough for most websites. And the W3C support is up to par with normal browsers, though still a bit lagging.

Re: Supporting IE Is Too Much Work

#72
post #68
post #51

Earlier quoted context omitted.

Has it occurred to you that at least you're legally allowed to virtualise Windows+IE for web development testing? On the Windows side of things, devs aren't even allowed to virtualise MacOS! And you complain about lack of options for Mac developers! Pot calling the kettle black?

Point conceded. Though, certainly a +1 for choosing Mac as your primarily development environment; as it can run all the other operating systems you'd care about (:

True, though many of us feel very comfortable developing on Windows. Seems unfair that we should pay the Mac hardware tax just to test with Mac browsers when Apple could provide OSX on a VM, license-restricted for testing purposes or similar.

Re: Supporting IE Is Too Much Work

#73
post #40
post #3

I honestly think a lot of hacker types really do live in a bubble where they think it's still 2000, Microsoft is still the same evil company they were, Apple still can do no wrong, most people now use Macs "if they know what's good for them", RoR, node.js and Python are really the only valid technologies for back end development and so forth. Certainly plenty of folks out there using the aforementioned technologies a…

You're right, supporting IE9 isn't hard at all. IE8 is the problem. It's amazing how many people still use 8 -- and it's because of corporations who are slow to update software. The thing that annoys me is that Microsoft knows that businesses will use the current version of IE for many years to come, so they should be as cutting edge as possible, but they don't seem to care.

The reason for a large IE8 contingent is because its the latest version of XP will support. The fact that businesses are using a TWELVE YEAR OLD operating system is the main issue here. Sure, maybe they could've made IE9 work with XP, but if people aren't even willing to update their OS once a decade, are we really sure they'll upgrade their browser?

Re: Supporting IE Is Too Much Work

#74
post #3

I honestly think a lot of hacker types really do live in a bubble where they think it's still 2000, Microsoft is still the same evil company they were, Apple still can do no wrong, most people now use Macs "if they know what's good for them", RoR, node.js and Python are really the only valid technologies for back end development and so forth. Certainly plenty of folks out there using the aforementioned technologies a…

IE9 is not that bad. To prove to myself that it was not, I forced myself to use it as my main browser for a while. It was not painful at all. It had reasonable speed, and although lacking some CSS3 features that are nice, it is generally a decent browser. And it runs one of my Canvas demos much more smoothly than Chrome or Firefox, since it hardware accelerates canvas rendering.

It's not that IE9 is bad. It's that IE is not only IE9. It's IE7,8,9 and 10. Testing on all IE versions takes as much time as testing on all other browsers. They all have their unique issues.

And you can't run all of them on one machine safely.

And you usually use IE7 as the least common denominator, thus sacrificing functionality.

Re: Supporting IE Is Too Much Work

#75
post #14
post #3

I honestly think a lot of hacker types really do live in a bubble where they think it's still 2000, Microsoft is still the same evil company they were, Apple still can do no wrong, most people now use Macs "if they know what's good for them", RoR, node.js and Python are really the only valid technologies for back end development and so forth. Certainly plenty of folks out there using the aforementioned technologies a…

After the IE 6 pain no web developer will forgive microsoft for the time lost and pain. They test for IE only because lots of people use it or because their jobs require this, nobody likes IE, it always had bugs, was insecure and most important non standard. IE9 is closer to normal, but microsoft lost is trust, they had the chance to change something much earlier and they did nothing, they are only acting now because…

I cannot agree with the "lost trust" enough. MS lost trust with it's attempt to strange with IE. Honestly if IE was the only browser, I'd be ok, if it was a good browser. Only when people started doing everything in their power to avoid it did MS even pick up the keyboard to fix bugs.

Re: Supporting IE Is Too Much Work

#76

It's time we separate "full-stack" developers from "front-end" and "back-end" guys / gals. I've met some brilliant folks who write amazing Ruby but say they hate CSS or JS. Those are "back-end" guys. A "front-end" person will write CSS and HTML markup without a problem and will always make sure it's cross-browser compatible. I've been coding front-end markup for 7 years now and I've never come across a IE-specific is…

> I've never come across a IE-specific issue that took longer than 5 minutes to resolve, and 99% of the time my markup worked without any "hacks" at all.

Now that's a flat-out lie right there.

Re: Supporting IE Is Too Much Work

#77
post #66

Earlier quoted context omitted.

> If Microsoft facilitated having VMs of each windows installation + browser version available for that OS to developers Which they do, they've been offering complete VM images with various combinations of Windows and IE for some time, the current offering is XP + IE6, Vista + IE7, Win7 + IE8 and Win7 + IE9: http://www.microsoft.com/en-us/download/details.aspx?id=1157... While the images are for VirtualPC, I've yet t…

> Which they do, they've been offering complete VM images with various combinations of Windows and IE for some time, the current offering is XP + IE6, Vista + IE7, Win7 + IE8 and Win7 + IE9 I've used the IEVMs project on github to install these VMs before; it failed. I'm trying it again as we speak, maybe it's a viable solution, maybe not. > IE9's devtools are significantly better than IE8's: more feature and much mo…

> I've used the IEVMs project on github to install these VMs before

I don't know about that, downloaded them straight from Microsoft's website.

> Obviously the problem here is that IE9 represents 25% of the currently in-use IE browsers

Note that IE9 can be switched to IE8's engine (there are differences with the official IE8 but not that much, so most of the rough work can be done with IE9's devtools even using the IE8 engine).

> IE9 has a ways to go before it's new amazing developer tools are valued significantly.

I did not say IE9's devtools were "amazing", because they are not (unless your only comparison basis is IE6 devtools or pre-firebug Firefox devtools that is). But they are significantly better than IE8's (let alone 6/7)

Re: Supporting IE Is Too Much Work

#78
post #9
post #4

Earlier quoted context omitted.

It's actually much more work to test on a Mac when developing on a Windows machine since Apple is so protective of OS X that they don't allow it to run in a vm. Which is sad because I like to have all kinds of users but it's really really difficult to accommodate for all you guys browsing on a mac. Please hit me with hints to make life easier for myself if you have some...

Agreed. Not a single person in my company (a whole five people) owns a Mac, and it leaves us with no real options on the compatibility front. I prefer to develop in Linux, but I have a Windows partition since it's easy enough to do. But none of us have the pocket change lying around to buy a redundant machine just to check up on some demonstrably minimal segment of our users who use Safari on OS X. I'll put in the ti…

> I'll put in the time to boot into a Windows partition and double-check IE9, but when it comes to OS X/Safari, I've got little recourse but to crossing my fingers and bank on Safari's Webkit rendering being the same as (or close enough to) Chrome in Windows and Chromium in Linux.

Might want to try the Windows version of Safari then. The JS engines in Chrome and Safari have some quirks between them and can behave differently in some scenarios, mostly things that JSLint would catch though.

Re: Supporting IE Is Too Much Work

#79
post #3

I honestly think a lot of hacker types really do live in a bubble where they think it's still 2000, Microsoft is still the same evil company they were, Apple still can do no wrong, most people now use Macs "if they know what's good for them", RoR, node.js and Python are really the only valid technologies for back end development and so forth. Certainly plenty of folks out there using the aforementioned technologies a…

This is a lot of FUD style arguments please let me elaborate: a) Developing on windows is absolutely attrocious. If MS wants me to develop on windows, PUT SOME FUCKING EFFORT INTO IT. b) Developing for Chrome, I support ALL operating systems. c) Developing for FF, I support ALL operating systems. d) Developing for Opera, I support ALL operating systems. e) Developing for Safari, I support OSX, Windows XP, Vista, 7, 8…

Your blinders are industrial grade.

Developing for Windows is in fact a pleasure. MS have more love for their development community than you realise, and this is reflected in the tools and technology they provide. .Net is incredible. Really.

> IE 9 is only supported IN WINDOWS 7

Supporting WebKit in iOS requires me to BUY AN IPAD just to test properly! Supporting WebKit on Android requires me to buy an Android phone just to test properly! Your argument is invalid.

> Now... ITS 20-fucking-12 and windows still has the biggest piece of absolute shit terminal tool possible

The actual console window annoys me, I'll grant you that, but only in terms of fixed width and columns. PowerShell, the current standard shell for modern Windows version is really powerful. Get with the times.

> Developing on windows means piece of garbage hardware, shitty laptops till maybe a few months ago, who still cant fucking get touchpads right

Ummm... blame the manufacturers? Microsoft doesn't own Asus, Acer, HP, or any of these other companies.

The topic is whether or not to support a particular major browser, not whether you prefer Windows as a development environment or working with budget hardware. I would suggest you step back from your frothing-at-the-mouth hatred of Microsoft and determine how up-to-date, relevant and accurate your information actually is.

Re: Supporting IE Is Too Much Work

#80
post #3

I honestly think a lot of hacker types really do live in a bubble where they think it's still 2000, Microsoft is still the same evil company they were, Apple still can do no wrong, most people now use Macs "if they know what's good for them", RoR, node.js and Python are really the only valid technologies for back end development and so forth. Certainly plenty of folks out there using the aforementioned technologies a…

This is a lot of FUD style arguments please let me elaborate: a) Developing on windows is absolutely attrocious. If MS wants me to develop on windows, PUT SOME FUCKING EFFORT INTO IT. b) Developing for Chrome, I support ALL operating systems. c) Developing for FF, I support ALL operating systems. d) Developing for Opera, I support ALL operating systems. e) Developing for Safari, I support OSX, Windows XP, Vista, 7, 8…

>> So now why would I support IE?

Because you're not developing for yourself. You're developing for users.

Also, just because you're developing on browsers that exist on both platforms doesn't mean you're supporting all operating systems. If you tested on any WinOS you'd understand that.

Post reply on HN