[dead]
LotusNotes
71–80 of 113 posts
Re: LotusNotes
#72My first dev job was a Notes developer. It really was an amazing piece of tech in hindsight. IMO their real folly was chasing the web trend; at its heart it was a groupware product, and they tried to make it be too many things to everybody. I spent most of my time trying to wrestle it into doing things it wasn't meant to do. It got me extremely proficient with LotusScript which led to other opportunities (Hello ASP!) but the whole thing is a shame. Had they stayed in their lane with the product, it might still be alive and widely used today.
Re: LotusNotes
#73Earlier quoted context omitted.
Cut my teeth in Lotus Notes development. The combination of forms, views, and agents with the Notes security model was really powerful. I look at products like Notion and Coda and see nothing but Notes forms and views and formulas everywhere. Ray Ozzie was way ahead of his time.
AirTable is a straight up Notes clone.
AirTable? Really? As a Lotus Notes Developer working internally at IBM, I can not see the resemblance.
Re: LotusNotes
#74> Admittedly, IBM buying a popular software product at great expense and running it into the ground is an old story. IBM (Rational (Pure (Atria))) ClearCase and IBM (Rational (Telelogic)) Synergy are two other casualties why I once showed a slide of the elephant cemetary from the Lion King in a Powerpoint presentation arguing why the company should switch to git.
They took the Computer Associates (CA) playbook and ran with it.
But IBM targeted companies that techies had heard of, while CA seemed to go after only enterprise software that ran in the backoffice.
Re: LotusNotes
#75I was a developer at Iris Associates--I worked on versions 2 through 4. For version 3 I stuck in an easter egg in the About box. A certain combination of keys would produce a Monty-Python-like cut-out of Ray Ozzie's head and the names of the developers would fly out of his mouth. [This was when the software world was young and innocent and developers were trusted far beyond what they probably should have been.] Lotus…
Lotus Notes as a thick client application was a dead end but the Domino server could have lived on as a back end database for web applications, if IBM had any vision. The core technology of a fast, secure NoSQL document database with multi-master replication actually worked really well (at least after they fixed the index corruption race condition bug that I found). But it had a weird stupid limit of (I think) 64GB p…
Look at the history of Lotus Notes ( https://en.wikipedia.org/wiki/HCL_Notes#History )Development began in 1984. 64MB was large back then, maybe 64GB total was seen, but multiples of 64GB?
I guess Lotus/IBM decided to stop upgrading Lotus Notes as computer limits were increased.
Obligatory Damien Katz Lotus Notes Formula Engine Rewrite (it is a great story but also shows the limits the original devs had to deal with; n.b. scroll down to read Ray Ozzie's comment): see https://web.archive.org/web/20050110035626/http://damienkatz...
Re: LotusNotes
#76The PLATO connection is the best part of this piece.
PLATO ran its own programming language - TUTOR - which was designed specifically for creating interactive lessons on the system in 1967.
It's one of the earliest examples of a domain-specific language shaped entirely by its platform. The system also had real-time chat, message boards, and multiplayer games running on shared terminals in the early 1970s — a decade before BBSs went mainstream.
Lotus Notes, email, Slack — the entire groupware lineage traces back to a university teaching system in Illinois.
Re: LotusNotes
#77When the Mac version came out, I was all over it. WordPerfect user at the time, but wird processing was king back then. It would freeze and crash and irritate me. But I loved using it. If anything, it made things interesting for us Mac users as our options to PC software were quite virtually nonexistent.
Re: LotusNotes
#78I have certification in Lotus Notes, I quite liked it.
Fairly simple to create an application but not being open source was a problem.
Re: LotusNotes
#79I'm building an app that is, in a way, a modern take on Lotus Notes ( https://github.com/superegodev/superego ), and I couldn't feel this more: > It is hard, today, to explain exactly what Lotus Notes was. Whenever I try to explain what it does to a non-tech person, I'm met with confused looks that make me quickly give up and mumble something like "It's for techies and data nerds". I think to myself "they're not my t…
One noted science fiction author, C.J. Cherryh, notes, “It is perfectly okay to write garbage --- as long as you edit brilliantly.”[1] --- for a while I've been wondering if this adage was applicable to Vibe-coding, and your methodology would seem to be a reasonable approach/response to get the benefits of this and to shield against the detriments, and to ensure that a human developer understands the code before comm…
> your methodology would seem to be a reasonable approach/response to get the benefits of this and to shield against the detriments
If you're referring to the sandboxing / isolation of each app, I agree. Plus, the user can change the app quite easily, so if when they spot a bug, they can tell the agent to fix it (and cross their fingers!).
> ensure that a human developer understands the code before committing
Just to clarify: for Superego's app there's no human developer oversight, though. At least for the ones the user self-creates. Obviously the user will check that the app they just made works, but they might not spot subtle bugs. I employ some strategies to _decrease the likelihood of bugs_ (I wrote a bit about it here https://pscanf.com/s/351/, if you're interested), but of course only formal verification would ensure there aren't any.
Re: LotusNotes
#80I have been waiting for someone to open source lotus notes, sadly the time is probably past.