What a veteran gives you, what a young language doesn’t have… those darn CA certificates (Java vs…

What a veteran gives you, what a young language doesn’t have… those darn CA certificates (Java vs Elixir)

What a veteran gives you, what a young language doesn’t have… those darn CA certificates (Java vs Elixir) 5 TLS iterations. cacerts: :undefined → verify_none → cacertfile → max_path_length_reached → verify_none again.

All to send an email from Elixir.

In Java: add the dependency, copy 30 lines of code, and it works. The JDK ships its own CA root certificate store ($JAVA_HOME/lib/security/cacerts). STARTTLS with Gmail works out of the box. Zero extra configuration. —

Don’t get me wrong — Elixir isn’t bad for this. Swoosh has a beautiful API, the functional pipeline is 3× more concise than Jakarta Mail, and the dev adapter (emails in memory, never sent) is a dream.

But there’s something a 25+ year old ecosystem gives you that a younger one simply doesn’t have: someone already thought about the edge cases and solved them for you.

In Java, SSL certificates are part of the JDK. You don’t think about them. They’re just there.

In Erlang, you depend on the operating system, your distro’s CA bundle, whether Erlang respects the environment variable, whether the path length validation is compatible… and you end up sacrificing peer verification in development just to move forward.

Enterprise maturity in Java isn’t just bureaucracy and boilerplate. It’s reliability. It’s things working without you having to become a TLS expert.

Elixir, I love you as a language. But this round goes to Java.

And it’s okay to say it.

Please visit for more in depth clarification: https://lnkd.in/d55d4Wbw

Use your browser’s built-in translator to read in your preferred language.

📢#Java #Elixir #PhoenixFramework #SoftwareDevelopment #TechComparison #SSL #TLSCertificates #EnterpriseJava #Elixir

Originally published at https://www.linkedin.com.