Leaving .Net
whatupdave.com
Leaving .Net
1–10 of 122 posts
Re: Leaving .Net
#2Eh, whatever dude.
Re: Leaving .Net
#3Romantic, starry-eyed, hopelessly idealistic and mostly true.
Re: Leaving .Net
#4Amen. This pretty well articulates what I experience at work with .NET on a day to day basis. When I code other stacks there's always a library or a plugin to do X. At work its always "we can buy something or build it in house." Frustrating to say the least.
Re: Leaving .Net
#5Previous (extensive) discussion: http://news.ycombinator.com/item?id=1719277
Re: Leaving .Net
#6Previous (extensive) discussion: http://news.ycombinator.com/item?id=1719277
Looks like his blog was previously on Tumblr, so the dup-detector didn't catch it.
Re: Leaving .Net
#7Yeah, I dunno I like/love c# (depending on post/pre 3am...). Plus Mono really kick's ass and is a lot of fun to play with (esp. monotouch). I seem to be able to find free stuff off codeproject or stack whenever I need it. Even on the UI it's pretty painless if you avoid MS's stuff and just go with jquery and open standards. I kinda dig it to be honest, and monodevelop is a pretty nice IDE for mac now. All in all coming along quite nicely.
Re: Leaving .Net
#8Funny, but I felt the opposite. I'm sick of open source software that's documented like a donkey's ass and that never works. And all those 'developers' that can't be productive and create things, instead all they're doing is plumbing joomla with jquery while high on json.
I guess it's like a mid life crisis, you just have to flip side.
Re: Leaving .Net
#9Yeah, I dunno I like/love c# (depending on post/pre 3am...). Plus Mono really kick's ass and is a lot of fun to play with (esp. monotouch). I seem to be able to find free stuff off codeproject or stack whenever I need it. Even on the UI it's pretty painless if you avoid MS's stuff and just go with jquery and open standards. I kinda dig it to be honest, and monodevelop is a pretty nice IDE for mac now. All in all comi…
Mono is where the innovation is happing now, e.g projects like Manos de Mono
Re: Leaving .Net
#10Dave has some reasonable points, and frankly I think MS is going where he'd like them to go.
But he does miss the boat on a few things.
One thing that I do think he discounts too much is the surprising effectiveness of small focused teams. In the same way a small startup is more effective than a lumbering machine, a small team of devs is often more effective than 1000 loosely organized volunteers. The classic example is GCC which has probably 10x more people working on it than any commercial compiler, yet the Intel and MS C/C++ compilers generally kill it. Not to mention other less popular compilers like IBM xlc and DEC's Alpha compiler.
The contribution list to RoR is impressive, but the quality of the product doesn't scale with the number of contributors.
I think the question MS has to ask is "do we forego control to possibly get an incremental increase in product quality?" What I've found interesting is the speed at which Silverlight and ASP.NET MVC have improved over the past few years. With relatively small developer teams, they've increased in quality as fast as any open source projects I know of.
The other thing he gets wrong is he conflates framework developers with application developers. And I think this causes him to see a skewed world-view that developers are "waiting" for Microsoft. In general, app developers, are not waiting for MS to do anything. You have tight deadlines and are trying to find the best solution today. You take a snapshot of the world right now and pick the best solution (or starting point). You don't have the time to ponder what might be available in eight months.
Most ppl on the MS stack are app developers. Always has been the case.