Hacker News new | comments | show | ask | jobs | submit login

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.

> PowerShell, the current standard shell for modern Windows version is really powerful. Get with the times.

Do you actually use PowerShell as an interactive console on a daily basis? When I tried to learn it, it seemed powerful for scripting, but nearly impossible to use interactively. I ended up using bash under cygwin, because it seemed to be the best option available.

Yeah I use it most days. I use Console2 though (open source console window replacement), which removes some of the physical limitations I'd otherwise have to put up with.

It's perfectly fine interactively unless you've got shit between your ears.

You don't have to buy an Android phone to debug Android webkit. Just get the toolkit and run the emulator. (Which is a bit slow unless you install an x86 image and Intel HAXM).

The same applies for Apple, you just have to download their SDK and use their Simulator - though that requires Apple hardware.

You can run an emulator for both the iPad/iPhone iOS stuff on top of an Apple Mac OS X machine, same with the Android development environment. At that point you can test your website using WebKit on a "mobile" device without actually owning a mobile device.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact