| ▲ | poulpy123 an hour ago | ||||||||||||||||||||||
I would have expected a modern language to have an extensive datetime library in its standard library | |||||||||||||||||||||||
| ▲ | lambda an hour ago | parent | next [-] | ||||||||||||||||||||||
The problem with this model is that then you try to build all of the libraries that you anticipate users are going to need in one big go before you release version 1 of you language. Because you're trying to do a lot at once, they don't ask get the proper attention they deserve. Then, because of stability guarantees, you're stuck only making backwards compatible changes in the future (or you risk either constant breaking changes, or big changes where a lot changes at once forking the ecosystem, like Python 2 to 3). So if you made any mistakes in the library, you're stuck with them, only being about to deprecate but never really remove them. The alternative is to keep a relatively small standard library, and a good package manager, to make it easier for people to iterate on API design in third party packages. Major version changes in a single library can have much less impact accross the ecosystem than standard library packages. Eventually you may get a de facto standard, and sometimes they are then later incorporated into the standard library. This model isn't without its downsides; it can sometimes mean fragmentation when standardization would help, sometimes these de facto standard libraries can become important enough that they run into the same ecosystem fragmentation issues on major releases. But it allows for more flexibility. The latter model is what the Rust project decided on for everything outside of the most fundamental time types. Dates and times and timezones are notoriously hard to model in code, and easy to create API designs that are full of footguns, so this is a place where that extra freedom to iterate was more important than standardizing on an API early on. That iteration has led to a number of different libraries, including time, chrono, and now jiff, allowing for exploring the space of API design to really get it right rather than being stuck with what was available early on. | |||||||||||||||||||||||
| ▲ | dminik an hour ago | parent | prev | next [-] | ||||||||||||||||||||||
Any modern language recognizes that some things are inherently complex and will always have tradeoffs that certain users won't be satisfied with and that will be locked in forever. Such modern languages then let users pick whatever approach they actually need by implementing sensible package management. | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | solidsnack9000 an hour ago | parent | prev | next [-] | ||||||||||||||||||||||
I'm not sure this makes sense for a systems programming language -- but I can see it for an application programming language. For a systems programming language, Rust is relatively easy to write applications in -- but I suspect standard library choices (and other choices) will be driven by the systems side for the foreseeable future. | |||||||||||||||||||||||
| ▲ | tredre3 an hour ago | parent | prev | next [-] | ||||||||||||||||||||||
Rust doesn't even have an async runtime in its standard library, despite async being part of the language. They believe increased reliance on third party dependencies is better for the ecosystem. Things like supply chain risks or disparate documentation or conflicting dependencies or enormous .cargo are seen as less of a problem than having a built-in API that could go stale one day. | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | sunshowers an hour ago | parent | prev [-] | ||||||||||||||||||||||
A poorly designed one, maybe. My understanding is that the Temporal model is a very recent invention. | |||||||||||||||||||||||
| |||||||||||||||||||||||