Mirror of forum.nim-lang.org

10087 :: 2.0 RC new and old

• Antichristos (orginal) [2023-04-11T02:25:35+02:00] view original

  Good people, please answer me, clarify! Will Nim solve the problems of different Nim implementations? With each new version of Nim - all the time something is removed or added. Projects simply do not support new versions of Nim, thereby having to rewrite the code almost from scratch or to develop a project without updates on a static basis.

  Will version 2.0 RC be stable and support all the following updates and upgrades? I mean, so that Nim can work with all the old features and only add new features.

---

• Araq (orginal) [2023-04-11T06:32:32+02:00] view original

  There is a long deprecation cycle already before we remove a feature. It's easy for most projects to keep up.

  Projects simply do not support new versions of Nim, thereby having to rewrite the code almost from scratch or to develop a project without updates on a static basis.

  That doesn't match my experience, every new release is tested against a range of real-world projects.

---

• moigagoo (orginal) [2023-04-11T06:51:34+02:00] view original

  Projects simply do not support new versions of Nim, thereby having to rewrite the code almost from scratch or to develop a project without updates on a static basis.

  I didn't have much trouble updating for Nim 2.0 with Norm or other packages I maintain. Is there a specific issue you're having with a specific package?

  Nim's upgrade story is as gentle as it gets, there's no comparison to Python 2/3, Perl 5/6, or Go pre1/1.

---

• Calonger (orginal) [2023-04-11T08:39:19+02:00] view original

  sigh... The real problem is there are not enough versions... Nim add features all the time but release very slow, everyone has to change code all at once for all the new features. Then too many features, old code is "broken" but would be fixed easily if it was gradual release. Look at Rust, they release fast and no one complain

  Time between Version 1.0 release and Version 1.2.0 release is 5 months

  Time between and Version 1.2.0 release and Version 1.4.0 release is 6 months

  Time between Version 1.4.0 release and Version 1.6.0 release is 1 year

  And now time until Version 2.0 release is 1 year 6 months+...

---

• Clonk (orginal) [2023-04-11T11:05:59+02:00] view original

  With each new version of Nim - all the time something is removed or added. Projects simply do not support new versions of Nim, thereby having to rewrite the code almost from scratch or to develop a project without updates on a static basis.

  Do you have concrete examples of this happening ?

---

• treeform (orginal) [2023-04-11T16:55:35+02:00] view original

  I don't see any problem here. I don't have to fully rewrite everything for new versions. I manage a plethora of Nim libraries such as Pixie, Vmath, Jsony, Boxy, Bumpy, Ws, Webby, Chroma, and so on. Yes, some changes are required to transition between Nim versions, but they are minor. Keeping up to date has been a breeze. Perhaps it's because I don't go overboard with macros or advanced features. Maybe it's because I just use the language straightforwardly. I feel Nim handles the deprecation of old features pretty well.

---

• PMunch (orginal) [2023-04-11T19:11:01+02:00] view original

  As someone who maintains a lot of libraries and frequently uses macros I still have very few issues. There used to be a case many years ago that you would find a library which hadn't been touched in a year or two and it no longer worked, but I find that to be the case less and less. But as @Calonger hinted at the bigger issue is that many projects gets released depending on devel because it uses an upcoming feature that hasn't been released yet. And then people forget to actually pin it to an actual version when the next version releases.

---