5 ms·
To be brutally honest about .Net, and I use it and like it myself, the reason there's no startup market in it is because until MVC there was no point developing
by mattmanser 16y ago
To be brutally honest about .Net, and I use it and like it myself, the reason there's no startup market in it is because until MVC there was no point developing in it.
ASP.Net controls, postbacks for everything, view state, a general hiding of the actual power of ajax and an obsession with using tables made .Net a terrible web development environment if you had any clue what you were doing. The html it spat out was a bloated horrible mess, web services were anything but unless you really slogged your way through some pain, ashx pages and the directory structure just felt plain wrong.
That said I'd almost, almost, switched to using python/django and then I had a look at MVC and it did everything I needed. Full control over html, nice code separation, a nifty ORM for taking away the pain of basic crud. An alright templating system easily extensible using extension methods. And 3.5 brought some tricks using LINQ and anonymous methods.
I still know I need to learn a few more languages, but MVC has allowed me to copy everything I felt was the 'right' way of developing webs apps from rails/django without having to actually learn a new language and dev environment.
If you weren't worried about performance and didn't want to learn how to actually program, the old ASP.Net was ok for very quickly throwing out web apps for the 10 people in HR. Much more than that required an in depth of knowledge way beyond most .Net programmers, with most of those people being multi-lingual anyway and tending to opt for the cleaner code the alternatives offered.
I don't feel that's the case anymore, but it's way behind in adoption at the moment.
You still hit the occasional WTF in MVC where if feels as if someone wrote a part of the system without reading the memo about flexibility (the validation solution in MVC, for example, is terrible, although not finished and LINQ to entities can be frustrating).
tl;dr;? No startups because until recently good web development in .Net was actually really hard. MVC's changed that.
- barrkel 16y agoThis is false because it relies on an incorrect assumption: that if you were using .NET to do web development prior to MVC, you had to use ASP.NET. When I was writing .NET web applications, the sum total of ASP.NET integration was implementing IHttpHandler and friends - not much more than access to the request and response streams. You can build your own lightweight framework, which, being lightweight, isn't a big deal.
- bad_user 16y agoThere was also MonoRail, an MVC framework inspired by Rails ... http://www.castleproject.org/MonoRail/ http://www.castleproject.org/MonoRail/
- henrikschroder 16y ago+1 for this. We've been working in C#/ASP.Net for 7 years now, and we always stayed as far away from ASP.Net controls and Web Forms as possible. Some things we liked such as master pages and making a class hierarchy for the pages to inherit, so we used that. For the past two years we've been using our own light-weight MVC framework. C# and IIS are very versatile technologies, you don't have to buy into the entire Microsoft tool chain to use it, you can use whatever parts you want.
- swilliams 16y agoThis is true, but it also reinforces the statement that WebForms suck. It was so broken, that you had to write your own framework to deal with it.
- henrikschroder 16y agoTo be fair, ASP.Net was a better technology than JSP, which were the main competitors back then. On top of ASP.Net, Microsoft built Web Forms, which is really bad when it comes to building large, scalable web applications. Unfortunately, Microsoft kinda stopped there, whereas the Java community continued and made Struts and Spring and whatever else they do now. And that highlights the other problem with using the Microsoft stack: There's no community around popular frameworks, the absolute majority use only what comes out of Redmond, and if nothing comes, then they're just stuck. In the Java community, there were loads of MVC frameworks, people built it, and the popular ones flourished, and people could move on. In the .Net community, nothing really happened until Microsoft themselves made an MVC framework. So being on the Microsoft stack is more like a roller-coaster than a smooth progression, and that is a problem, because it's not very startup-friendly.
- evo_9 16y ago
- megablast 16y agoThis is why I hate .Net, it hides everything, changes the normal pages work. I guess it does this to make it easier for people who don't understand what is going on, but it just frustrates me. I understand the way POST and servers work, I don't feel the need to have to unlearn that and learn Microsoft twisted version of the web. And the horrible code and javascript it puts on a page is just ugly.
- henrikschroder 16y agoYour hate is completely misguided, the feature you are complaining about is Web Forms. .Net is a set of class libraries and a virtual machine, your rant would carry a bit more weight if you at least got the basic terminology right. (Although it has to be said that even Microsoft can't get it straight all the time either)
- Daishiman 16y agoNo, he's completely right. Regardless of what the framework may or may not allow, the fact of the matter is that most .NET web applications are using the full ASP.NET stack, which means that it's the place where most of the mindshare is, so for all practical purposes it would be more difficult to find people who aren't using it, and if you aren't using it then you're probably using another technology stack. For that matter, when using just the base .NET framework for web development, I fail to see any advantage over Python or Rails beyond familiarity, and many disadvantages.
- henrikschroder 16y agoRegardless of what the framework may or may not allow, the fact of the matter is that most .NET web applications are using the full ASP.NET stack Yes, but that is not what he said. That the majority of .Net developers are completely hooked on the entire stack is a problem when it comes to recruiting people. That is not the same thing as claiming the .Net stack is rigid and inflexible.
- megablast 16y agoThanks, I will try to clarify my rants better in the future :) I have only looked at web forms, I guess. Never actually formally been taught anything to do with .net. That was enough to turn me off.
- jonny_noog 16y agoThat said I'd almost, almost, switched to using python/django and then I had a look at MVC and it did everything I needed. I had almost convinced one of my ASP.Net developer friends who was well fed up with web forms to jump ship to Ruby and Rails with me when .Net MVC came out. After that, there wasn't a whole lot of a compelling reasons for him to start on a whole new language and framework anymore. If only they'd waited a few more weeks! Curse you Microsoft!