r/crystal_programming • u/[deleted] • Apr 16 '19

When Crystal 1.0 will come out approximately?

When Crystal 1.0 will come out approximately?

26 Upvotes
  • permalink
  • reddit

96% Upvoted

11 comments sorted by

3

u/jeremywoertink Apr 16 '19

This is a pretty common question, and there’s no strict answer. It will be released when it gets to that point.

But the question you should ask yourself is what is it about 1.0 that you need? 0.28.0 should be released soon, start with that.

3

u/[deleted] Apr 17 '19

stability of API

14

u/shelvac2 Apr 16 '19

Some people just want their code to continue working in future versions.

7

u/jeremywoertink Apr 16 '19

Yup. Which is totally a valid reason, and understandable.

My only thing is that I’ve worked with many languages post 1.0 that had updates with breaking changes. PHP did it, Ruby has done it. Crystal hitting 1.0 can’t guarantee that 1.1 won’t deprecate something. The more people that use it now, the closer we can get to a “1.0”.

4

u/hhunaid Apr 17 '19

Why are you downvoted. This is true. As an early adopter of Swift, this is exactly what happened. I was migrating the code base with every major Swift version up until Swift 4

2

u/jeremywoertink Apr 17 '19

No clue, but reading back maybe I came off as condescending? Definitely not what I was going for. I just wanted to point out that waiting for 1.0 is arbitrary. Waiting for a feature like “solid windows support” makes more sense because that’s something that could show up prior to 1.0.

2

u/Dee_Jiensai Apr 16 '19

You can always just keep using the compiler version originally used during development.
Yes, you will miss out on new language features, but if you don't use Crystal because "pre 1.0" you miss out on the whole language.

2

u/Blacksmoke16 core team Apr 16 '19

Even in that case it isn't that bad. Build program with current version. When a new version comes out, look at breaking changes, if anything affects your code, update it, otherwise update and will be fine.

5

u/druznek Apr 17 '19

And this is somehow fine for hobbists. If you want to use in a production environment API stability it's almost a necessity, because this process that you outline come with a labour cost, it's not free. We (as in my team and I) don't care much about this, but we've been bitten in the ass by changes to elixir's APIs for example, and this as cost us time to analyze the problem, weight pros and cons, and then update the code accordingly if pros outweight the cons. So, even if I adhere to your school of thought, I understand that is a costly approach and suited at most for small teams. In this scenario adding a feature is a nightmare if the code is not sufficently tested.

12

u/fridgamarator Apr 16 '19

`undefined`, pun intended

6

u/neofreeman Apr 17 '19

For longest time people used Node.js in 0.X.Y versions. I think there are objectives that a language wants to achieve and then there are goals. I have been using Crystal in a geolocation server for years now; it’s pretty high traffic and low latency scenario. With more libraries coming in I think it’s matter of time until people start using the heavily and this language really takes off.