this post was submitted on 18 Apr 2026
0 points (50.0% liked)
Programming
26579 readers
191 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
... 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 :
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#.
Why do you need namespaces? Apex has a singular purpose on a single platform.
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
loggerclass 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.