Earlier today I posted this tweet. It followed another update from John Curtis teasing more enhancements coming to DQL. If you’ve been following closely presentations and announcements about DQL, there are a few things that have been said and seem clear to me, things that give insight into the approach with DQL that are interesting and demonstrate the team is thinking beyond history, beyond Domino, and building for the future. Let me elaborate.

In base Eclipse it’s also possible to set these, in the eclipse.ini and display the current heap size in the preferences, on the General tab. That setting for displaying the current heap size has also been available in Domino Designer’s preferences for some time. You can’t see the setting in the Notes Client, only in Domino Designer. It’s again on the General tab.

This article has been prompted by my previous one on Domino application development. One of the major differences between Domino application development in the past and the approaches for Node.js-related development in the future is architecture. But part of that could also be an inhibitor for existing customers, because of the incubated world of Domino.

Some years ago I wrote a blog post called “Whither the Notes Client”. At the time (2012) XPages was flourishing, the Notes browser plugin (subsequently ICAA) was being launched, Symphony was being stopped and the IBM-specific enhancements routed back to Apache OpenOffice and iNotes was being integrated into what is now Connections Cloud.