A language with batteries included

A new project often begins the same way: you need to read a file, parse a bit of JSON, make a call over the network, maybe hash a password. In many languages that means finding, evaluating and installing a handful of third-party libraries before you've written a single line of your own logic.

The essentials come along

Norscode comes with a standard library that covers what most programs need: text processing, lists and lookups, JSON, date and time, files, cryptography, and a layer for the web. You don't download anything. It's there from the very first command.

The advantage isn't just convenience. Every external dependency is something you have to trust, keep updated and make sure isn't compromised. The more that lives in a vetted standard library, the less of that burden falls on you.

One style, not ten

When text, files and web are written by the same people with the same principles, they hang together. The error handling looks the same. The names follow the same pattern. You learn one way of doing things, and it holds throughout the whole library — instead of piecing together ten libraries that each have their own philosophy.

Enough to run a website

The website you're reading this on is written in Norscode and uses only the standard library — the web layer, the database and the markdown processing that come with it. It isn't a stunt; it's the point. The tool should be up to real work right out of the box.

"Batteries included" is an old idea. We think it's worth taking seriously again.

What "broad on purpose" means in practice

Picture a typical task: receive a web call, parse a bit of JSON, look something up in a database, and respond. In many languages that's four libraries to find, evaluate and install before you've written a line of your own logic. In Norscode all four are already there — std.web, std.json and std.db come with the runtime, and you're off right away.

Fewer dependencies, less risk

Every external package is something you have to trust, keep updated and make sure isn't compromised. The more that lives in one vetted standard library, the less of that burden falls on you. It's not just convenience — it's also fewer moving parts that can break or become a security issue.

One style throughout

Because web, files, date and cryptography are written by the same people with the same principles, they hang together. The error handling looks the same, the names follow the same pattern, and what you learn in one module you recognise in the next. You're spared piecing together ten libraries that each have their own philosophy.

Back to the overview