5 ms·
I've never used Julia but why would a language make breaking changes on each release? It doesn't have backwards compatibility? That sounds like a nightmare to w
by driverdan 8y ago
I've never used Julia but why would a language make breaking changes on each release? It doesn't have backwards compatibility? That sounds like a nightmare to work with. Is it because it was pre-1.0?
- ChrisRackauckas 8y agoYes. v1.0 is literally the release so that all future 1.x releases are backwards compatible. That's why it's such a big deal.
- celrod 8y agoExactly, and that is why 1.0 is a big deal: the end of breaking changes until Julia 2.0.
- KenoFischer 8y agoPre 1.0, we've generally provided backwards compatibility for one version with deprecations. Somewhat ironically that has often led to people just living with walls of warnings until the version that actually broke it came out, which led to a worse experience. We also have automated upgrade tools now, which can do many of the simple (and some not so simple ones) automatically. The situation on 1.0 is slightly worse than in previous releases because we released 0.7 and 1.0 simultaneously to avoid having to ship 1.0 with active deprecations. Of course that means that people will have to fix their packages now, rather than waiting until next year.