Looks like a fun exercise, and I agree with your point that Domino is not the only RAD platform in town.
However, given the simplicity of this application, which is non-relational CRUD, one could "build", or better said configure it in a platform like SharePoint within 1 minute. Too lazy to record it, but it would go like this:
- Create new custom list
- Add the columns
- Done
You will get the creation, editing, deleting and views out of the box. On top of that, you get subscriptions, Excel exporting, filters, user-configurable views and much more. Your point still stands, but these kind of greenfield CRUD "apps" can hardly be called apps anymore. In my environment, they would not be developed as a custom app.
Therefore, if you would ever plan to do more advanced comparisons, I have some suggestions :)
- Complex workflows. Recently did one containing 80 steps, both serial and parallel with lots of custom routing
I know, it would be impractical to screencast such a comparison, I'm just saying that the typical custom enterprise app (if created at all) in my experience contains many of the elements above.
So yes, Domino is not alone in its RAD capabilities and your comparison proves it. Yet, it does not compare actual productivity in the creation of a real world app. If you want to be thorough, you would even have to include non-development tasks, such as deployment.
I have been in the fortunate position to have seen LN&D, PHP, .NET and SharePoint in use on a large scale in the same team, in the same company, building roughly the same kind of applications. That makes for a decent comparison I think. I could list dozens of criteria and list you the differences, but I'll instead jump to the conclusion: the differences are neglectible from a business/cost point of view.
Looks like a fun exercise, and I agree with your point that Domino is not the only RAD platform in town.
However, given the simplicity of this application, which is non-relational CRUD, one could "build", or better said configure it in a platform like SharePoint within 1 minute. Too lazy to record it, but it would go like this:
- Create new custom list
- Add the columns
- Done
You will get the creation, editing, deleting and views out of the box. On top of that, you get subscriptions, Excel exporting, filters, user-configurable views and much more. Your point still stands, but these kind of greenfield CRUD "apps" can hardly be called apps anymore. In my environment, they would not be developed as a custom app.
Therefore, if you would ever plan to do more advanced comparisons, I have some suggestions :)
- Complex workflows. Recently did one containing 80 steps, both serial and parallel with lots of custom routing
- Integration with back-end systems such as SAP
- Data-driven security at every level
- Relational data combined with unstructured data
- Mobile access
- Offline access
- Email integration (lazy approval, task creation, scheduling)
- SSO
- Portal integration (SAP portal, SharePoint)
- BI/BW reporting
I know, it would be impractical to screencast such a comparison, I'm just saying that the typical custom enterprise app (if created at all) in my experience contains many of the elements above.
So yes, Domino is not alone in its RAD capabilities and your comparison proves it. Yet, it does not compare actual productivity in the creation of a real world app. If you want to be thorough, you would even have to include non-development tasks, such as deployment.
I have been in the fortunate position to have seen LN&D, PHP, .NET and SharePoint in use on a large scale in the same team, in the same company, building roughly the same kind of applications. That makes for a decent comparison I think. I could list dozens of criteria and list you the differences, but I'll instead jump to the conclusion: the differences are neglectible from a business/cost point of view.