D

What do you guys think about D?

Not Lisp.

aka shit

>>2
Besides that.

It fixed C++ just to break it again.

D is what happens when Java programmers think they're able to reinvent C++.

>>5
8/10

>>6
nah he's right

D is what happens when people don't promote Haskell hard enough.

We have C#, the true successor to C. Why do we need another language?

>>6
Which are valid?
1) Kodak-san likes Java
2) Kodak-san dislikes Java
3) Kodak-san likes D
4) Kodak-san dislikes D
5) Kodak-san likes both D and Java
6) Kodak-san dislikes both D and Java
7) Kodak-san thinks >>5-san is a mental midget who should go scrub another toilet

You may choose more than one option.

>>10
Penis envy will get you nowhere.

>>9
C# would have potential (not as a C replacement, but a higher level language that would be used instead of Java and C++) if it weren't developed by Microsoft (Mono is not a viable CLR and MS still gets to make all the decisions about the language).
However, D is not supported well enough (even Go has more packages and bindings available (and is a better language anyway)), so Java still remains as the best higher level somewhat high performance language.

>>10
7, always 7.

>>12
The real problems are:

D programmers keep circlejerking about how much better D is than C++

Go programmers keep circlejerking about how much better it is to reinvent fucking everything (hell, they even had to implement their own C compiler and linker, because we clearly don't have enough shitty compilers yet)

Java programmers keep circlejerking how platform independentness is totally the path to salvation (also jesus christ, etc)

LITHPu programmers keep circlejerking how awesome it is to never get laid and shower and to never make money and to live with your parents forever

C programmers keep circlejerking about how kernel hacking is the very definition of a hacker (and hardly get shit done, but instead rant about anythin)

PHP programmers... are hopeless

Perl programmers are busy finding new, obscure ways to turn output generated by /dev/urandom into yet another minesweeper clone

C++ programmers are busy deciphering errormessages generated by Boost, while being constantly puzzled which C++ standard is actually the "current one"

BASIC Programmers:

10 PRINT "Hello world"
20 RUN
**ERR ENOMEM


Javascript programmers are circlejerking about how awesome rotating images are, and how it is totally going to change everything we know

Ruby programmers are circlejerking about how totally funny and witty and original and hilarious and awesome programming jokes involving ruby are (print "this is not python" HAHAHAHAHAHAHAHAH its funny because it could be ruby as well! so funny! so witty! so original! hahahahaHAHAHAHAHAH ^{*cries itself to sleep*})

Python programmers are circlejerking about XKCD, as usual, being the unfunny, borderline-fascist scum they are

Haskell programmers are... well, they are fucking hipsters, what more is there to say about that? I mean, who else in their right mind would program in something as awful as Haskell if you aren't a self-absorbed man-child hipster bastard?

the only decent language is windows xp

>>12
Why is Mono not a viable CLR? It's true they usually go a step before the official MS implementation, but I don't think we'll see big C# changes in the next years, and Mono mostly implements .NET 4.0, the actual version.

And take a look at MonoTouch for iOS or Android. It compiles apps to native code using LLVM I think. So C# right now is a fine choice as a language with the base APIs. The problem is cross-platform UI APIs: Mono guys don't want to port the Windows-dependant APIs (and IMO, it's the right decision. It's better than having a cross-platform UI API like Swing for Java that looks like crap and it's slow as fuck).

>>16
MonoTouch is proprietary filth, and thus is unsuited for use.
The main problem with Mono is that it lacks conpatibilty with some .NET-based programs and libraries, which is primarily Microsoft's fault. Then again, Microsoft being in control of the language is what bothers me the most about it. If it weren't for them and their EEE, C# might have well become the leading high level language and more or less kill Java (excluding the legacy software, of course).

>>16

C# is shit
GC is shit
Mono sucks
MonoTouch sucks even more
Learn to make your own UI
If you want native code on android use a better language like C

>>18
C does not imply native code, compiling native code does not imply better.

>>19
Yeah, C is always interpreted and native code is much slower than Lisp/Java anyway.

>>19

this is what C# and java programmers believe

>>20
most lisp compilers will compile to native code

>>20
all three are languages and do not specify whether code is interpreted or compiled you nerd

>>18
Android's main language is Java.