If someone was a passionate user of one of the other Tools For Thought projects, and they asked me to sell them on using Drummer, I would probably say why don't you stick with the product you like, and work with us to get it interoperating with Drummer. That way when you want to try Drummer, you won't have to switch, you can just use it, and use the other one too, whenever you like. #- This is something I struggle to explain to people. I'm 66 years old, and have spent decades making software, so I think about it differently than I did when I was say 22 and wanting to take on the world. My horizon is obviously 44 years shorter now than it was then. And my goals are adjusted as well. #
- As I said the other day, I've been lucky because of when I was born and my interest in technology, to be part of several "bare metal bootstraps," where we got down to a basic set of functionality, a complete machine that everyone agreed on, and we as developers built up from there. Some amazing things can be accomplished if the baseline is powerful. #
- I think of my "product" today not being Drummer or Daytona or whatever's next, rather it's wanting to have my passion, outlining, experience the same kind of birth as a platform as the Apple II did, or CP/M, MS-DOS, Windows, the web, RSS, podcasting. Look at that string! Wow. But today's users and developers haven't even really experienced one exploding platform. That's my product now. I want outlining to be the basis for growth the same way those others were. #
- So you don't have to use Drummer but do insist on the highest level of interop with it from the people who make your software. Don't accept no for an answer. I'm not. Hopefully that makes sense? #
- Drummer is more than a piece of software -- it's an interop bomb. It's going to sit there and grow, inviting others to interop with it, and every feature and service I add will make the proposition more enticing. Think of Drummer less as a product and more as a seduction. 💣#
