• 0 Posts
  • 242 Comments
Joined 3 years ago
cake
Cake day: June 22nd, 2023

help-circle






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






  • There are two types of languages:

    • Ones people complain about
    • Ones that don’t get used

    JavaScript, especially when using TypeScript, is quite frankly one of the most pleasant development experiences. Yes, there are still footguns here and there due to poor early choices and maintaining decades of backwards compatibility (===, etc), but literally all of them are caught by basic linting.

    Go try using Salesforce’s bastardized version of old Java (Apex) if you want to experience a truly unpleasant language.



  • If you’re a user who grows up using one, and then starts following instructions on how to build one, when are you going to come across the word program?

    It will be app, maybe application, saas software, functions a service, compute as a service etc etc. Hell what most people think of as an “app” is really a collection of applications all working together.



  • It’s probably predominantly because of the switch to mobile computing / smartphones / web being dominant, and everyone referring to programs there as “apps” / applications.

    i.e. If you write a mobile app with a function-as-a-service backend, you will never compile what someone would refer to as a “program”, so calling yourself a “programmer” (as-in, someone who makes programs) feels inaccurate and a not helpful description for people. “Coder” (as-in, someone who writes code) is a vaguer in terms of the type of code you write and more accurate in terms of what you spend your time producing.




  • Downvoted for sane-washing meta glasses.

    Down voted for wash-washing any point being made.

    You can’t just declare something washing and therefore bankruptcy, you have to explain your reasoning why.

    I also disagree with your other takes, mainly boiling down to the insinuation that competence and intelligence is how capitalists make money in a system that’s rigged in their favor…

    Yes but we’re not discussing a binary system of capitalist and “not-capitalists” we’re discussing a single company. And while they have not outcompeted their rivals on the basis of serving the best product for their users, or making the world better, they have outcompeted their rivals at the actually game they’re all playing (i.e. making money), all in the face of others who are playing equally soullessly.