More on Notes sucking
And so the debate rages on — remember this site from a while back?
Uncle Dirtae: Lotus Notes sucks.
Well I can’t be bothered to set the record straight if people are ignorant enough to say stuff like “Only saw one person mention the support personnel needed for Bloats. Takes on average 3:1 over what Exchange requires.” or “Not being able to automatically deal with multiple time zones in calendaring is a serious shortcoming.” — but if you want to, be my guest. This one is a particular gem — from someone who sells himself as a consultant no less:
The MASS majority of the people that like this are one-trick pony developers and admins that don’t know better. Some of them have experience in other technologies, but are not technically capable of understanding them. Many don’t even have a technical degree, Notes was just something they picked up or went to a class and ‘poof’ they were a developer.
Heh. Oh, and by the way, if you’re from some marketing company who wants to sell your “Notes sucks” merchandise via this site: no thanks. I may be pissed off with Notes most of the time nowadays, but I’m not hypocritical about it: I still don’t see anything else out there that comes close in terms of what it does, so don’t worry about getting in touch any more. I would also include the charming “Gary” here, with his ever-so-useful (but funny) site...
Posted at 10:45 pm GMT on 01 Feb 2005 | Categories: | (6 comments)

I do like Notes and it beats the competition hands down. I've worked with Notes since 3.0 and currently plan to continue working with Notes and whatever it becomes for as long as possible, but I'm a techie. Notes has always been a product that seemed to be design by techie's for techie's. End users are not developers/administrators but the people who actually use the applications we develop/administer day in day out and don't care what platform it runs on so long as it makes their job easier. End users seem sometime to have been forgotten about.
I've have a few more Why's when it comes to the Notes UI' which I've previously posted in LDD..
http://www-10.lotus.com/ldd/nd6forum.nsf/55c38d716d632d9b8525689b005ba1c0/56b7aefadab43ff185256f11004224e7?OpenDocument
1) Functions that I can see no practical reason for the general users:
- View > Show > Hidden From Notes
- View > Show > Pass-Thru HTML
- View > Show > Java Applets Running
- View > Image Resources...
- View > Switch Form (how dangerous is this? I know you can prevent it by not having any forms in the Create Menu but why would you want a user to switch a form anyway?)
- Document Properties > .. most of the tabs
- Actions > Edit HTML Attributes (what is a user going to do with this option?)
- File > Tools > Debug Lotus Script (I can give examples of a user with Client only (no designer) and Author access to a db who used Debug and modified variable values "because he wanted to see what it did" !!
- File > Tools > Show Java Debug Console
2) Functions that should be hidden when not authorised
- Create > Agent...
- Actions > View Options > Rename..
- Actions > View Options > Design..
- Actions > View Options > Move..
- Actions > View Options > Remove View..
- View > Agents
- View > Customize This View...
3) A designer/administrator should be allowed to block these Functions completely.
(Private views are a maintenance nightmare and should be banned unless they are part of the original database design and can be deleted using GetView)
- Create > Folder...
- Create > View...
- View > Go To > .... (Why when a designer has spent hours designing the perfect frames and outline would you want a user to the user View > Go To ??)
Re functions and end users, as we know Notes comes from a very strange place. People seem always to compare it with Exchange - to this day I have no idea why - and harp on about the email functionality within Notes.
But that is not what Notes is about! Notes is derived from PLATO, a very different beast from email clients... and of course PLATO was aimed at people quite different from your typical corporate user (the current target for Notes).
I've said it before, as have many others: if your organisation is using Notes solely for email, then that's totally inappropriate technology. Lambasting an application / platform for the failings in your organisation's IT strategy is stupid, to say the least.
The origins of Notes lead to the mismatch: end users (not dedicated developers) used to do all kinds of crazy stuff with Notes (no doubt many still do), and on a very ad hoc basis -- that was Ray Ozzie's explicit intention with Notes.
The problem nowadays is that corporate IT and applications are heavily controlled (often with good reason), thus Notes looks more and more like the anachronism it is.
I get the impression that the forthcoming managed client for Workplace, with the intended Notes/Domino convergence, is the reason why some of the interface oddities in Notes aren't being addressed: why bother when the next-gen client will be far more controllable from the get-go?
I personally like and use private views myself all the time. They are invaluable for maintaining and troubleshooting database problems, but I am a techie and know (or at least should know) what I'm doing. I don't doubt that you and everyone else reading this blog has a pretty good ideal of how to create and modify views, but 90% (guesstimate) of end users do not.
I'm not suggesting that Private views should be banned altogether (well actually I was but I've mellowed a bit). An ACL option "No Private views unless Private on First Use" would be fine.
Lets face it who wants to support a user base that creates private views left right and centre. What happens when a database design is updated, field names change, form names change etc, the information the view is meant to display may no longer be available. There is no way of updating the private view design automatically, users probably will not have a designer client and often the database design is hidden. If all users are regularly having to create Private views then perhaps the database design should be updated to include the view as a shared view. The only time a Private view is needed is when data needs to be displayed based on the current user. (IMHO)
I do like the principle aims of the Notes platform, I would not use it, develop applications for it or spend half my life fighting its corner if I did not believe in it. Notes has come a long way from Plato, and it has a long road ahead of it but, as Ben points out the Notes user base is now very different from that of Plato.
AJP