71–80 of 110 posts
Earlier quoted context omitted.
Hmm, a few visitors and Ryan's blog has crashed. What non-Microsoft tools & hosting do you think he used?
It's hosted with Wordpress on Linode so you are correctly spotting a huge dose of irony.
http://wordpress.org/plugins/w3-total-cache/
The simplest thing in the world.
Earlier quoted context omitted.
I'm with you. I think it's funny how people put down a technology (ASP.NET) that was released in January of 2002 because it's not up to snuff with 2013 web development tools. I also made the switch to ASP.NET MVC and can't imagine ever going back to ASP.NET. The unbelievable clean HTML you get, full control over rendering and rapid development is just phenomenal. Most of the anti-Microsoft comments I see on HN are of…
Sorry signed up to say this - been lurking a while but this one infuriated me terribly. The only reason ASP.Net MVC looks good is because you were a WebForms user before. If you've come from other tech, it's still a stinking pile of crap. 1. The API is totally broken and consists of tonnes of barely testable wrappers (HttpResponseWrapper etc). 2. The attribute model is a pain in the arse. How do you test filters base…
As for 1, I haven't really had to write tests around these wrappers yet.
I can't really comment on 2 as we don't use but a couple of pretty simple ones that ARE easily testable.
I'm also really not sure what you mean with 3. If by "hint" you mean use @ as your denotation for C# code, then yeah, I guess you do. I also don't see how it's much different from Rails templates, and in fact I think the syntax is far more readable than rails templates (disclosure: I've not used Rails extensively or professionally) and a marked improvement over JSP/ASP Classic.
4. We've got >20k users who access the site multiple times a day and we've not seen anything indicating thread corruption. Not saying you're wrong, but I'm really not entirely sure what you're talking about, perhaps you could elaborate?
5. I can't really comment on this one either, but I can say for a fact that we currently have users downloading excel files over SSL in IE8 and greater.
Earlier quoted context omitted.
Sorry signed up to say this - been lurking a while but this one infuriated me terribly. The only reason ASP.Net MVC looks good is because you were a WebForms user before. If you've come from other tech, it's still a stinking pile of crap. 1. The API is totally broken and consists of tonnes of barely testable wrappers (HttpResponseWrapper etc). 2. The attribute model is a pain in the arse. How do you test filters base…
What extensions are you using with Visual Studio? Found vanilla to be really stable, but certain extensions result in some random crashes. But not terribly often.
We have 34 projects loaded in the solution so it hits VS's limited 32-bit process restrictions pretty quickly causing the debugger to break miserably. When this fails it's a restart job.
One of the first tasks the new CEO will have when Ballmer leaves is the job of convincing Enterprise customers that Microsoft is still here to fill their needs. That said, the conclusions the author came to may very well be true for classic "Web Forms" projects, and though he noted MVC... i don't feel like he gave it the proper time it deserves. In fact, I find almost the opposite of his sentiments to be true. MVC is…
One of the first tasks the new CEO will have when Ballmer leaves is the job of convincing Enterprise customers that Microsoft is still here to fill their needs I don't think that Enterprise customers are the problem- they already use MS all the time. It's the small to medium size companies that aren't using it - and as they become larger companies it will become a problem for MS.
EDIT: Was finally able to get the page to load... I see the author alluded to this: "Yes, BizSpark is a great program for giving free Microsoft stuff to startups. It’s like a drug dealer giving free samples to get you hooked on their expensive and now compulsory wares."
One of the first tasks the new CEO will have when Ballmer leaves is the job of convincing Enterprise customers that Microsoft is still here to fill their needs. That said, the conclusions the author came to may very well be true for classic "Web Forms" projects, and though he noted MVC... i don't feel like he gave it the proper time it deserves. In fact, I find almost the opposite of his sentiments to be true. MVC is…
I moved to C# from Java back in 2001 for the RAD projects I had (still using C++ a lot when necessary though.) C# was a great language and it was faster than Java back then. But for the last couple of years all my RAD projects are now in JavaScript and it wouldn't go back. JavaScript frees me up, where as with C# I feel like I am in a straightjacket where I am forced to write a lot of boilerplate code just to do some…
It's the right tool for the right job. C# is second to none for server side work and JavaScript is great for the client side stuff. Node makes it interesting but i'd imagine the [server side] debugging support is a while from being at the level C# offers.
Tried reading this but the site was down... ironically. I've been developing the .NET stack for 10 years now and would have to say straight ASP.NET is the easiest way to add the most horrible amount of bloat to your pages and bring about horrible performance. My gut feel is that it was made to allow application developers to build intranet sites without having to worry about the stateless nature of HTTP. The result w…
I'm with you. I think it's funny how people put down a technology (ASP.NET) that was released in January of 2002 because it's not up to snuff with 2013 web development tools. I also made the switch to ASP.NET MVC and can't imagine ever going back to ASP.NET. The unbelievable clean HTML you get, full control over rendering and rapid development is just phenomenal. Most of the anti-Microsoft comments I see on HN are of…
Earlier quoted context omitted.
Sorry signed up to say this - been lurking a while but this one infuriated me terribly. The only reason ASP.Net MVC looks good is because you were a WebForms user before. If you've come from other tech, it's still a stinking pile of crap. 1. The API is totally broken and consists of tonnes of barely testable wrappers (HttpResponseWrapper etc). 2. The attribute model is a pain in the arse. How do you test filters base…
I much prefer working in .NET MVC4 than I did trying the same pattern in Java with JSP/Servlet/Spring. Things seem to just work. As for 1, I haven't really had to write tests around these wrappers yet. I can't really comment on 2 as we don't use but a couple of pretty simple ones that ARE easily testable. I'm also really not sure what you mean with 3. If by "hint" you mean use @ as your denotation for C# code, then y…
I've ben going back and forth between Java and C# in the not-so-distant past and I felt that C# ecosystem is just too limited.
Earlier quoted context omitted.
I'm with you. I think it's funny how people put down a technology (ASP.NET) that was released in January of 2002 because it's not up to snuff with 2013 web development tools. I also made the switch to ASP.NET MVC and can't imagine ever going back to ASP.NET. The unbelievable clean HTML you get, full control over rendering and rapid development is just phenomenal. Most of the anti-Microsoft comments I see on HN are of…
Sorry signed up to say this - been lurking a while but this one infuriated me terribly. The only reason ASP.Net MVC looks good is because you were a WebForms user before. If you've come from other tech, it's still a stinking pile of crap. 1. The API is totally broken and consists of tonnes of barely testable wrappers (HttpResponseWrapper etc). 2. The attribute model is a pain in the arse. How do you test filters base…
I'm not a fan a Razor either. It's code-centric instead of html-centric. Again, use an alternative view engine like Spark. I think a better recommendation is DON'T PUT LOGIC INTO YOUR VIEWS. You will rarely run into issues if you follow that.
Any issues I've found I have also found fixes for relatively easily. If you run into something that is a framework bug that you can't fix, call up MS and they will issue you a patch that fixes the problem you're having. MS has great support, so don't be afraid to use it.
Strange post, now when ASP.NET looks better than ever: MVC, WebAPI, ServiceStack, Nancy and all other micro frameworks, SignalR, OWIN/Katana middleware, whole SPA story, decent ORM (EF v5/6), small ORMs like Massive, Dapper, SimpleData ... Which means that author really doesn't know whats going on in .net web ecosystem, works in big old company that still uses Cobol, or has just have a head stuck in the sand. Sure, b…
Companies on the Microsoft stack tend to be extremely conservative. I hardly ever see anyone using these ORMs - I see LINQ-to-SQL or EF, or just as often, inline SQL using DataSets in codebehinds.
I don't think that companies should immediately jump on the next great technology, however there are plenty of companies sitting around on WebForms based on .NET 2.0 (2005) and .NET 3.5 (2007), and a few still on .NET 1.1 (2003). The only reason these companies have not moved onto ASP.NET MVC (or anything else) is because of the sheer cost of doing so. With that comes all of the negatives discussed in the post.