It's great to have a liberally licensed alternative to Meteor and Firebase. Many thanks for that.
What I have taken from the article:
1. Derby is done by competent people
2. They support server and client code sharing
3. MIT license
4. NPM instead of proprietary packaging
I especially like 2). It was one of the killer features of Appjet which had code sections like: /* appjet:server /, / appjet:client /, / appjet:both */ You can guess what "both" did. Appjet was miles ahead for its time. I am sure David will take care of that part at Meteor's.
Last but not least, I don't like the name Derby. It is already used by a popular Java SQL database.
Agree on the name. I'm not even sure how to pronounce derby. I have heard it pronounced both "darby" and "derby", with the former being the more traditional, "correct" pronunciation. Kind of like how you are to pronounce grand prix as "gron pree" instead of phonetically. I don't know if it's best to be "correct" or to "dumb it down" to fit in with your peers.
What I have taken from the article:
1. Derby is done by competent people 2. They support server and client code sharing 3. MIT license 4. NPM instead of proprietary packaging
I especially like 2). It was one of the killer features of Appjet which had code sections like: /* appjet:server /, / appjet:client /, / appjet:both */ You can guess what "both" did. Appjet was miles ahead for its time. I am sure David will take care of that part at Meteor's.
Last but not least, I don't like the name Derby. It is already used by a popular Java SQL database.