Just so MOUSE, DBPro has to have a solid foundation, or anything built on it might start to wobble. I have built FPSC entirely upon it, and used the exercise to find all the weak spots. The bug week added the plasterwork to make those refinements visible, and by the time FPSC V1 is complete, the stability will have increased further. Unlike FPSC-EA, FPSC-V1 is a retail monster launch and it will need the stability to stand up against just about every PC nightmare configuration out there. For this, there is a hefty dose of system testing to hit U58+ before you see U6.0. I am leaning away from adding too much more to the core command set, and instead opt for add-on DLLs for further enhancements. The main reason is that the core can continue to get more stable as fewer and fewer changes are required to it. When you make a change, you risk a bug (or as DBPro users like to think of them, feature amendments). I hope to do another bugweek right after FPSC-V1 is done, to catch those bugs that escaped the net in March, and any new ones that might have found their way into the DB universe. Eventually, the core will simply exist as a reliable predictable framework. If I did then move on, at least my contribution would have a level of dependability (and of course, shelf life).
"Small, smart, and running around the legs of dinosaurs to find enough food to survive, bedroom programmers aren't extinct after all
"
