c#, java or python

[VectraMan]

not to mention I haven't heard anyone say VS2010 is "messed up" based on reviews I read.

Well you heard me say it. It's S L O W, and it has some weird issues, like the find dialog being twice as wide as the screen. What I'd like is the VS2010 C++0x compatible compiler, the VS2010 intellisene but in the VS2005/2008 IDE which doesn't have these issues. Rewriting the IDE has acheived nothing but slowness, even though other aspects of VS2010 are pretty good.

[doodab]

Python is a thing of beauty and a joy forever.

I bet you like perl as well

[d000hg]

Well you heard me say it. It's S L O W, and it has some weird issues.

There is not one single piece of software that doesn't have weird issues on at least one PC. I don't think WPF in general is slow, although I would agree that it doesn't seem entirely necessary on VS... do we know what Office is developed with these days? It's obviously in MS' interest to use their own technologies to show them off, I suppose that's enough of a reason to them.

[Scrag Meister]

Be a real man and learn assembler?

Did that when I was 14/15, its a bit passee.

Edit , Yes I know it maybe useful for electronics type project, but I'm not into that.

[fullyautomatix]

MS come out with some new fangled paradigm in every .NET version. They made a big fuss out of WPF, WCF and WWF and suddenly all the job adverts wanted folks with WCF experience. I am not surprised WPF is dead but it definitely had its advantages.

[thunderlizard]

Python is a thing of beauty and a joy forever.

Python does have its adherents (do they still all meet up in the Old Bank of England every month??), but I'm not one of them. Any language where indentation has syntactic force is taking the mickey. I think that most people would agree that going into Python as a career would have to be for aesthetic rather than commercial reasons.

Java is good if you like everything to be free and open source, and enjoy sifting through 100 libraries that do almost-but-crucially-not-quite the same thing.

C# is good if you prefer just 1 library and don't mind spending a grand or so on upgrading every couple of years to find out what sloppy feature they've added to the language this time. (we've had implicit typing, and now dynamic typing. It's only a matter of time before they decide declaring variables at all is for uptight squares, dude).

[doodab]

Java is good if you like everything to be free and open source, and enjoy sifting through 100 libraries that do almost-but-crucially-not-quite what you need

FTFY

[d000hg]

Java is good if you like everything to be free and open source, and enjoy sifting through 100 libraries that do almost-but-crucially-not-quite the same thing.

Not really. Java has a huge set of standard libraries roughly comparable with .NET, plus standards for all the extended stuff in J2EE. But then on top of that you've all the open-source stuff... however every language has this, Java just more so. The Apache libraries and a few others are practically standard though, it's the random OS projects you find that are not great because they aren't mature.

C# is good if you prefer just 1 library and don't mind spending a grand or so on upgrading every couple of years to find out what sloppy feature they've added to the language this time. (we've had implicit typing, and now dynamic typing. It's only a matter of time before they decide declaring variables at all is for uptight squares, dude).

Again, there are open libraries for .NET. And you don't have to upgrade .NET versions, nothing wrong with 2.0 or 3.0. And they haven't changed variable typing, they've let you use BOTH styles. And you don't have to buy the expensive version, the Express one is sufficient of the majority of projects.

[d000hg]

MS come out with some new fangled paradigm in every .NET version. They made a big fuss out of WPF, WCF and WWF and suddenly all the job adverts wanted folks with WCF experience. I am not surprised WPF is dead but it definitely had its advantages.

WCF is still a big thing, mainly because there's not much alternative - they're trying hard to kill COM and I think they're winning (phew), and Remote Objects are dead too... WCF actually seems pretty sweet although nobody seems to use WF very much outside massive integration projects.

[fullyautomatix]

WCF is still a big thing, mainly because there's not much alternative - they're trying hard to kill COM and I think they're winning (phew), and Remote Objects are dead too... WCF actually seems pretty sweet although nobody seems to use WF very much outside massive integration projects.

What about Linq to SQL and its new avatar ADO.NET entity object model ?

I cannot see WCF, WF etc lasting long.