Live data from Hacker News

Leaving .Net

whatupdave.com

31–40 of 122 posts

Re: Leaving .Net

#31
post #11

Compared to anything except rails, ASP.NET is pretty good. Yes, the viewstate / gridview bs is annoying and should not be used. The problem is primarily that corporate dev departments want interchangeable parts. They want to be able to hire a developer and him to know the API that everyone is using. They don't want magic. They want everything spelled out so that the code looks identical to the UML and identical to th…

It appears you've never heard of Django or Pylons/Pyramid.

[deleted]

Re: Leaving .Net

#32

Dave 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…

I think the core rails team is pretty small and focused. The benefit of it being open source is that an army of people wanting to make a name for themselves are combing over their code to make sure all the I's are dotted and T's are crossed. The quality of Rails obviously doesn't scale with the number of contributors - there are only a few core contributors and a heckuvalot of casual contributors. Makes sense to me.…

I'm relatively new to web development, and I've never worked in an enterprise environment using enterprise software/frameworks, but I honestly cannot understand why anyone given the choice and assuming the cash is the same would choose to go the MS route. I admit naïveté.

A lot of reasons. The big reason is that for a LOT of people, open source isn't all that compelling as a feature on its own. For certain classes of people its the most important thing in the world, for other people it doesn't add much value. And for maybe an equally large subset, it's actually a negative.

At the end of the day each person/org has to decide what is important to them and optimize accordingly. For you open source may be the most important thing in the world, in which case, the choice is obvious. But there are millions of people who have made a different decision.

Re: Leaving .Net

#33
post #28

Earlier quoted context omitted.

Is that how you think of the open source world? A bunch of people writing jquery scripts for joomla? You may want to investigate a bit more (hint: google, facebook, yahoo and a bunch of other all rely on very solid and well documented high quality open source projects).

No it's not what I think of it, it's what I've been exposed to. I've done some open source projects myself, although that was in flex and nobody really picked up after me ;-) I'm a strong believer in Open source, I used open-bsd for years and I really enjoy Mono and Monotouch. However the state of 95% of open source project is rather dirty and messy, scruffy development.

95%? Would you like to back that number up with anything?

Even if I grant you that arbitrary statistic, it says nothing about the state of the selection developers have for open source projects. If 5% of all open source projects are good, that leaves an enormous quantity of good open source projects. What languages do you code in?

Re: Leaving .Net

#34
post #11

Compared to anything except rails, ASP.NET is pretty good. Yes, the viewstate / gridview bs is annoying and should not be used. The problem is primarily that corporate dev departments want interchangeable parts. They want to be able to hire a developer and him to know the API that everyone is using. They don't want magic. They want everything spelled out so that the code looks identical to the UML and identical to th…

Stackoverflow is built in ASP.NET MVC, which is magnitudes better than normal ASP.NET (and ships with Visual Studio 2010).

Re: Leaving .Net

#35

Dave 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…

GCC targets way more platforms and compiles way more languages than the Intel and MS compilers do. That's not an apples and oranges comparison.

I think you mean that is an apples to oranges comparison (or its not an apples to apples comparison).

In any case, fair enough. I tried to detangle the contributors, and while its easy to do for language, it's harder to for target. I suspect 90% of the commits are ARM or x86/AMD64, but w/o spending more time than I care to, it's hard to know.

With that said, you'd still expect, with GCC long history of being open source and open source being such a clearly superior dev model to have surpassed most commercial compilers, but that hasn't been the case in perf. Now maybe one might make the argument that perf has never been the metric for gcc, but it has always been portability. But that would also lend credence to why open source is not an ideal model for many companies -- your (the open source project's) metric of success is not the metric that we care about.

Re: Leaving .Net

#36
post #26
post #8

Funny, 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.

I agree with you. The languages, documentation, and standard libraries of .NET are awesome. The community is definitely lacking though. These days you can get excellent help on IRC about F# and on stackoverflow for everything, but there is not really a spirit of "lets build something cool" outside of F#.

but there is not really a spirit of "lets build something cool" outside of F#.

Can you give an example of something that is cool? Everytime I think of something cool, I can think of something done on the MS stack, but maybe our definitions are different.

Re: Leaving .Net

#37

Dave 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…

I think the core rails team is pretty small and focused. The benefit of it being open source is that an army of people wanting to make a name for themselves are combing over their code to make sure all the I's are dotted and T's are crossed. The quality of Rails obviously doesn't scale with the number of contributors - there are only a few core contributors and a heckuvalot of casual contributors. Makes sense to me.…

The first question when I suggest ANY piece of software at ALL in my 'enterprise':

"Is it supported? Who supports it? Is the support 24x7?"

$10,000 a month, depending on the applicatin, is chump change.

Although, some people do appreciate the value of open-source when a vendor takes two months to solve a problem in their proprietary mess of 'software solutions'.

Re: Leaving .Net

#38
post #11

Compared to anything except rails, ASP.NET is pretty good. Yes, the viewstate / gridview bs is annoying and should not be used. The problem is primarily that corporate dev departments want interchangeable parts. They want to be able to hire a developer and him to know the API that everyone is using. They don't want magic. They want everything spelled out so that the code looks identical to the UML and identical to th…

"You'd have a corporate list of approved gems in specific versions that were 3 years old (probably whatever comes with a default install of RedHat)"

You made me choke on my cola. SO TRUE! I'm laughing out of sadness.

Re: Leaving .Net

#39

Dave 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…

  > 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.
Oh? Interesting; I thought that gcc was one of the better ones. Could you elaborate?

Re: Leaving .Net

#40

Funny timing. I've been a .net developer, mostly web - some desktop, since the first release. I am currently going through the interview process with a company that focuses on rails. Part of me is excited, I've been wanting to get away from MS technologies for a couple of years now. Part of me wonders if I am going to miss the safety net of the compiler and IDE, and if the grass truely is greener. I started out doing…

I've been doing development with Rails on personal projects and while Netbeans isn't Visual Studio, it's still a pretty solid development tool. I also dig how the local Rails environment shows you every call that's being made, plenty of solid logging integration, etc. Also the gems and other libraries being open source and freely available is great, and Ruby crushes C# with regards to Metaprogramming if you're going…

ASP/VBScript

Are you referring to classic ASP? VS (for .NET) has great debugging features.

Post reply on HN