Good videos, with context.
Lucid Energize Demo VHS 1993

Lucid Energize Demo VHS 1993

Zach Beane
0 HN recommenders · discussed 2016–2026
Open YouTube ↗

About this video

A 1993 VHS demo of Lucid Energize, a database-backed, incremental C/C++ programming environment built on XEmacs. It shows features like incremental compilation, live debugging and hyperlinked output.

Why it appears in the archive

HN cites it constantly as evidence that modern IDE and LSP-style features existed in the early 90s.

AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.

From the Hacker News discussion

pjmlp · 2016-01 · reference

I also only toyed with Ada. My real work experience with Algol like languages are Turbo Pascal, Delphi and Oberon. Although thanks to my interest into compiler development during my CS degree, I also do have some knowledge of almost all major Wirth influenced languages. Personally, I do prefer some verbosity to lines full of symbols. Ada 2012 is quite good. It is also remarkable that in the 80's Ada 83 as seen as almost impossible to implement and nowadays C++ is way complexer to implement than Ada 2012. Another anecdote, Rational started out in mid-80's as a startup doing Ada workstations[1] (think Ada machines), with IDE capabilities that probably only Lucid C++ had in the 90's [2]. [1] [LINK] [1] [LINK] [2] [VIDEO]

Read original comment ↗
pjmlp · 2016-05 · reference

Interactive programming is very developer friendly workflow, something that was already possible at Xerox PARC in their Smalltalk, Interlisp-D and Mesa/CEDAR environments. Actually there was an early attempt to provide C++ repls back in the early 90's with Lucid Energize C++, after they pivoted from Lisp Machines and applied their knowledge to C++. [VIDEO] Also the majority of CERN code is written in a mix of Fortran and C++, and not all teams like to use Python. So they rather use something that provides interactivity to research their algorithms and speed at the same time.

Read original comment ↗
pjmlp · 2016-05 · reference

Like Lucid Energize C++ in 1993 ? [VIDEO] Or C++ Builder or C Set++ for OS/2 (might have the name wrong). If it wasn't for tool vendors having switched their focus from C++ to Java and .NET, until LLVM and clang got created showing everyone what was wrong with their approaches, C++ IDEs might have been much more advanced already, in spite of technical issues with language.

Read original comment ↗
pjmlp · 2016-10 · reference

The point being that we have seen the future like Bret puts it, and are to certain extent disappointed that the industry keeps doing left turns. Many C++ users are finally enjoying environments like Clion and incremental compilers, well this was a C++ environment in 1993: [VIDEO] Built on top of Lucid Common Lisp infrastructure, as Lucid pivoted their business to C++. IBM had a similar one, that imported C++ into a database, offering a Smalltalk like development experience for C++, called VisualAge C++ Professional 4.0 [LINK] So yeah, we are grey hair dogs disappointed how things evolve.

Read original comment ↗
pjmlp · 2017-11 · reference

It existed, but sadly both were too early for the market. The first one was from Lucid, after pivoting away from Lisp Machines. [LINK] Here is a demo on YouTube. [VIDEO] IBM also tried to create a Smalltalk style repository in Visual Age for C++ v4.0, which has quite resource hungry for mid-90's PCs. So we had to wait until the idea of compiler as library to catch on, to get those ideas back.

Read original comment ↗
pjmlp · 2018-04 · reference

Here is how Lucid implemented their C++ knowledge repository for Energize C++. "Foundation for a C++ Programming Environment", chapter 7, Protocols [LINK] And how it looked like with their Emacs customization in 1993 on UNIX. [VIDEO]

Read original comment ↗
pjmlp · 2020-02 · reference

It would look like Lucid Energize for C++, here a 1993 sales demo: [VIDEO] Or the version 4 of IBM's Visual Age for C++ Visual Age for C++ was quite impressive, the whole program was serialized into a database, an approach similar to Energize, and you could edit C++ code just like in a Smalltalk environment. Sadly not much of it has survived, so save pages like this while they exist [LINK] The problem with those two products was that they were ahead of their time, so with their hardware requirements, ended up being a commercial failure. Then for something more down to earth, there is C++ Builder, the only actual C++ RAD tooling, but their market is only deep pocket corporations. Think VB experience, but using C++ instead. [LINK] Finally there is VC++, which also supports edit-and-continue with incremental compilation and linking, and with C++/CX I thought it could eventually be like C++ Builder but was wrong. Also with the C++/WinRT reboot, the tooling is still playing catch up with C++/CX. However there is also the option to use interpreters like Cling. Then you also have the development experience of Common Lisp, Dylan and Eiffel. All of those have rich IDEs, with interpreter/JIT compilers for development, and then you can also AOT optimize for release builds. Eiffel to this day uses their JIT (oder MELT as they call it) for rapid development, and then relies on a C or C++ compiler for the release builds. Dylan while killed by Apple, had a short commercial life, and you can

Read original comment ↗
sedachv · 2020-03 · reference

Compare Symbolics Genera to a Free Software Common Lisp development environment today (SBCL and SLIME on GNU Emacs). The latter does a lot less and is more bloated. Commercial Common Lisp compilers like Allegro and LispWorks have features and optimizations that Free Software compilers lack (Allegro has really good debugging tools and garbage collection, LispWorks has excellent support for concurrent programming). Intel Fortran compiler and their C++ compiler produce the fastest code. Lucid Energize and IBM VisualAge C++ did incremental compilation and had IDE features not available with Free Software C++ compilers and editors/debuggers. [VIDEO] [LINK]

Read original comment ↗