|
|
|
|
|
|
by dmitriid
3095 days ago
|
|
|
> it mostly likely means slowing down progress outside of the new focal domain. IIRC, at the end of last year they promised 1.0 by the end of this year. Then they missed a 0.6.x release by four months. Now they don't even talk about a 1.0 and even minor releases no longer have a due date [1] So yes, all these additional endeavours will definitely slow an already slow progress to a halt. I also wonder if they finally fully implemented integers and floats... [1] https://github.com/red/red/milestones |
|
|
To be honest, I don't think that was ever a realistic goal, even when it was set. The only benefit of setting such a goal ahead of when a clear release date can be determined is in keeping up momentum during the awkward middle phase of language maturity, when key functionality is clearly missing but you want to maintain interest. This isn't just a Red thing, it's fairly common.
If I had to guess, even by the end of next year, it's much more likely we'll be looking at a 0.7.x release (or, best case, 0.8.x) rather than 1.0. The good news is that the language is likely to be generally useful around 0.7.x (assuming the roadmap is stuck to), as that's the point when the network I/O features are being implemented.