Jake Birchall - 4 years ago
As a new developer to Apex, I assumed switch cases were existing as they are in every other language only to get stuck on a obscure compiler error which was a result of me trying to use a switch.
I was very disapointed to find switch wasnt a thing, and even more so to see this has been a promised feature for 9 years now.
Deb Hale - 4 years ago
As an IT Manager for a small/medium sized company I have way more things to do than develop work arounds for an application/system that I am paying hundreds of dollars a year for. I want to pay for an application that works, has support that can actually understand what my issue is and help to resolve it ( I also pay for Premier Support) and that works in MY time zone. (US Central). I still say that Salesforce needs to listen to what the CUSTOMERS are asking for. I for one am one of those customers "that is stuck in the past". My needs are very simple and I am deeply offended by the article. Maybe it really is time to look for a new solution.
Bill Hanson - 4 years ago
I'm starting to get worried about the direction SFDC is taking. We don't use Lightning at all, but have 1000's of hours in custom development of classic features (APEX, VisualForce). I see lots of development on new features, but not much in the classic environment. Please stop creating shiny new features for the next Dreamforce and focus on improving what we already have. Pretty please? It feels like you are catering to your stockholders rather than your users.
Rick Nendza - 4 years ago
Okay. with Full credit to Adam :)
switch (PM Update);
alert("omg we have caught up to COBOL ");
communicateSolution('work-around is to code 20 if statements');
Tobias Aichele - 4 years ago
I think they just need to reimplement the whole compiler from GCC to LLVM. :) Maybe because it's Java in the background it sucks more than on any other language.
Ok, I respect the APEX language. It's ok to use and the forced tests are also good. But no switch... case... sucks really. :(