Which programming language you like the most and why?

[Nemanja Trifunovic]

Nagy Vilmos wrote:

Multiple inheritance opens such a large bag of pain

Not at all.

utf8-cpp

[OriginalGriff]

I agree - which is why I see it's use and even necessity for Linq. But other than that, it is a sign of laziness, and of "I don't care what this is and I can't be bothered to work it out". Given Intellisense is pretty good, most of the time I have to type no more characters to get the actual type I am going to use than to get var. So which is easier to maintain? Strongly (but anonymously) typed variables, or the actual class name?

Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Manfred R. Bihy: "Looks as if OP is learning resistant."

[Rob Grainger]

I see both points of view, but

SqlCommand command = new SqlCommand();

Seems a bit redundant. I prefer "var" there (especially for generic types). Most other times I use the type - it helps keep code readable. Maybe you should be arguing for coding standards where you work that codify these things (always a shame you need to tell people). Better still, stop employing sloppy programmers.

[Rob Grainger]

Nagy Vilmos wrote:

Multiple inheritance opens such a large bag of pain

I call you out there - C++'s implementation offers a whole bag of pain, but try it in SELF and you'll see that its an incredibly powerful technique. The main problem is that in statically typed languages, inheritance is often confused with typing. Dynamically typed languages don't have this problem, so you can freely mixin behaviour. I'd like to see a type-safe language with something more like duck-typing - allowing non-related classes to be polymorphic if they have the same interface (not a Java/COM-style interface, but real interface). i.e. two objects are polymorphic on the set of common methods they have, regardless of their relationship through inheritance. C#'s extension methods attempt to fill the same gap - adding features to existing classes (and interfaces), but do so only by compromising OO - these are all static methods, can't be overridden, etc.

[Rob Grainger]

Really, I've always thought SQL was a hardship we have to endure. To whit... 1. Dates. WTF?!!?? No real standard support for dates. 2. Joins. WTF is that fugly syntax. 3. Aggregattion and grouping. WTF. 4. Use of DISTINCT (it should be implicit in every query) There's plenty more, but it always struck me as a butt-ugly language, poorly designed for the task in hand. I mean honestly, a language for accessing relational databases that fails to be even relational: SQL Criticism[^]

[BobJanova]

Of the conventional languages, C# is excellent. One thing which is missing (related to the multiple inheritance thing) is a way of specifying that you implement an interface through a member field; this would simplify the provider based approach to multiple inheritance workarounds significantly. For example let's say we want to 'inherit'

class A {
void DoAStuff() {}
void DoStuff(int i) {}
}

class B {
int BStuff { get; set; }
void DoStuff(int i) {}
}

class C: A, B { ... }

This exposes a common problem in multiple inheritance, a 'common' method (what is C.DoStuff)? At the moment you can have interfaces IA and IB and have C implement both through member fields:

interface IA { void DoAStuff(); void DoStuff(int i); }
interface IB { int BStuff { get; set; } void DoStuff(int i); }

class A : IA {
void DoAStuff() {}
void DoStuff(int i) {}
}

class B : IB {
int BStuff { get; set; }
void DoStuff(int i) {}
}

class C: IA, IB {
A a; B b;

void IA.DoAStuff() { a.DoAStuff(); }
// ... etc
}

What I want is

class C: IA, IB {
A a implements IA = new A();
B b implements IB = new B();
}

Also, I want array operations, particularly arithmetic. Writing

for(int i = 0; i < a.length; i++) c[i] = (2 * a[i]) + b[i];

... is tedious and obfuscating. I should be able to write

c = (2 * a) + b;

Given a free choice, a modern APL like Dyalog's offering is still the best for getting complex problems solved quickly. APL has made significant strides towards the 'normal' world in the last 10-15 years and you can now write readable structured code, use OO and talk to external components in a sensible fashion, but it still has all that crazy power if you need it. Something like R would also be good if I knew it as well as I do APL, probably.

[RogelioP EX DE HL]

nikunjbhatt84 wrote:

Which programming language you like the most and why? What feature(s) you love the most?

BASIC, because it allows me to Briskly Achieve Solutions Impossible in C For the meaty part of my "developer" life it has been usually the defined in IEC_61131-3 [^] - these are the ones I actually got paid to do. Been a while. For fun personal stuff C++ is somewhere in there. And Pascal... Logo... Forth... :-\ -- RP

[Super Lloyd]

now, what is it about bacon!?

A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.

[Michael Haines]

My favorite is the one that keeps me gainfully employed. I am currently working several projects at a time and working in C#, VB, Java, Groovy, Javascript, XUL, and a proprietary templating language for UIs. I finish lines of VB with semi-colons and forget the ()s on If statements in Java/Groovy/Javascript. If someone knows how to setup eclipse and VS to catch these mistakes, that would be a feature I'd like to have. You are here - through no fault of mine!

[RugbyLeague]

I agree. But haters gonna hate :)

[PIEBALDconsult]

To know her is to love her. I guess you don't know her like I do.

Rob Grainger wrote:

Joins. WTF is that fugly syntax.

Perhaps you're using Oracle?

Rob Grainger wrote:

DISTINCT (it should be implicit in every query)

Heck no. I very rarely use DISTINCT; I did the other day, first time in years, I was being lazy. About the worst thing I can say about SQL is that BETWEEN shouldn't be inclusive.

[jocstar]

68K Assembler, Snasm and an Amiga!! An elegant weapon from a more civilized age.

[VEMS]

C++

[BubingaMan]

Beyond a doubt, my favorite (GUI) language is XAML. MVVM in combination with MVC patterns results in the most elegant LOB applications I have ever seen. I absolutely love it. XAML + C# is by far my favorite combo. As for specific implementation of XAML based technology, I have a preference for WPF. Silverlight has some nice features as well, but overall SL has been a pain in the ass for me.

[User 4085378]

I vote for VB for several reasons. I say this, having designed 2 fully operational procedural languages. Professor E. J. Yannakoudaks eyan@aueb.gr

[Old Ed]

Assembler, without a doubt. I like it because it's pristine. Every instruction does exactly what you expect it to do. As for features, it's the lack of features that make Assembler great to work with.

[danmcleran]

Python is my fun girlfriend. C++ is my dependable wife.

[Alexander DiMauro]

Rob Grainger wrote:

Seems a bit redundant. I prefer "var" there (especially for generic types).

Exactly. I agree. Especially when you are handed code like this:

SomeClassWithACrazyLongNameThatGoesOnAndOnAnd bacon = new SomeClassWithACrazyLongNameThatGoesOnAndOnAnd();

The one that makes me laugh (while pulling my hair out) the most is when I see:

var bacon = 3;

Now THAT is not even laziness, just silly...except for the bacon.

The world is going to laugh at you anyway, might as well crack the 1st joke! Have you tried turning it off and on again? Have you tried forcing an unexpected reboot?

[BrainiacV]

FORTH is the one true language...at least for anything requiring real time controls. It allows you to freely intermix high level and low level code as you create a new language to match your task. Your commands can become active during compilation and can start reading your source code to perform functions not built into the compiler. It supported the rudiments of object orientation, long before the terms and methodologies were created. FORTH code is smaller than machine code and operates at 80% of compiled C code. Being stack based, unit testing is a snap. No need to create scaffolds for testing. Just load up the stack and execute it. Each command (verb) can be compiled in immediate mode and immediately tested. In team environments, after we define our points of contact, we generally just zipper our code together and it all works. I became a true believer after we slapped together in just six weeks a project I estimated to take nine months (and I'm good at estimating). We literally slung code at a wall and it all stuck. Later projects let me write code that wrote itself by expanding the compiler dynamically. It was fast too, I'd compile 300K programs in 30 seconds while C compilers at the time would take hours. It is interactive, you can add commands while the program is running (particularly after you have added multi-tasking to the language instead of the OS), so you are not stuck in the Edit-Compile-Run-Debug-Repeat cycle. That said, I still prefer to let the task select the language. If I am going to be parsing strings, my first choice is BASIC, and I don't mean that perversion called VB.NET. But today my language of choice is C#.NET because it is less verbose than VB.NET. Mostly because it is a commercial decision and there is no Object Oriented FORTH (of merit) until I guess I write it.

Psychosis at 10 Film at 11 Those who do not remember the past, are doomed to repeat it. Those who do not remember the past, cannot build upon it.

[Masterdesign]

Hello, deciding which programming language is most likely one depends upon the ease of use less complicated still productive and the variety of udate feature If that is the case than i think C# is the only option. Thanks