News for hackers. Stuff that matters.

A comment on A new year resolution to have Crystal reach the 1.0 milestone in 2017. Parent comment

Re:A new year resolution to have Crystal reach the 1.0 miles... by RX14 on Friday December 30, 2016 @07:42AM (#13284086)
I think that's a mistake in the article, we will follow semver after 1.0.0, and we definitely don't want a 2.0.0 less than two years after 1.0.0. I'm sure crystal will provide the same stability guarantees as go and rust.
[ Parent | on HN ]
Re:A new year resolution to have Crystal reach the 1.0 miles... by gravypod on Friday December 30, 2016 @07:57AM (#13284130)
My main concerns are development time and tooling. Crystal looks great and offers some great features that no other native-compiled languages really offer at this time (which is amazing) but I am the kind of person that needs first-class IDE support to take a look. I think crystal would be the perfect platform for some great software development.

Aside from tooling I need a guarantee that my code, if following all of the best practices, should be compilable from now till the foreseeable future.

[ Parent | on HN ]
Re:A new year resolution to have Crystal reach the 1.0 miles... by spalladino2 on Friday December 30, 2016 @02:17PM (#13286558)
The idea is to avoid falling into a Python 2 vs 3 situation, by being very careful in how we break compatibility when moving to the next major.
[ Parent | on HN ]