Lotus Notes was underrated imo.
We used it as a combo Helpdesk ticketting, email, wiki/doc tool and it worked so well. It took 20 years for other tools to catch up and webapps still arent as functional.
Lotus Notes and the dangers of starting from scratch
11–20 of 122 posts
Re: Lotus Notes and the dangers of starting from scratch
#12I used Lotus Notes until 2022, in a British blue-chip company. Stopped because I left that company - I am almost certain they're still using it, because they weren't close to migrating off the last few use cases. It was universally hated because it felt so clunky and old-fashioned, but it was being used for ERP-type applications with a lot of business process logic that had developed over time. I found it interesting…
> that you could click through the interface and find a lot of capabilities that were vestigial
Lotus Notes allows you to right-click on a "document" and see absolutely all data attached to it, directly in the UI, including access permissions. This can be immensely useful, because not all data could be part of its UI representation.
The closest to this today would be inspecting the JSON data on your browser networking tab to view what your app exchanges with the server, but its much more clunky.
Re: Lotus Notes and the dangers of starting from scratch
#13I used Lotus Notes until 2022, in a British blue-chip company. Stopped because I left that company - I am almost certain they're still using it, because they weren't close to migrating off the last few use cases. It was universally hated because it felt so clunky and old-fashioned, but it was being used for ERP-type applications with a lot of business process logic that had developed over time. I found it interesting…
I was at a big European company that was also somehow still on Lotus Notes in 2015, for similar reasons. Moving back to Outlook after my 5 years there was a breath of fresh air.. for a time. I do have to say Microsoft has spent the last decade "upgrading" their product to be a similarly painful experience though.
> I do have to say Microsoft has spent the last decade "upgrading" their product to be a similarly painful experience though.
Why Microsoft continues to burn goodwill for native Outlook to keep pushing webview "new Outlook" which isn't feature complete is beyond me. Unless we're getting webview Excel, there's no point because you won't be running Office on any other OS anyway.
Re: Lotus Notes and the dangers of starting from scratch
#14I used Lotus Notes in the 00s and 10s and greatly preferred it to Outlook. The full featured one, not the OWA version. Yes, the UI was clunky, but it was quick. It was McMaster-Carr quick. The mail client was never a barrier between you and your emails. These days I miss Outlook, as the new web-based solution we replaced it with is even worse.
Just to add that nowadays once can use HCL Verse for web- or mobile app-based email access to their Lotus Notes email database. It's quite sleek and it works.
Re: Lotus Notes and the dangers of starting from scratch
#15As much as it was rough in places (debugging an object oriented LotusScript library, connecting to a web service or dealing with a locked out 64GB NSF), I had to admire the email client was fully built as a Notes database and you could see all the source code for yourself so internally Lotus at least believed in it. Having said that, once you're locked in (and I don't just mean email I mean the hundreds of custom app…
Our company has now migrated its Lotus applications to web applications written in Java, but it took us quite a few years.
Re: Lotus Notes and the dangers of starting from scratch
#16I'm confused. Where does this article say anything about starting from scratch? Is there a chunk of the story missing? It jumps straight from talking about PLATO Notes to referring to Lotus Notes. There is a "spoiler alert" in there about IBM acquiring Lotus for Notes, but it doesn't spoil anything in this story. Did IBM try to rewrite it from scratch or something? What's happening?
I had the same reaction. I was particularly interested in "the dangers of starting from scratch" and it just turned out to be a history of lotus notes. I stopped reading about 80% of the way through, so perhaps they addressed that towards the end - but the title should have been different then.
Re: Lotus Notes and the dangers of starting from scratch
#17I'm confused. Where does this article say anything about starting from scratch? Is there a chunk of the story missing? It jumps straight from talking about PLATO Notes to referring to Lotus Notes. There is a "spoiler alert" in there about IBM acquiring Lotus for Notes, but it doesn't spoil anything in this story. Did IBM try to rewrite it from scratch or something? What's happening?
I think they basically did (at one point, horrifyingly, there was a lotus notes based on Eclipse of all things), but yeah, article doesn’t mention it as far as I can see. Maybe they hit publish too early…
Re: Lotus Notes and the dangers of starting from scratch
#18Lotus is the best example of why you don't let IBM touch you.
Re: Lotus Notes and the dangers of starting from scratch
#19In all honesty, I don't think this "concern" is valid anymore. With AI, I firmly believe that if it needs to be done, you should do it. Look at Bun. It took 11 days for them to rewrite it into Rust from Zig and it was all done through AI.
Re: Lotus Notes and the dangers of starting from scratch
#20I worked for Ray Ozzie at Groove, and I still mourn what that could have become. It was, in many ways, a modern reimagining of Notes, but that meant it had the same problem: customers and users thought they were using a product, but they had actually bought a PLATFORM. It was a digital choose your own adventure, but people really wanted a better chat room.
Same thing with Google Wave, really.