It's 2026 and I am still in the middle of porting our notes databases to web. Notes is still the main platform for our applications, we have around 50 or so. I have a lot of respect for what notes is and what it enabled developers to do and I try to bring some ideas of it to the platform I am building. Funny enough today is exactly the day I did the initial commit on the new project one year ago. Happy birthday to my…
That's crazy. I did a Notes migration to a custom Java/Red Hat platform 20 years ago, even at that time it was like "can't believe these guys are on Lotus Notes". I remember Howard Stern used to reference LN on his radio show in the early 90s.
Lotus Notes and the dangers of starting from scratch
61–70 of 122 posts
Re: Lotus Notes and the dangers of starting from scratch
#62So... PLATO user, Notes user and Thunderbird user here with a couple of notes. a. Everything you think is new was created in the 1960s by Don Bitzer @ UIUC or Doug Engelbart @ SRI. (and probably also Robert Creasy @ IBM.) b. Lotus Notes (and Groove) were products, not protocols. If you wanted to use them, you used Windows and the server and client from the vendor. c. Lotus Notes only sort of worked over the intarwebs…
view -> message body as -> plain text :)
Re: Lotus Notes and the dangers of starting from scratch
#63We had our "email blast" code in the founder of the companies mail database. When we launched new features or had various announcements, you would log on to Mark's email database and run those features in the drop down. Of course there were various permissions in check that only certain people could do (or view) certain things in the database, but that's where it ended up...
I always thought the data/design replication was cool as well. I had to bake in what I called "relational fields" into the documents to be able to perform some standard relational database type of work, but it was really easy to work with overall. Maybe too easy - as one person mentioned in the thread, there were hundreds of little custom apps built by anyone/everyone in the company, because it was just that easy.
Re: Lotus Notes and the dangers of starting from scratch
#64Re: Lotus Notes and the dangers of starting from scratch
#65Yeah, Notes had its shared database features, and you could see remnants of IBMers using them at the time, but most such applications been ported to Java CRUD apps. Also Lotus Sametime (it's like Slack) became a much more important collaboration tool.
Re: Lotus Notes and the dangers of starting from scratch
#66Earlier quoted context omitted.
Sure, but Notes was built for a world where ccMail, MS Mail, and GroupWise were the main workgroup email systems. Notes followed a similar pattern, with a proprietary "post office" system with optional gateways to larger x.400 / SMTP / UUCP / OfficeVision networks for those who needed them. Going SMTP (or even x.400)-native from the start might have been a better choice in the long run, but that's only clear in retro…
Exchange is funny because it's X.400 native internally, even if recently they dropped external X.400 support
It's hard now to appreciate how different corporate IT was from the free-wheeling Internet world. The unexpected popularity of the web really did change everything.
Re: Lotus Notes and the dangers of starting from scratch
#67There's exactly two people who LOVE Lotus Notes. One is the boss, cos he's never wrong, and the other is the Lotus Notes developer/integrator, cos he's getting money.
EVERYONE else in the org goes "Uggghghghhh, not Lotus Notes!"
Re: Lotus Notes and the dangers of starting from scratch
#68In the 90’s I worked for a large retailer. Our centralized systems were on IBM mainframes, with some Unix servers for specialized work. We ran a small Unix server - really just a decent PC - in the stores. We had very low end machines running DOS-based terminal emulators for POS, etc. Senior management wanted a some kind of communication platform for store employees. Something that could handle shared, broadcast comm…
Re: Lotus Notes and the dangers of starting from scratch
#69Re: Lotus Notes and the dangers of starting from scratch
#70My first exposure to Lotus Notes was to work on a migration project that was moving from Notes to "Exchange WebStorage System" (WebDAV) - which was an aborted "go-nowhere" server/service which ended-up being replaced by SharePoint ("Teams Services") - which we had to also re-target mid-project. We faced a situation where we had about 4,000 custom Notes apps to migrate, a small team and an extremely limited time. (and…