Hacker News new | ask | show | jobs
by melc 4781 days ago
At the server side it simply gives no choice but proprietary and unreliable ms systems and a weak app/web server (iis). The desktop client side is only good for ms clients. For the devices realm there is nothing to talk about really and regarding windows phone it's a bit early. I've worked with .net in the past but now i usually avoid it as much as i can.
1 comments
sergiotapia 4781 days ago
"Weak" Hah! I'd like to see some references to that claim.

Oh wait, here it is: [1] - melc's ass.

============

IIS has given me a TON of performance right out of the box with a fantastic GUI editor for settings. StackOverflow a website with MILLIONS of monthly hits runs fine with IIS.

link
melc 4780 days ago
Even though i don't like your attitude i will try to give a little info that may assist other people. The reference i have is a couple of enterprise level projects (information systems for the public sector) built with c#, iis6 for the server side parts, sql server 2005 and win2003 R2 servers. Also sharepoint which was quickly replaced due to slowness and high resource consumption.

- Win2003 servers had a limit on the amount of RAM so that was a bit of a problem along with the sluggish performance compared to linux based servers that we are used to work on. Did we have a choice to switch operating system? hm.. not really

- sql server was pretty good it did much better than i expected and i really enjoyed all the functionality out of the box, but that was until we reached more than 10 millions of records in some tables, then it was no more fun but that could obviously happen with any database. Did we have a choice to switch database? hm.. not really

- iis6 whether you like it or not you have no other choice. Having a background with jee application servers of different vendors where i could configure and customize them in any level, switch them with other vendor solutions and do plenty of architectural tricks.... i did find iis situation a bit weak

- programming with c# was great, but if we needed any good libraries/APIs did not exist or we had to pay, not many choices here either and as with all other parts targeted only to ms platforms

Stackoverflow is really great, and i was sure that in the past i had stumbled upon a post about stackoverlfow architecture i.e. http://highscalability.com/blog/2009/8/5/stack-overflow-arch... to be honest i was a bit suprised that they were using ms technologies. To me the bottom line is that for large scale projects based on ms technologies you will eventually need to invest money and time to proprietary solutions without many architectural choices, at least not as many as other platforms provide. Of course that is certainly not a problem if one works only on ms platforms.

link