Comment by gingerBill
3 months ago
Those are library/package collections which contain multiple different packages, not the packages themselves.
And we will take backwards compatibility seriously when we hit 1.0, and only "break" on major versions.
3 months ago
Those are library/package collections which contain multiple different packages, not the packages themselves.
And we will take backwards compatibility seriously when we hit 1.0, and only "break" on major versions.
> And we will take backwards compatibility seriously when we hit 1.0, and only "break" on major versions.
I'm talking about post 1.0 language choices:
- Choose backwards compatibility. Packages frozen in time, you get "Packages go to std to die." - Choose to break backwards compatibility. The ecosystem is split, some choose to go Odin 2 some are Odin 3.
I already know all that, that's why we are being very conservative and slow when it comes to figuring out what is meant to be in 1.0.
I don't think it will matter. There will be things people want that Odin won't have in the vendor package list.
Then those people will have to manage dependencies, which is a hell on its own. Which will cause problems. Because people are super lazy so they will automate it. In the end only thing no package manager gets you is multiple package managers to juggle.
Many languages started without package managers and eventually got them - Java, JavaScript, Python, C, C++
4 replies →