The worst programming language of all time
youtu.be
A little video about C++.0:00 Introduction1:39 Casting in C++.2:47 Keywords5:31 Types7:02 Different Ways to Do the Same Thing7:20 const8:20 Formatting and St...

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

  • Skullgrid@lemmy.world
    31·
    19 hours ago

    … 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

    1. 1 ↩︎

    • masterspace@lemmy.caEnglish
      22·
      18 hours ago

      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#.

      • Skullgrid@lemmy.world
        41·
        18 hours ago

        Apex doesn’t have namespaces.

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

        • masterspace@lemmy.caEnglish
          11·
          9 hours 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.