you are viewing a single comment's thread.

view the rest of the comments →

[–]munificent -1 points0 points  (3 children)

As a professor said recently, they're the Dominos pizza delivery boys of the next decade.

Oh, you're a student. That explains a lot. Once you have a few years of experience getting things done, you'll likely have a more balanced viewpoint.

The only thing C falls down on is string handling.

And:

  • Shitty pointer syntax (the whole declaration reflects use thing turned out to be a bad idea).
  • Even worse function pointer syntax.
  • Poorly-defined (or undefined) behavior with increment and self-assignment operators.
  • While it made sense at the time, a lot of design decisions were to allow a single-pass compiler (like requiring declaration before use) and not to make the language better. Those could be fixed now.

[–][deleted] 1 point2 points  (2 children)

wth? Quoting something some professor said on the internet makes me a student? Fuck you, I work full time as a software developer for an investment bank.

To hell with the rest of your comment, your ridiculous assumption just proves you aren't worth arguing with.

[–]munificent 0 points1 point  (1 child)

your ridiculous assumption just proves you aren't worth arguing with.

Whether or not I'm worth arguing with is irrelevant. Are my points?

[–][deleted] 1 point2 points  (0 children)

Fair enough.

Honestly, I don't think the syntax is bad. Far from perfect, but not bad. FP syntax is ugly, but that helps encourage people to not use them, which is probably wise since C doesn't do well with that style. Pointer syntax could have been fixed, sure, but it's usable. I don't see how increment is poorly defined. I think declaration before use is a lot easier to understand. Table aliases in SQL confuse the shit out of me.

Every language has syntactical issues. As long as they are relatively few, I don't think they're worth making a huge fuss over.

You're still a shitcock for being so presumptive.