The Open Source of the framework is good news, but I
can't find downloads (although I can see the changes log). This is crucial to instil confidence for VB6 professionals stranded by "the great treason of Redmond" (quoting
www.vbforums.com/showthread.php?t=565238 ).
Being a strandee, I can't invest time in this great project only to find it stagnates or changes. I don't mind paying say $100 for access to source as long as it IS open (and I know it compiles). The IDE source is important too, but failing that, an Open Standard i/f for IDEs?.
For the record, I've tried Jabaco and find it follows the philosophy of VB6 s/w well.
It's simplicity despite portability and power is genius.
Why VB / Jaba? I argued with Microsoft at high level to retain VB6. It is the event driven, departmental hierarchy and bug-defying tight-binding & single-thread that I miss most. VB6 is not "bad software" or a "horrible hack" as non-VB forums suggest -- we bought the enterprise edition and VB was the 2nd biggest part of MS's VS6 (high-level in VB, low level in C++).
Why bring this up now? Although VB6 went out in 2000, it was only the 2010 MS Dot Net release that announced no more attempts at a proper upgrade path to Dot Net. There are still major users out there including me, banks, public services etc, who were all secretly holding out for a decent upgrade path. Now we don't trust MS even if they did one.
What does this mean? It seems Jabaco is well placed to take over RAD. However, to be a serious contender against the staying power of MS etc, Jaba must show dedication to the ethic of open source. Major clients (banks etc) and suppliers (Oracle etc) are going this way.
So I will be watching closely, hope to see source soon, and will help where I can.