Probably more likely that he doesn't know the timeline much more than us. He probably has a to-do list he is working on. And for every item he checks off, one or two more gets added. Holding him to a timeline for a launch would be ridiculous.
This is my fear and why I am for getting getting something deployed. I believe the more we test, the more we realize better ways to provide more flexibility / value to xel job authors and it becomes a never ending cycle. Ideally, I think it would be best if a solid version that includes basic ElasticPL functionality is deployed...but even with that we now have a couple question...do we stick with the POW model we have?, EK identified some issues with the underlying memory model so we need to determine if changes are needed there, etc...and this was just in the last 24 hours.
Hopefully, people won't make their decision based on the bubble crypto is currently in...not sure how much longer it will be but I've got to believe this bubbles going to crash and we'll be right in the middle of that...so you won't see the huge influx of buyers. I base what I recommended to do solely on what I feel may help us get more devs to pick up some of the more mundane code fixes while EK continues to explore new use-cases. But I could be completely wrong
Guys, you should listen to coralreefer (and provenceday - see his previous posts). coralreefer and EK know the major issues, so if the main problem for now is the POW, then we should ask them to focus on that, and then (if that's the only major issue) release the first version. That version should include basic wallet functionality + the first computing-related features.
Forget about launching the finished product because it won't happen. There's no way EK is able to develop everything and then just launch finished product - it's always something that needs to be modified, so I think unvoid has the point that Elastic needs more market-oriented progress in order to get a critical mass for further development.
Elastic is mature enough to be launched even as bare wallet, with all in-progress features scheduled for staggered deployment. That's common strategy and there's nothing wrong with it. I personally think that "it's-ready-when-it's-ready" approach is really bad idea.