Domino <===> Scott Adams

Again this year, I did not attend IBMConnect. Last year it was for personal reasons, this year it did not make sense given the direction that I see IBMConnect heading towards. However, I really appreciated that IBM had a number of sessions live and recorded on Livestream for me to watch. What I really miss is not the sessions, but seeing the people within our community. But that is OK since I will most likely see them at ICON and MWLUG. And I always have Twitter. The most compelling session for me was the OGS with Scott Adams. To me what Scott Adams said about himself was a reflection of what I feel about Domino/XWork. As he mentioned in his presentation, he is not the best in anything he does, like drawing. He practices and tries and eventually become better at it. That is how I feel about Domino/XWork.

We have been looking into other server technologies and see what we are missing. Should we venture off into another server platform? Domino is not fastest compared to other technologies, it is not cool compare to nodejs, its HTTP thread is small compared to other technologies, its NoSQL technologies is limited by the 64GBytes file size and 32K limits, view indexing should be redesigned, each time I talk to someone they make fun of me for working with old technology, with the exception of the Windows version the SSL technology is old and so on and on.

But as Scott Adams said, I am OK with that, because just like Scott Adams, Domino/XWork is flexible. We can and do build on top of what we have and that is the key!

SSL not up-to-date, proxy it with Nginx server
Need bigger database infrastructure, create connectors to CouchDb or MongoDB
Need more threads, get a bigger server, it will still be smaller than a Websphere-based server
Need bigger field sizes, use MIME
and so on

Because of its flexibility, we as a community will figure out a method to address any limitations.

But one thing that cannot be beaten if IMPLEMENTED CORRECTLY is SECURITY. So when others are making fun of me using Domino, I ask them how is security implemented and you know what a majority of the developer say, oh the admin handles that or why do you need that level of restrictive security. In today's world, that is the wrong answer. Again, just like NoSQL, Domino was and will be ahead of its time if that makes sense.

So as I move forward on learning, tailoring, and improving Domino/XWork for our needs, just like Scott Adams, we are improving what Domino/XWork can do and more some and when someone ask me why I am using Domino/XWork, I tell them because it is the best and meet the needs of all my current AND future customers.

The iPhora Journey - Part 8 - Flow-based Programming

After my last post in this series -- way back in September 2022, several things happened that prevented any further installments. First came CollabSphere 2022 and then CollabSphere 2023, and organizing international conferences can easily consume all of one's spare time. Throughout this same time period, our product development efforts continued at full speed and are just now coming to fruition, which means it is finally time to continue our blog series. So let's get started... As developers, most of us create applications through the conscious act of programming, either procedural, as many of us old-timers grew up with, or object-oriented, which we grudgingly had to admit was better. This is true whether we are using Java, LotusScript, C++ or Rust on Domino. (By the way, does anyone remember Pascal? When I was in school, I remember being told it was the language of the future, but for some reason it didn't seem to survive past the MTV era). But in the last decade, there a...

Creating Twitter Bootstrap Widgets - Part II - Let's Assemble

Creating Twitter Bootstrap Widgets - Part I - Anatomy of a Widget Creating Twitter Bootstrap Widgets - Part II - Let's Assemble Creating Twitter Bootstrap Widgets - Part IIIA - Using Dojo To Bring It Together This is two part of my five part series "Creating Twitter Bootstrap Widgets". As I mentioned in part one of this series, Twitter Bootstrap widgets are built from a collection standard HTML elements, styled, and programmed to function as a single unit. The goal of this series is to teach you how to create a Bootstrap widget that utilizes the Bootstrap CSS and Dojo. The use of Dojo with Bootstrap is very limited with the exception of Kevin Armstrong who did an incredible job with his Dojo Bootstrap, http://dojobootstrap.com. Our example is a combo box that we are building to replace the standard Bootstrap combo box. In part one, we built a widget that looks like a combo box but did not have a drop down menu associated with it to allow the user to make a select...

The iPhora Journey - Part 3 - Creating an Integrated UI Framework

The iPhora Journey - Part 1 - Reimagining Domino The iPhora Journey - Part 2 - Domino, the Little Engine that Could The iPhora Journey - Part 3 - Creating an Integrated UI Framework There are many ways to create the user interface (UI) for a web application. The HTML page could be created on the server and then pushed out. It could be static with the data generated on the page by the server with JavaScript, providing a more dynamic experience, or the server could generate new HTML content to update portions of the web page. XPages or PHP are good examples of this. Another method is to have the web page partially generated by the server and have JavaScript build the rest of the HTML by pulling data from the server via an API. This is the approach used in the Single Page Application (SPA) model. In all cases, it is still dependent on the web server technology being using. As mentioned previously in this blog, XPages is dependent on complete integration between form and document, whi...

Domino Interface

Search This Blog