C#

No, it's not great. In fact, it's not even very good. There are many things that cannot be done easily. It is bound to one vendor who can change the standard on a whim and sue any alternative vendors. It is clearly intended for ENTERPRISE program and makes inefficient use of it's keywords. Much of it's power comes from doing things that are considered harmful. It's standard library has almost nothing in common with other libraries.

Still, it is mostly simple to write and very simple to read. It is a lot of what Seeples should have been. It knows it's place and stays there. It does not puke and bleed out on the simplest of errors. Where did Bjarn go wrong? Was it the megalomania and feature creep? Was it too much focus on compatibility with C?

http://www.youtube.com/watch?v=hMNSVMyxzxA

>>1
CAN SOMEONE TELL AN OLD MAN WHAT'S LOST THE SIGHT OF HIS EYES WHERE NOW MIGHT BEEE?

http://www.youtube.com/watch?v=_Pm5r0KJops
dumb blond bimbo, the car warned her with the growling

to the bimbo - not every creature is a black guy, they're all not going to worship you because you have blond hair you're white

http://www.youtube.com/watch?v=jIoOJKLHeY0#t=55

C++ just grew around C as it's designers hacked away without higher planning. All it's derivatives had time to look at it's failings and correct them.

>>1
C# is a flavor of Java. You're saying Java is simple to write and very simple to read? Go fuck yourself, troll.

>>7
C# is not a flavour of Java any more than Java is a flavour of C++.

>>7
Java is a beautiful language.

>>8
That's bullshit because Java and C# both have forced GC and Sepples doesn't.
The object model of Java and C# is the same. Their syntaxes are same. Their performance is usually the same. Their warts are the same. C# was a Java ripoff from the start and is only superficially different.

>>10

Their warts are the same. C# was a Java ripoff from the start and is only superficially different.

That's what I thought at first. But C# has better interop (esp. with C++), better cross-platform integration, vastly superior VM, its platform has better hosted languages and it doesn't have a pathological GC that OOMs itself or takes multiple seconds to complete in most cases. PS: LINQ.

>>11

knowing about all this shit

>>12
Who the fuck are you quoting, retard?

>>12
Half of it is obvious if you ever end up using software written in the two languages. The other half comes from caring about programming languages and paying attention to things like F# and Scala. They have good ideas, M# will have good ideas in it too (confirmed because MS applied for patents on them.)

The real problem with C# is nobody has any idea how litigious MS is going to be about it down the road. Somehow uncertainty is worse than the worst case scenario because Oracle went all the way with the lawyering over Java, yet people still think Java is the legally safe bet. Bayes vs. the devil you know, I guess.

>>14
No, I don't pay attention to shit that is shit from conception.

>>15
No wonder you can't take care of yourself.

>>16
What are you talking about?

>>11

vastly superior VM

How?

>>15
You're too ignorant to make that evaluation.

>>18
The Common Language Runtime was designed to support multiple languages. The Java Virtual Machine was designed to be marketable to universities, and only incidentally execute Java bytecode. Most of the differences are little things like whether or not you can do TCO reasonably. (You can trampoline on the JVM, but you still end up making food for the GC. A few JVM functional languages do without TCO as a result.)

>>19
Fuck off you corporate retard. You niggers still haven't come up with anything that beats c or lisp and you're too normal for haskell, fuckin nigger.

>>20
C is fucking dead. Lisp is on the JVM and the CLR. Haskell is too mainstream for me.

[spoiler]But you're right, I do have a big dick.[spoiler]

>>21
retard

I think Haskell is the best choice for apping nowadays.

I think C++ is the best choice for crapping nowadays.