Advertisement

On leaving .NET

Started by September 24, 2010 09:48 AM
31 comments, last by ranakor 14 years, 4 months ago
Quote:
Original post by Alpha_ProgDes
Quote:
Original post by Mithrandir
My company has finally been convinced of the benefits of .NET, and has put me on the team that will eventually convert all of our products over to C#. To me, it's very exciting to be in .NET world. I can't ever imagine leaving it.



Now, that being said, WCF makes me a very sad panda. It was ridiculously over-engineered and I can't stand it. But other than that, pretty much everything in .NET is golden.

Interesting, I misread your post thinking you said WPF (since I hear that is the overengineered part of .NET). I've heard nothing but good things about WCF. Hmmm. Also, out of curiosity, do you think the AJAX Control Toolkit is better than jQuery? Because I've just about have had it with the ACT and am about to start exploring jQuery more thoroughly.


I heard the same thing about WPF, but after using it, I don't agree with that assessment. It's pretty elegant and I cannot see myself going back to WinForms. The ickier parts are nicely handled by tools like Expression Blend.

WCF on the other hand, is what I like to call "factory hell". It's like someone opened up Design Patterns and said "I'll need to use at least a dozen of each one of these patterns!". Sure it seems simple and elegant when you first look at the samples, but once you want to customize it to do anything remotely custom, you find yourself needing to create all sorts of custom classes for no apparent reason just to do the simplest thing. It's utterly ridiculous.



As for ACT vs jQuery, not sure they're really comparable. Sure ACT has a jscript component to it, but it was never really meant to be a comprehensive client-side library like jQuery is. 90% of what I use ACT for is the server side stuff that jQuery cannot do anyway. Not that it matters much, because ASP.NET has embraced jQuery and future versions will have it integrated in anyway. So they both have their place. One place where ACT is irreplacable is the client-side web service code generator. If you want to call a web service all you have to do is add a reference to the service to your script manager, and it generates ALL the jscript you need to call that service with one line. It's absolutely essential.
This is my signature. There are many like it, but this one is mine. My signature is my best friend. It is my life. I must master it as I must master my life. My signature, without me, is useless. Without my signature, I am useless.
Quote:
Original post by capn_midnight
(and I'm sorely feeling the "not at home" feeling of Python and Vim outside of a *NIX environment).

Vim fits in quite nicely with Windows. And if everything breaks, you can always resort to Cygwin or GnuWin32.
Advertisement
Comparing the ajax control toolkit to jQuery makes no sense , they don't overlap one bit in features unless you include jQuery UI or separate plugins.
One lets you abstract your JS over the dom difference and provide a high lever way of working with it, the second one lets you use widgets. Not alike at all.

This topic is closed to new replies.

Advertisement