> many empty promises by the creator which V simply wasn't able to deliver on.
Seems like this trend will probably continue with regards to the "1.0 release in December 2019" claim advertised in the Github description[1][a], since things like memory management are not implemented yet[2] and the December 2019 deadline would mean going from "first public alpha"[3] to 1.0 in less than a year.
The world is full of projects which are late, never fulfill the original plan, disappear with people's money, pivot direction or funding source, put arbitrary restrictions on use, etc. If someone publishes an ambitious plan, the disbelief is likely not personal. It's: "that almost never happens, we need some serious proof". Especially if the timing is more ambitious than seen elsewhere.
No judgement here on the project, just an observation. I'm excited to see where the project ends up.
Hey, don't take such criticism personally. It's just internet spout. It's awesome how far you've come. Things that are worthwhile often take longer than expected. The key is for creators to limit or pad public-facing estimates as their projects grow toward completion. It's not easy to temper the innate ambition and passion that drives projects into existence as they mature.
I've gotten better at this but it's taken a couple decades and I've still not mastered it. I figure I'm in good company. Steve Jobs developed this ability between his stints at Apple and Elon Musk is still working on it.
I guess I’ll just leave this comment here so I can link you back to it explicitly in december when you ask for exact details on what you promise vs. deliver next time.