That's why everyone who works on Mono should be so excited about the .NET Core announcement. They still won't have WPF (but who wants that), and I doubt WF will be a part of it, but they'll have a lot more than they do now.

.NET places no requirements on MSSQL. Me personally, I store my data in a mix of MSSQL. Postgres, SQLite, Cassandra, Lucene (the Java version), and yes, even Firebird (and I absolutely do NOT recommend Firebird).

If you want to host ASP.NET code on Linux, there are various ways to host Mono's version, using Apache, Nginx, and other servers: http://www.mono-project.com/do...

Once .NET Core actually exists, we'll see what the hosting story looks like. I imagine it'll look a lot like Mono's.

So a no-name CEO of a tiny little startup (who doesn't know the difference between a platform and a language) doesn't hire .NET programmers, and that means .NET is dying and Java will rule the world?

Tee hee. Keep posting, I'm enjoying it.

The ".NET stack" only runs on "SQLServer"? You either have a funny definition of ".NET stack" or you're completely ignorant.

No, he was merely giving that as an example of the power one senator has. In this case, it wasn't that a cancellation bill was placed on hold, it was that the amendment sponsored by Wicker was passed, directing NASA to finish it.

6 years since release, and the nicest thing that can be said for it is that it's growing steadily.

LINQ the DSL was the big news when it was released, but in the real world, it has gotten very little traction. The Enumerable extension methods that are the plumbing behind it, however (after all, the DSL simply gets translated into calls to this stuff by the compiler), are quite common.

LINQ, or the Enumerable extension methods? Results (can be) similar, language is very different.

The enumerable extension methods plus lambdas is more similar to Java's stream API, but only an insane person would prefer Java's implementation. As for LINQ (the DSL for working with the same methods), it's FAR less common. I rarely see it in practice, and I don't generally prefer it.

Most likely a really old one. New Pythons have been coming out for a long time, but nobody uses them.

... which isn't confusing at all, right?

NETMF runs on microcontrollers, has for years. Has been Apache licensed for years.

It's not using Linq. It's using a set of extension methods and lambda expressions. Linq is a whole other DSL ("from x in myVehicles...") that I rarely see used.

Lambda expressions are simply syntactic sugar for anonymous methods.

It's distressing to me that you claim to be a C# developer and can't "wrap your head around" lambdas, which you also confuse with Linq. Hopefully you have an MSDN subscription and can take advantage of some of the new free PluralSight training, because you clearly need it. I wouldn't hire you.

AT&T doesn't work for its customers, it works for its shareholders.

Only works for .NET applications. What about native applications?

Of course they're not required to do so. That being said, some of us bank with institutions that don't hate their customers.