When should you choose something other than Norscode?

We believe Norscode has something to offer. But an honest choice of language requires that we also say when you should choose something else. Here are those cases.

When the ecosystem decides

If you need a ready-made library for a specialized field — machine learning, scientific computing, or the toolkit of a particular cloud service — a mature language like Python, JavaScript or Java will usually have it on the shelf. Norscode has a broad standard library, but it cannot match decades of third-party packages. If you are not going to build the building block yourself, choose where the blocks already exist.

When you need a large community

On a large team, or when you are hiring, it matters how many people already know the language. There, established languages have a head start Norscode does not yet have. If finding people quickly is crucial, a widely used language is the safe choice.

When you need absolute metal-level performance

Norscode is compiled and statically typed, and with AOT compilation on the way its performance is approaching the fast, compiled languages with a garbage collector — more than enough for the vast majority of services. But for the very last layer, where every microsecond counts and you need manual control over memory, Rust and C are still ahead. Norscode is made for readability and safety first.

When maturity is a requirement

Norscode is under active development. For systems where you cannot tolerate anything changing, or where you need certifications and a long track record, you should choose something that has stood longer.

Why we say this

A tool that fits everything rarely fits anything well. Norscode is a good choice when you want Norwegian syntax, security by default and reproducible releases — and an honest answer about when you should not use it makes the times you should easier to trust.

Back to the overview