Why I use it

Where predictability under load matters. The compiler catches at build time what surfaces in production in other languages — for services that can’t go down, that’s the deciding argument. No garbage collector also means flat latency without surprise pauses.

How long

3 of my 6 years in development. It’s been my main language for the last few years — most of what I’ve built in that time is written in it.

What I build with it

• Platform cores and high-load services
• Data processing and transformation
• Telegram bots with non-trivial logic
• Parsers where speed and resilience matter

Why I use it

A compromise between strictness and writing speed. The type system is strict enough to keep silly things out of runtime, but it’s noticeably faster to write than Rust. Good where the JVM ecosystem is what you need.

How long

About a year. I picked it up for one project and kept it — a good example of how a new language shows up in my stack: out of a task, not out of a wish to add a résumé line.

What I build with it

• JVM services
• Telegram bots
• Integrations with third-party APIs

Why I use it

The actor model on the BEAM solves a problem you otherwise assemble by hand: thousands of independent processes, supervisors, failure isolation. If part of the system crashes it restarts itself while the rest keeps running — for distributed services that saves an enormous amount of effort.

Where I use it

• Microservice architecture on a project with unusual requirements
• Services with many simultaneous connections
• Paired with Rust where both concurrency and raw speed are needed

Why I use it

The shortest path from idea to a working result. I keep it for things that need solving once, or for testing a hypothesis — rewriting that in Rust for performance usually makes no sense.

How long

About two years out of six. These days it’s a supporting language, not a primary one.

What I build with it

• Prototypes and hypothesis checks
• One-off data processing
• Scripts and some parsers