We have spent some time putting together an estimate for what’s pending for a 1.0 release that we could be proud of, an it comes to about 1.400 additional hours. At a pace of 2x the monthly hours we are currently covering with donations (~54hs) that means another extra 14 months which is way longer than what we want. We are trying to rally some other sponsors to shorten that time; it's looking positive for now, but we need a few more weeks to provide another update on that.
Parallelization is one of the main efforts for 1.0. We managed to run the multi-threading sieve of Eratosthenes sample with reasonable results on Linux and poor results in OS X.
Windows port is advancing thanks to the extended community, can't comment much else on that.
I wouldn't want Windows support to block 1.0! I think it would be important to get feature complete with 1.0, which, in turn, will expand the interest and base for Windows support.
We have spent some time putting together an estimate for what’s pending for a 1.0 release that we could be proud of, an it comes to about 1.400 additional hours. At a pace of 2x the monthly hours we are currently covering with donations (~54hs) that means another extra 14 months which is way longer than what we want. We are trying to rally some other sponsors to shorten that time; it's looking positive for now, but we need a few more weeks to provide another update on that.
Parallelization is one of the main efforts for 1.0. We managed to run the multi-threading sieve of Eratosthenes sample with reasonable results on Linux and poor results in OS X.
Windows port is advancing thanks to the extended community, can't comment much else on that.
Glad to hear that!
I wouldn't want Windows support to block 1.0! I think it would be important to get feature complete with 1.0, which, in turn, will expand the interest and base for Windows support.
Agreed. It's not blocking 1.0.