Norscode or JavaScript?

JavaScript is everywhere: in every browser, on the server via Node, and in countless tools. Can a young Norwegian language compete? In some areas no, in others that is exactly the point.

Where JavaScript is unbeatable

JavaScript is the language the browser speaks — if you want something to happen on a web page, there is no way around it. With Node it also runs on the server, and npm is the world's largest package registry. The community is enormous: you find developers, courses and answers everywhere. For frontend, and for teams that already live in this ecosystem, JavaScript is the obvious choice.

Where Norscode chooses differently

Norwegian, not English. funksjon and hvis instead of function and if — readable for Norwegian speakers without translation.

Fewer moving parts. A JavaScript project often drags along hundreds of npm packages you have not read. Norscode delivers web, database and cryptography in the standard library and links everything into a single file with a single checksum — less to trust, less that can go wrong.

Safety by default. Node has traditionally given a program full access (newer versions have begun with a tentative permission system). In Norscode, capabilities are the core: the program gets nothing it has not been given.

Simpler flow for simple things. Much of JavaScript is asynchronous with callbacks and promises, even when the task is trivial. Norscode reads straight ahead, the way you write it.

What should you choose?

If you are making something that runs in the browser, or you need the npm ecosystem and a large community — choose JavaScript. If you want Norwegian syntax, few dependencies and built-in security on the server side — Norscode is a genuine alternative.

The browser is JavaScript's home turf

There is one thing JavaScript can do that no one else can: run in the browser. If something is to happen on a web page — a button that responds, content that updates without reloading the page — there is no way around it. There Norscode is not an alternative at all, and it does not pretend to be.

On the server the picture is different

With Node, JavaScript also runs on the server, and this is where the two meet. Node has an enormous ecosystem in npm and a large community — but also a tradition of many small dependencies and a lot of asynchronous code, even for simple tasks. Norscode goes the opposite way: a broad standard library so you avoid the package hunt, code that reads straight ahead, and a runtime that gives the program only the access you specify.

What should you choose?

For frontend the answer is simple: JavaScript. For a server-side service where you want few dependencies, built-in security and Norwegian syntax, Norscode is a genuine alternative. Many teams end up with both — JavaScript where it has to be, and something calmer and safer on the back end.

Back to the overview