4 ms·

I agree with this sentiment, and would add a few (somewhat) related reasons. a.) 'Planet Microsoft'. By this, I mean the gravitational pull all MSFT products

by mxh 19y ago

I agree with this sentiment, and would add a few (somewhat) related reasons. a.) 'Planet Microsoft'. By this, I mean the gravitational pull all MSFT products seem to exert on one another, apparently by design and decree of the marketing department. With open-source stuff, it seems like I can mix-n-match components pretty freely. I can use Django on BSD, or Linux. With MySQL, or PostgreSQL. I can use its built-in templating, or not. With MSFT, it seems like I'd better be using Win2K3+SQL2K5+IIS6+ASP.NET or I'm taking my life in my hands. (And, when upgrade time comes, I better upgrade 'em all, or I'll have problems. And I better upgrade every system or they won't talk to each other.) Presumably MSFT could make its products more standalone, but prefers not to. b.) Inevitable screwage. I believe MSFT's goal is to establish itself as an unavoidable presence in the IT business (ala the bad old days of DOS) and then use that position to demand money. For the moment, thanks to open standards, they can't do that. I'm not interested in helping them change that by using/endorsing their technology stack. c.) MSFT MVPs. More generally, MSFT people. With all due respect to any Planet Microsoft hackers hereabouts, there is an enormous lack of perspective found in people who've only used MSFT tools; they tend to think 'One Microsoft Way' is a viable approach to building code, and not just an address. If you're reading this, and that offends you, I hereby acknowledge that there are exceptions, and you're probably one. I don't want to flame anyone, I just want to share an honest reason why I'd prefer to avoid the MSFT stack.

hello_moto 19y ago
What makes upgrade better in other technology world compare to MS? Last time I checked, other technologies are rarely backward compatible, cut support for previous version not too long after new release is out, tons of controversies on newer releases. One choice is not to upgrade at all. No big deal I assume. It's not like you're going to write a lot more of new code. What makes you think open standards are better? just because they're open thus they're better? how about the technology value behind it? 'One Microsoft Way' isn't overly bad. At least it doesn't waste your time trying to decide which one is better (Rails vs PHP vs Django vs TurboGears vs Pylons vs Symfony vs JSF). You know what, these are the example of wasting your time: Servlet (need template)-> JSP/Servlet (not good enough) -> Struts (some design mistakes) -> Spring (mkay.. well) -> JSF (oh, we finally catch ASP.NET up) PHP -> PEAR -> Symfony/CakePHP/Ignition I wouldn't say Python stack is "wasting your time" yet but time will tell how long Django/TurboGears/Pylons will last. They're cool frameworks and I like Python more than C#. But I haven't really heard much from their communities lately other than the Django book had finally been released after deadline slips (I know they have good reasons but whatever).
- g-e 19y ago
  "Last time I checked, other technologies are rarely backward compatible" 7 years ago I created one of the first Web2.0 websites in PHP. It became very popular and is still up and running and used by hundreds of thousands of people a month. Without any modification. On a managed server that has been updated to new versions of LAMP countless times. I also wrote ASP (not .net) code at that time. It is long dead and gone.
ntoshev 19y ago
c) are my thoughts exactly. Few months ago I even wrote about why does it happen: http://nik.blue-edge.bg/?p=17 http://nik.blue-edge.bg/?p=17

by mxh 19y ago

hello_moto 19y ago

What makes upgrade better in other technology world compare to MS? Last time I checked, other technologies are rarely backward compatible, cut support for previous version not too long after new release is out, tons of controversies on newer releases. One choice is not to upgrade at all. No big deal I assume. It's not like you're going to write a lot more of new code. What makes you think open standards are better? just because they're open thus they're better? how about the technology value behind it? 'One Microsoft Way' isn't overly bad. At least it doesn't waste your time trying to decide which one is better (Rails vs PHP vs Django vs TurboGears vs Pylons vs Symfony vs JSF). You know what, these are the example of wasting your time: Servlet (need template)-> JSP/Servlet (not good enough) -> Struts (some design mistakes) -> Spring (mkay.. well) -> JSF (oh, we finally catch ASP.NET up) PHP -> PEAR -> Symfony/CakePHP/Ignition I wouldn't say Python stack is "wasting your time" yet but time will tell how long Django/TurboGears/Pylons will last. They're cool frameworks and I like Python more than C#. But I haven't really heard much from their communities lately other than the Django book had finally been released after deadline slips (I know they have good reasons but whatever).

g-e 19y ago
"Last time I checked, other technologies are rarely backward compatible" 7 years ago I created one of the first Web2.0 websites in PHP. It became very popular and is still up and running and used by hundreds of thousands of people a month. Without any modification. On a managed server that has been updated to new versions of LAMP countless times. I also wrote ASP (not .net) code at that time. It is long dead and gone.

ntoshev 19y ago

c) are my thoughts exactly. Few months ago I even wrote about why does it happen: http://nik.blue-edge.bg/?p=17 http://nik.blue-edge.bg/?p=17