3 ms·
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 c
by fleitz 16y ago
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 the Use case document as signed off in triplicate by a committee of managers. In corporate dev you get promoted for doing everything to the letter not something new and exciting.
I've seen pages with more than 100 checkboxes on them and arranged in a grid, it was like someone when mental with excel putting a checkbox in every cell.
To be honest, if rails were adopted by corporate dev you'd see things like not being allowed to use haml / sass, etc. 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)
I'd bet if you look at what Atwood and Spolsky are doing over at StackOverflow on ASP.NET it's probably a reasonable choice of defaults and open source. There are a lot of stupid decisions you can make with .NET and I agree that the community is definitely lacking, but largely it's a mindset issue that stems from the socio-political environment they program in.
At my last job you should have seen the shit show that ensued when someone in management found out the DLLs I was handing off to other teams were written in F#, even though it was the .NET team and not the C# team. Apparently, unbeknownst to me, the largest cause of developers leaving a company is due to being hit by buses, and a dependency on FSharp.Core.dll is just unacceptable and could never be part of the automated build process.
- Pewpewarrows 16y agoIt appears you've never heard of Django or Pylons/Pyramid.
- deleted 16y ago[deleted]
- okaramian 16y agoMy company is currently getting folded into a dev shop with... sub par developers/management that follows pretty much every paragraph you've written (except the F# thing, but I have similar newer code that would weird managers out to some degree). It's depressing, the framework is great but it's like there are external forces that cause the framework to be used poorly. I feel like .NET is solid for smaller shops, but once you get bigger those shops seem to want to fold weaker devs in and that tends to put up a lot of barriers/management.
- ronnier 16y agoStackoverflow is built in ASP.NET MVC, which is magnitudes better than normal ASP.NET (and ships with Visual Studio 2010).
- Encosia 16y agoASP.NET MVC and ASP.NET WebForms are both built on the same ASP.NET platform. You can even use some of the simple WebForms controls, like the Repeater and Menu, in ASP.NET MVC views.
- Encosia 16y agoJust to be clear, I would never use server controls like the Menu in my ASP.NET MVC projects. I just mentioned it to help illustrate how closely related the two really are.
- lhnn 16y ago"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.
- jister 16y ago>> In corporate dev you get promoted for doing everything to the letter not something new and exciting. I've seen pages with more than 100 checkboxes on them and arranged in a grid, it was like someone when mental with excel putting a checkbox in every cell. That is because organizations have their own set of company rules/policies that you have to follow to the letter. Mess one up and you end up being scolded or worst, fired. People that don't have enterprise experience often say things like development should be "fun" and "exciting" without considering that working in an enterprise means that you have to develop "Business Applications" not web 2.0 stuff. This means less graphics, more business rules to follow and tons of reports to generate. At the end of the day what matters is that the accounting department or HR people used the system correctly based on standard policies of the company.