- 142comments
- 49comments
- 42comments
- 458comments
- 180comments
- —discuss
- 36comments
- 51comments
- 13comments
- 552comments
- 28comments
- 117comments
- 5comments
- 132comments
- 192comments
- 14comments
- 108comments
- 301comments
- 360comments
- 24comments
- 18comments
- 89comments
- 23comments
- 11comments
- 51comments
- 44comments
- 122comments
- 7comments
- 280comments
- 4comments
Polish is also a matter of taste and expertise.
why is there no scroll bar in this article?
Yes, horrible experience..
This was an enjoyable read. Especially the idea of someone living and creating between eras resonates with me.
I've seen and played with Lotus but I'm too young to have worked in any environment where it was the primary communication tool.
Still, my take away from OP is that Ozzied strived for Lotus to be much more than an email client.
Lotus makes much more sense as an attempt to bring the collaborative features of a shared university computer system with email, chat, forums, shared documents and applications to an ordinary networked PC like environment.
Something bigger than a weird email client.
I'm guessing you are writing about Notes.
Lotus was the name of the company that initially made the 1-2-3 spreadsheet.
Yes, Notes, sorry, totally forgot about 1-2-3.
Lotus Notes was too big, too self-contained, and too weird to be "Something bigger than a weird email client." One facet of being too self-contained was that it had its own user interface paradigm, which was different from the operating systems it ran on. In other words the product decisions that would've made sense in an IDE or maybe a CAD system were bad product management decisions for a groupware product. Notes also had its own self-contained application development language and runtime. That is reminiscent of 4GLs. Remember 4GLs?
Maybe there is a parallel reality where groupware is as important as web browsers, but not in this universe.
That just feels like an extension of how things used to be done back then, especially on DOS. Making a recipe app? A bookkeeping app? A paint program? Well, you start by making a UI library first, and the product stuff got done eventually.
Then there was a transitionary period where common UIs were available, but not that great and individual shops could still easily create better experiences on their own. See eg Winamp. But eventually shared UI stacks got better and doing your own thing became a bad experience, see eg the Java UI libraries.
I don’t know about this. If you were doing a recipe app on DOS likely you were using dBase or a clone of it and all those apps looked the same because of the character based limitations of the PC. Borland environments were similar.
I worked on both Lotus Notes and Groove. What's great about Ray is that he has the capacity and drive to be involved in every part of the project. He drove high-level business requirements and wrote code and also cared about icons and colors. But he did it all without arrogance and allowed his team to argue back when necessary.
In case anyone is interested, a while back I wrote about another Ray Ozzie project: Live Mesh: https://gridwhale.medium.com/live-mesh-and-the-future-of-com...
I still miss Groove.