Ask HN: Does the Easel programming language still exist?
Does the Easel programming language still exist and is it supported? I’m just curious, because I worked with it in 1994 at Sears. The last I’ve heard very few people supported it at the company that owned it.
It was event driven but not object oriented. By that I mean, code was executed based on responses from a control like a push button or when text was entered in a text area. You would have click responses to a button that would execute code written for that button. That’s why it was considered event driven. It wasn’t object oriented because it didn’t have classes. We used it for a marketing system at Sears for many years and I was wondering if the language still existed.
30 comments
[ 2.5 ms ] story [ 78.2 ms ] threadMe: young, new to the professional world, making my way around a new environment at Sears in 1994. You: an shy but engaging language, event driven, with a style that was new and exciting for that time and place. It's been a long time but I still think about you whenever I write addEventListener. Would love to reconnect, even if only to share some memories of that time.
https://news.ycombinator.com/item?id=16631346 (March 2018)
https://news.ycombinator.com/item?id=9362115 (April 2015)
https://news.ycombinator.com/item?id=7030798 (Jan 2014)
The 2018 comment links to https://www.eslsyndetic.com/Documentation/overview_of_respon....
From there I got to https://web.archive.org/web/20030220213927/http://www.eslsyn..., which makes it clear that Easel was renamed ESL and https://www.eslsyndetic.com is indeed its current incarnation. I guess that means it still exists.
And it looks very dated -- old-style MDI interface and controls, System font everywhere, bare-bones interface... the discussion of "5250 and 3270 host sessions" doesn't exactly speak to its modernity either.
They may still be putting out builds.
Hopefully some current Easel devs chime in. I took a look at the docs, it has an interesting approach to userinterface event handling and there seems to be some special "Screen Scraping" facilities.
Maybe it's just me because I am used to that interface, but it looks much more user-friendly than many of the modern apps I use:
1. I can tell at a glance what is clickable and what is not.
2. I can see the accelerator/shortcut keys for most of the elements.
3. Sections are grouped together, and on a single page. I don't have to click 'Next' to see the next three clickable widgets.
> ESL is the world's most comprehensive development tool for easily connecting all of your current and legacy systems and presenting your users with an integrated and easy to use windows program.
> The latest versions of ESL are available to all of our customers with a support contract and are also available for a 30 day evaluation.
I still prefer code formatting to only be used for code snippets, commands and command outputs though.
For quotes I like leading each quoted paragraph with a “>” sign and a space. Like we do in plain text emails. Same kind of thing that they talk about in http://catb.org/jargon/html/email-style.html
Same, when I saw it on a PC. Originally I saw it on a mobile app‡, which still uses horizontal scrolls - hence my comment.
‡ https://f-droid.org/bo/packages/nl.viter.glider/
The best part of working at Sears was 92 was in the Sears Tower, and somehow noob me got a window office on the 46th floor overlooking Lake Michigan. On a clear day I could see the MI shores on the other side. It also gave me a lifelong aversion to working for big companies - too slow, too out of date.
Then into the early 2000s at FirstUSA/BankOne/Chase, where it powered their card services CRM system. This application had a metric ton of business logic, and tied together DB2, 3270 scraping via custom C executable, ImagePlus for viewing customer letters and correspondence history (also brokered via custom C executable), and a few other systems. We eventually replaced with with a C++/MFC application on Windows backed by CORBA services in a massive port effort. For a very long time the new application was a much worse experience than the original.
Easel was commonly used in OS/2 financial shops (both of the above fit that category) with heavy mainframe integration. I would have to assume there are /some/ legacy users still kicking around, but the last I knew of were a few Boston-area companies phasing it out also in the early 2000s. Around that time, consultancy rates for the language started to go way up as domain expertise was pretty rare.
Easel's 'block' style (I don't remember exactly what it was called) for accepting input from external systems was the first time I ran into anything like the pattern matching I next saw in Erlang. I enjoyed working with Easel - it presented a reasonable abstraction for GUI creation and interaction, was easy to integrate, and the event model made a lot of sense.
It was also obtuse and sometimes painful to use, but no more so than any other language (then or now).
I started doing a little digging when I saw this article, and came across this in Jeff Sutherland's "The Scrum Handbook" [1]
And [1] https://www.researchgate.net/publication/301685699_Jeff_Suth...