Why Abstract? Doesn the world already have enough cross-platform development frameworks?
Hmm… not really. There are several reasons: – As nice as Qt is, it’s expensive, and doesn’t quite do things the way I would like. Abstract could be written on top of Qt, but then anyone using Abstract would have to have Qt too. Qt also requires its own compiler for certain things. – As nice as wxWindows is, it’s still a rough diamond (on the Mac), plus it has a lot of MFC influence. It’s good as a wrapper technology but not as an abstraction system. As wxWindows matures, it’s entirely possible that Abstract (or a version of Abstract) could be written on top of it. – As nice as Java is, it’s still slow, not really open, not really portable, and only runs Java code. – As nice as Mono is, Microsoft may flex its patent/copyright muscle with the underlying .NET interfaces, and the Windows.Forms implementation is pretty intense (using Wine, etc.). The .NET interfaces also do some things wrong. – As nice as Wine is, it doesn’t provide the user experience of the native platform, and it is st