3 ms·
So what's Deno's stdlib principle: 1. you got pretty much 80% of what you will need from the std libraries for a mid-size 'normal' application(similar to g
by synergy20 5y ago
So what's Deno's stdlib principle:
1. you got pretty much 80% of what you will need from the std libraries for a mid-size 'normal' application(similar to glibc, libstdcpp, go stdlib, python's stdlib)
2. you got a small stdlib than usual(rust's stdlib), the rest you use cargo and good luck with that
3. you grab whatever you need(node.js, you have no idea about the 500 modules npm just installed)
I prefer No.1 here.
- CodesInChaos 5y agoIsn't the scope of the standard library of C and C++ close to the scope of the Rust standard library (an thus much smaller than python's)?
- synergy20 5y agonope, I was told rust prefers to a light stdlib approach.
- CodesInChaos 5y agoC and C++ also have light stdlibs from my point of view, just like Rust. Rust has collections, strings and algorithms manipulating these. It supports synchronous IO (files and network) and can work with threads/processes. It lacks async IO, higher level network protocols (e.g. HTTP and TLS), regex, advanced unicode support, serialization, UUIDs, GUI, linear algebra/vectors, logging, encoding, time, randomness, command line parsing, cryptography, compression. C++ has reasonable randomness and time support, but apart from that Rust isn't far behind.
- _jplc 5y agoIt's definitely No.1.