-6
A video arguing C++ is the worst programming language to ever exist (youtu.be)
submitted 5 months ago* by to c/programming@programming.dev
97 comments fedilink hide all child comments
 

Found this gem. A single well made video in a channel. The Channel owner probably made this channel just to house one video I guess.

I havent watched it all the way through but it seems to have alot of substance. By the looks of it the guy probably has spent atleast a year developing professionally in C++ and is pretty pissed to make that video as a ventfest

See if you cant agree with something he said

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 5 months ago* (3 children)

... I'm a polyglot^[1] . I fucking hate working on salesforce, but I prefer languages that work like Apex/Java/C++ over things that work like JS.

[1]: Let's see :

  • Javascript
  • Actionscript
  • Python
  • Bash
  • C++
  • C#
  • Java
  • Apex
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 0 points 5 months ago (2 children)

    Apex doesn't have namespaces. It doesn't even let your organize your classes into subfolders. It is an absolute F-Tier language.

    Try TypeScript, try React, try Go / Swift / Kotlin, spend more time with C#.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 5 months ago (1 child)

    Apex doesn’t have namespaces.

    Why do you need namespaces? Apex has a singular purpose on a single platform.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 0 points 5 months ago*

    If Apex had a "singular" purpose then they wouldn't have built it as a turing complete generalized programming language.

    And the reason you need namespaces is for basic code organization. Classes organize functional objects with a module of code, namespaces let you're break code into modules.

    If you have two distinct modules of code, each with their own logger class you suddenly have a confusing naming conflict with both loggers being exposed everywhere (or forced you to rename one).

    So then it forces you to try and name your classes like RenderingLogger or Service_Logger and then you very quickly run into the fact that Apex imposes arbitrary length limits on class names.

    If you're writing a simple db access script then whatever, it can get the job (worse then other languages but it can). If you're actually trying to build a proper application like you publish on AppExhange then it's shortcomings become apparent everywhere.

    Hell it didn't have a reasonable unit testing framework until a side project from some devs introduced Apex Mockery, and it still sucks compared to Mockito and actual professional testing frameworks.

  • permalink
  • fedilink
  • source
  • parent