TwinBasic

[fafalone]

1) Yes, it has been lifted, along with most other similar limits.

2) There's a lot of bugs with running, especially when running them in 64bit VBA, and Property Pages aren't supported for in-project UCs (.tbcontrol, same as .ctl, as opposed to ocx)

3) The Printer object is completely unimplemented at this point, but it's an announced feature for v1, so can be expected very likely before the end of the year. If you want to print, you'll need a solution such as BSPrinter (has been tested to work in tB according to their page), or doing it manually through Windows APIs/COM interfaces.

4) Collection performance blows VB6 out of the water on most operations, some being thousands of times faster, and matches it on the rest. And this is without compiler optimization (early tests of that show it beating VB6, but it can't optimization code with classes/objects yet)

5) Lines of code themselves aren't a limitation... my ucShellBrowse control works perfectly, for instance, and that's 50k lines with a dependency on tbShellLib, my oleexp replacement that's also covering large swathes of the Windows API base, clocking in at 167k lines, nearly every one going into the global namespace. But larger projects do raise the odds something in it will be unimplemented or hit a bug (of which there are still quite a few, being in beta and all).

Check out these Collection benchmarks Wayne posted in the Discord channel:


removal all items via index position (backwards, sequential), 60000 items. 2607ms 1ms
removal all items via index position (random), 60000 items. 2270ms 43ms

(the last two couldn't fit on my screen for the screenshot)