C#

What do you think about C# ?

Its just java with Microsoft branding, do not want.

It's pretty much a java clone except MS based, I don't care about it.

Yet another Microsoft branded Java-a-like, no thanks.

>>2-4
This, although if I was forced (under gunpoint, threat of castration, etc) to only use either C# or Java, I'd pick C#

>>5
This, except I'd also choose it over a wide variety of other languages commonly use in the enterprise world, like COBOL, Visual Basic, C++... It's probably the best language in widespread use in the non-technical sectors.

Super same person thread

>>7
Perhaps the same could be said of /prog/'s entire fucking first page. Seriously, someone needs to chill.

J# is MS Java, and its been depricated because Java is shit and the .Net runtime can already execute Java Bytecode.

The same cannot be said of the JVM.

C# = Java with some of the mistakes fixed, creeping up sideways on becoming something more like ECMAScript.  Still doesn't do mix-ins, a lack that is a recurrent pain in the ass to work around; but I'm happier to use it rather than Java in the day-job.

C♯ = D♭

>>11
Not alwyas

>>11
How do you that backwards d?

>>13
8/10

>>14
What? I give it 0.5 at best.

Aynway, I don't mind C♯ itself (it's not Java, at least), it's the non-standard things like System.Windows.Forms (that Microsoft put in the system namespace even though it should be Microsoft.Windows.Forms) that suck.

C♯ itself is portable, as is the rest of the CLR. Much of the rest of .NET, such as WinForms, is Windows-specific. The fact that Mono have vaguely implemented it on other platforms is entirely incidental. And also ｃｏｎｓｉｄｅｒｅｄ ｈａｒｍｆｕｌ by some.

Also, the language has kind of outgrown the framework. The framework and language started out on equal terms, but then C# added nullable types, generics, extension methods, lambda expressions, LINQ, and partial methods. Some parts of the framework use these (newer parts) but it's still bad.

"Multiplatform" means that it runs on multiple versions of Windows.

>>15
Are nullable types any good?
I don't see how they are useful for things other than catching errors in a database.

Partial Methods in C# (draft)

PARTIAL METHODS MEME FAN
Masachuchu Technorogy Insitute

                                                                                                                 

Abstract

I can hardly keep tears from raining down my already
mascara-stained face while reading the explanation of
the motivation behind the introduction of Partial
Methods into the C# language.

                                                                                                                 

1 New spaggetizing capabilities

It is possible to split the definition of a class or a struct,
an interface or a method over two or more source files. Each
source file contains a section of the type or method
definition, and all parts are combined when the application
is compiled.[1]

Seems like I cannot avoid quoting Steve Yegge:

Large Systems Suck.  This rule is 100% transitive.  If you
build one, you suck.[2]

2 Lack of RCS

Please also observe this emerald:

When working on large projects, spreading a class over
separate files enables multiple programmers to work
on it at the same time.

Surely Microsoft never discovered an RCS without per-file
locks, and its whole philosophy forbids it from implementing
or adopting a distributed one, like Git.

3 Unquestionable VS codegenerator

When working with automatically generated source, code can
be added to the class without having to recreate the source
file. Visual Studio uses this approach when it creates
Windows Forms, Web service wrapper code, and so on. You can
create code that uses these classes without having to modify
the file created by Visual Studio.

Nothing screams more about unmaintainability of VS-generated
code than that.  There is little possibility to reason about
such programs.  Of course, this approach is vastly inferior
to more enlightened technologies of development, like the one
that was taught in MIT until recently.

4 Conclusions

We have proven in this paper that C# gets more and more
shitty with time.  % Insert punchline here -- PMMF

                                                                                                                 

References:

[1] http://msdn.microsoft.com/en-us/library/wa80x488.aspx
[2] Steve Yegge, Rich Programmer Food.
    http://steve-yegge.blogspot.com/2007/06/rich-programmer-food.html

Partial methods can be useful for implementing lightweight event handlers that optimise out to nothing when the event handler isn't actually implemented.

I've never actually used it for that, though, and I don't know anyone who has.

>>16
c# runs on windows?

>>20
it does and is thus a joke amongst languages

>>19
I sincerely think this is the best post in /prog/ ever.

They somehow made Java even worse.

>>18
I sincerely think this is the best post in /prog/ ever.

How do you pronounce ``cocktothorpe''?

>>21
i thought windows programmers were still stuck with 1980s languages like sepples an java.

Reason and persuading The Computer to terminate  them before they  do the same  cannot be said  of the JVM  is always shit  Blatantly false No?