3 ms·
I think the big problem is that any such thing you'd design an interface for might change in such a way that it doesn't make any sense to preserve this hypothet
by tialaramex 4y ago
I think the big problem is that any such thing you'd design an interface for might change in such a way that it doesn't make any sense to preserve this hypothetical interface over time. Rust's standard library promises to keep maintaining all the pieces long after they're obsolete, and the bigger it gets the harder that will be.
In 1983 if I design a Video interface I guess we need PAL vs NTSC to handle colour standards, and also we need Interlacing, that's a thing. Should we have a fixed list of resolutions? Nah, let's splash out, user defined, that's future proof.
Oops, here we are in 2023 and while nobody cares about Interlacing, and the arbitrary user defined resolutions allow me to express 4K display, there's nowhere to pick 120fps, or to specify 12-bit colour.
- thesuperbigfrog 4y ago>> I think the big problem is that any such thing you'd design an interface for might change in such a way that it doesn't make any sense to preserve this hypothetical interface over time. Rust's standard library promises to keep maintaining all the pieces long after they're obsolete, and the bigger it gets the harder that will be. True. However, without more standardized components the Rust ecosystem could end up like the Common Lisp library problem: lots of libraries in various states of maturity and maintenance with no obvious choice of what to use to solve your problem. Big standard libraries help to drive corporate and enterprise adoption. It is part of the reason why Java and Python are so widely used in corporate / enterprise environments. It brings a lot of standardized functionality and longer-term support that those kinds of environments want. We rely on the Rust standard library because it will be maintained for a very long time and has mostly stable APIs. Without a bigger standard library or some other kind of standardization, we would build our own libraries that might re-invent the wheel, but at least we know that our libraries will be maintained.
- pjmlp 4y agoOn the other hand, developers, including the Rust team appreciate the 1970's UNIX model to be available in 2023. Originally all the UNIX libc that didn't land in ANSI/ISO C89 and became POSIX instead.
- thesuperbigfrog 4y agoPerhaps we need a Rust-centric POSIX replacement? Rust is making inroads in the Linux kernel which is good. On HN I have seen links to many interesting blogs and articles about how painful interfacing Rust with the eccentricities of C / libc can be. Unless there is a better replacement for POSIX (which as written requires C), then POSIX will remain along with all of its eccentricities.
- pjmlp 4y agoThat is what languages with rich standard libraries allow. In Rust's case maybe what is required is a kind of curated set of modules, a bit like Java EE defined a set of basic functionality (in multiple JSR specifications) that every application server should provide, including Spring based ones.