Hi,
Pretty much just the title.
For example, there is a library for i18n but there is not for a11y.
It’s is clearly a harder problem with no clear or universal OS support, but it might be battery worth including or vendoring in the future.
I remember hearing somewhere that future encryption algorithms will be added and supported, but I can’t find the source for it (may have not even been for odin). Even if true, it’s not quite a new battery I think.
The library system lends itself well to adding more stuff, but a line has to be drawn somewhere. What is / is not worth including? If anything at all?
Is there an official stance on this?
I don’t think there is an official stance on what will be added and what won’t. As far as I know it’s basically at Bill’s discretion. There have been a few libraries added recently including box3d and rexcode.
You remembered right, the crypto library is constantly being improved so that some of the more complex algorithms can be added in the not too distant future. There is also a http library under development and a few others as well.
Not sure if you have seen the Odin 1.0 announcement video but it contains some info about what’s coming soon. The following link contains the video and at the bottom you can also view some recent package changes.
https://odin-lang.org/news/newsletter-2026-spring-summer/
2 Likes
Thanks for the answer. I’ve seen the announcement, but not the post.
The announcement was mostly the reason I asked. 1.0 for a language feels adopting it’s final identity, since stuff is more or less baked in at that point. If stuff gets added, it risks making older stuff redundant or look dated in comparison. But then they can’t be removed for compatibility reasons.
But also 1.0 might mark the end of “not included yet” and the start of simply “not included”.
Again, the library system lends itself well to adding more stuff: I don’t think odin would feel bloated even with a million more packages.
I just want to know if stuff gets added after 1.0, and if yes, based on what. Thats why I’m hoping for an official stance or policy, even if it’s just
Popular and/or beloved and/or very useful stuff gets included. Now and in the future
We do plan to have more packages, yes, even after 1.0. Odin 2027 is just the milestone for the language itself, not the core library, vendor library, etc.
Packages take time to make and polish too, but we do plan to add more.
I am not familiar with a11y, and I’ll see if @Jeroen is because he was the one who developed the i18n package.
1 Like
Thank you for the answer, that is reassuring.
I used a11y as an offhand example, it wasn’t the point of the question, but also thanks for looking into it. It stands for accessibility and it is a very broad topic. It doesn’t have much to do with i18n beyond both being UI concepts. When I said no clear or universal os support I was specifically thinking of screen readers.
Like @gingerBill said, packages will continue to be added when ready even after 1.0.
As for a11y, I don’t believe it lends itself to a package like i18n. Where OS bindings are necessary to accomplish it and they’re missing, we’ll be happy to add those.
Some of that will likely end up having to live under vendor:darwin, and that rules out a core:a11y as those can’t import vendor packages. Maybe if in the future Windows, macOS and Linux can decide on a common standard - even if they each have their own API to support that standard - then we can think about a vendor:a11y.
1 Like