You're talking before the fairly meteoric rise in the standard of web programming over the past few years. Before blogs. When tables vs divs was an actual argument. When C++ was relevant in anything apart from high performance programming.
You're also talking about .Net 2.0, pre-LINQ, extension methods and MVC.
And reading your post makes it sound more that you have a chip on your shoulder about bad programmers more than anything else:
lazy, non-challenged developers
ASP.NET is a hulking piece of shit, anyone that tells you otherwise is lying and/or too stupid to realize it
other .NET developers you know are unchallenged nitwits without any sense of vision, any sense of craft. A bunch of me too dim wits who collect paychecks by copying and pasting their way to completion
redmond regurgitating drone army
There are lots of jobs in .Net or java. There's sweet fa for a crap programmer in OSS. Once you realise that is the reason you came across so many crap programmers, perhaps you can understand that there's nothing actually wrong with .Net, it was actually a pretty fucking big revolution. On the other hand you will still come across .Net programmers who think datatables are pretty funky, rely heavily on view state and bizarrely believe .Net controls aren't the spawn of the devil.
As for the rest of it, honestly, 'Win2K server admin', um, it's moved on man. Stop beating the straw doll. 'The world is open now', look a little more objectively at the world we actually live in. Did you even notice the iPhone come out a few years back? Or the Kindle? Or all the other closed source proprietary systems that a me too OS movement gleefully copies, badly for the most part. There's plenty of room at the table for both.
Yes MS have turned into a pretty crap company under Ballmer, but their language teams are still pretty damn good.
The reality is you've become a more experienced programmer. And somehow you're magically attributing it to OSS instead of just knowing more than when you were wet behind the ears.
OSS and proprietary seem on opposite sides of support-systems and customer-facing systems. Proprietary > OSS for users' visual cortex, OSS > proprietary for everything supporting that top layer.
I think part of it is that OSS UI reeks of design-by-committee. Which is something Apple has gotten ridiculously correct. UI needs to be unified and have a flow to it, something which you're more likely to get from a single (highly skilled) person than from a thousand.
I hate reading this. It shows little experience with with open source programs, and ignorance of how open source programs work.
There are hardly any OSS projects with thousands of people- in fact, the only one I can think of is the Linux kernel. Most GUIs in the open source world are worked on by one or two people. Firefox is a good example. Ben Goodger and (one?) other person did essentially all the UI work.
Now, it's true that there are a lot of open source programs with terrible user interfaces. Some of this is because of the strong connection between *nix and OSS, and the primitive toolkits available 15 years ago. Some of this is because it's written without an end user focus. Sometimes the authors don't care. Some of it just sucks.
It's true that Apple has had a lot of success by paying a lot of attention to UI issues. But they're not only different from the majority of OSS software, they're different from the majority of proprietary software. Have you ever tried to explain to someone how to use Opera, or Internet Explorer? Word? Security products like Symantec? The world is filled with baffling crap, it has nothing to do with the licensing scheme.
In short, I am bothered by your generalization because it I believe it to be untrue, and worse, unexamined.
Just look at Ubuntu's interface preferences. Committee. Everyone wants an option, so they're all there. Perfect for alienating everyone who doesn't want all the options. I.e., 99% of the world. Look at <OSS program X> and poke around (especially the popular ones - try Open Office). You'll find bajillions of settings which prevent average people from going deeper and improving their experience.
edit: granted, this is changing in a few areas. Rails, for instance, is convention over configuration - and look at how successful it's been. Mobile apps have been revolutionized by Apple's apps, and developers all over are rushing to mimic it. People are starting to learn, but it's a long way to the top, and the vast majority of the improvements seem to be originating from companies, not OSS groups.
OpenOffice.org is a disaster whose problems go far deeper than the UI.
Also, rails is changing things by preferring convention over configuration? What year is this, 2005?
In the end, here is my complaint: You are taking what is essentially the best case scenario, proprietary or not, and saying that it means software with a copyright license is more usable than software with a copyleft license. Stop doing that, it does the general discourse about software a disservice.
I've yet to see more than low-double-digits of beautifully designed open source programs, and the majority of those were made entirely by one person, often open-sourced because they didn't think they could get enough money to make monetizing it worthwhile. I've been watching for years (though I could be watching in the wrong area). Meanwhile, the rest of the world has been utterly rocketing towards more focus on design, and has a long history of success.
Want more evidence? Look at games. Millions upon millions of players, probably approaching billions of copies sold / downloaded, very few of which are open source games. There's an entire industry oriented around UI/UX and design... and where's the open source influence? Bad Civilization / Quake clones? A lot of the unique designs I've seen have been done by individuals without open sourcing the code, for whatever reason.
And yes, OOo is frightening on many levels. It's a worst case scenario, and I recognize it... but I see it echoed frequently in other OSS projects.
I have not said OSS cannot produce good UIs. I have said there seems to be a trend, and at least I have seen far less. And also take into account that this is not done by enumerating all programs ever produced; this is weighted by success, especially with the design-oriented consumer culture lately.
Better by far, certainly. The Ubuntu crowd has made significant strides in the past few years. But just look at the "Ubuntu One Music Store" image and tell me you don't see glaring inconsistencies in padding, form outlines, and control styles. Then look at other applications and notice which buttons are shaded and when, and resizable edge styles, and why does the shade get that dark near the bottom without a font highlight to counter the harder-to-read lower contrast?
Try comparing native/native or virtualized/virtualized. The vmware and virtualbox drivers lack many functions that are used in native-running ubuntu or windows, for that matter.
I hate trolls like you. A lot of us work really hard on making it the best damn platform ever, and it is, and then some quack who doesn't know anything says "it's just like Windows 95" which shows that they didn't even bother to try it out, or take the tour on ubuntu.com or even watch a recent video of the latest release on youtube. And that just sucks the fun out of life.
Please, actually take a look at it before saying something ridiculous.
Calling users trolls who don't know anything doesn't make me want to give you any credit. Vetinari made me consider that I might be missing out on the best the platform has to offer but you just made me want to uninstall it.
Wow! I was building sites with Zope by 2002. There were far better alternatives than C++, Java and .NET far earlier than 5 years ago. I did lots and lots of Perl since 1996 and some PHP thrown in around 2000. Only used C++ and Java when nothing else would do (mostly because of clients that had too much of the wrong Kool-Aid).
Microsoft has been crappy for a very long time.
About what domain are you talking? Perl and PHP were also quite popular in web development as far as I can recall. And several others.
And yes, Microsoft has been trying to get more and more Unixy over the years, and more and more Appley, and I'll bet they continue doing that in the future. Good for them.
It lacks support for something as simple as automatically inserting the method declarations for interfaces when you had to implement them, let alone promotion of variable declaration to fields. And there is essentially no way to uninline a method. Eclipse has _all_ these things.
And this is still a problem for the 2010 ultimate edition.
I was a .NET consultant since Beta 2 shipped (sometime in 2000 iirc). Before that I was doing a lot of hardcore Win32 dev, mostly doing UI related stuff (was doing antialiased, alpha-channeled interfaces back on Win95 in ASM & Pascal). Long story short, I was pretty deeply entrenched in the MSFT development camp.
But once .NET hit, I was already well into a career doing web development at the dotcom factories in NYC (razorfish, RGA, Rare Medium - plus consulting for FCB/FuelNA, McCann, other agencies). .NET quickly became the platform of choice for a variety of reasons, but looking back I think it was mostly because it was easy and you didn't have to be a rocket scientist to get results. MSFT is fantastic at documentation and the supporting ecosphere for .NET folks was pretty impressive. Gone were all the XML config files, the design pattern saturation of Java, and one of the best* IDE's available for lazy, non-challenged developers, aka Visual Studio.
And it was easy money. I was charging upwards of 250/hr consulting for Pfizer doing the most inane shit you could possibly imagine, shit you could do with two eyes closed and tripping on mescaline. But people were amazed at how quickly you got shit done, but not necessarily because you were some kind of rockstar - it was just easy.
But at some point it grew tiresome. ASP.NET is a hulking piece of shit, anyone that tells you otherwise is lying and/or too stupid to realize it. You start realizing that these other .NET developers you know are unchallenged nitwits without any sense of vision, any sense of craft. A bunch of me too dim wits who collect paychecks by copying and pasting their way to completion.
I was asked about 4 or 5 years ago to take on the CTO role at http://massify.com/. I was initially brought in to consult on getting it built. My first spec and budget was insane because I was relying on the MS crutch. I looked at their goals and what it would take to run this on .NET and the two didn't align. So I stepped back and redid the spec/budget based on OSS. The cost savings were astronomical, somewhere in the neighborhood of 900%. The only problem is that the only Un*x-like system I had ever touched were the NeXT stations from college (fo shizzle).
Considering that I'm entirely self taught (I went to Art School) and the way I had taught myself was throwing myself into the fire, I figured I could figure it out and make it work. And I did. I made a few mistakes of course, but as of today - I am not longer at Massify - they are still running with no unexpected downtime for roughly ~$500 a month.
And now that I've lived in the OSS/Unix world for the last 5 years, I will never ever ever go back to Windows or .NET (though I'm the CTO for a shop whose system was written in .NET - we are currently porting it over to OSS stack). It's so much better over on this side of things, I can't even enumerate the ways.
First of all is cost savings. As a CTO, that's your primary gig (usually). When I started Massify, hosting alone was ~6K a month. After a few months of hard work, we got it down to $500 a month by pushing it into the cloud. This includes a self-scaling application that does HD media conversion, CDN hosting and distribution, the whole nine. Not a trivial application by any stretch of the imagination.
Second of all is ease of administration. The learning curve was steep, don't get me wrong, but fuck all if I'll ever go back to Remote Desktop and the bullshit that is Win2K server admin. Life is too short. I have SSHd and PowerShell rocking now for the .NET app we are currently maintaining/porting, but it's such a sorry knock off of the real thing. Gimme bash or zsh or give me death is my new motto.
Third of all is the pace of technology. Nobody is innovating in the .NET space except for MS. Everyone else is a me too, redmond regurgitating drone army. OSS moves much faster. A problem you had a month ago was probably just solved today. And you didn't have to wait for MS to do it and you don't have to pay someone bizarre licensing fees for it.
Finally, the culture is so much better. People share, people contribute, there is a collectivism that is lacking from the .NET world where the old shareware model is the status quo.
I'm not sure how MS comes back to the fore, I think it's too late for them. The world is open now, and the closed model only flies for people without a clue. To become dominant again, they'll have to open up, truly open up. But, I think it's too late. There is better stuff, for free, out there and without an OSS model, they'll never be able to catch up.
Just my .02.