| The Ultimate Business Machine Technology, business And, not least, about by: Bernard Teo
|
The Ultimate Business Machine - ArchivesList of Categories : Database * Technology * Commentary * Singapore * Travel * Wed 07 Nov 2007 Maven for LeopardCategory : Technology/MavenForLeopard.txt The current version of Maven already works on Leopard. I've just tested it on Leopard. So, Luca and Maven, for the moment, now work on both Tiger and Leopard. But I'm planning new versions of both applications that will take advantage of unique Leopard features. So it's possible that future versions of Luca and Maven will only run on Leopard. But I'll get back to them in late December when I've cleared a few things I plan to do on MailServe, DNS Enabler and WebMon. It has been an exhausting last two weeks, and I hope to take a couple of days break to rest and to think. And then, I'll start work again. I've been asked, why do I want to work on Maven when there are already competing solutions like CocoaMySQL, etc. The only answer I have is that I build Maven for myself, so that I can build Luca faster. The important thing about Maven is not (at least, not yet) the CocoaMySQL-type GUI. It's the database access frameworks that I've embedded inside it and which do the heavy-lifting of talking to the databases in a consistent programmer-productivity-enhancing way, and which are the exact same ones I use in Luca. Maybe because I've spent so much of my working life in PC/Windows-dominated IT/MIS environments, I have a different view of the requirements for data-access and data-mining tools than, perhaps, most other Mac developers. I'm trying to marry the two - to build tools that won't be scoffed at by IT/MIS folks; if possible, to build tools that could make their jaws drop in areas where they appreciate - e.g., raw power and performance and the ability to express difficult concepts to get at the data - and yet still have the elegance we come to expect as Mac users. For that, we need minute control over the database access layer. Another question. Why do I persist in calling it Maven, when there's already an Apache project by that name? In time, the name may change. But for now, Maven captures the essence of what I want the user to be when he or she is using this tool to navigate, access, and understand the database. For now, all this is just a dream. But now and then, I get a glimpse of how to achieve it. |
Mac@Work
Services running on this server, a Mac Mini running Mac OS X 10.9.2 Mavericks:
all set up using MailServe, WebMon, DNS Enabler, DNS Agent, VPN Enabler, Liya and our SQL installers, all on Mavericks. |
||||||||||||||||||||||||||
