HTML Platform

Erik Beugelaar e.beugelaar at
Wed May 6 04:17:28 EDT 2020

It would be great if a lesson comes available how to create streaming apps
with LC.

-----Original Message-----
From: use-livecode <use-livecode-bounces at> On Behalf Of
Richard Gaskin via use-livecode
Sent: woensdag 6 mei 2020 08:42
To: use-livecode at
Cc: Richard Gaskin <ambassador at>
Subject: Re: HTML Platform

Mark Wieder wrote:

On 5/5/20 4:47 PM, Trevor DeVore via use-livecode wrote:
 >> I don't use HTML deployment myself, but thought I would mention that  >>
there has been some emscripten activity in GitHub lately. Looks like  >>
WebAssembly (WASM) support is being added.
 > Yeah, I saw the github posts come flying by, and that's a promising  >
feature, but it doesn't address the limitations and broken features of  >
the current html implementation.

In my own mind I phrase that differently.  Whether it's gentler or more
stark is up to the reader, but for me it's more: can't address the fundamental differences between desktop
   and web architectures, and the limitations inherent in Emscripten.

Emscripten is good for what it was designed to do.  But look deeply at LC,
consider what Emscripten is, and the more time you spend pondering it the
clearer it becomes how difficult it is to put a desktop app's square peg
into a browser hole.

"Difficult" is maybe unfairly optimistic. And "impossible" never applies to
software. Perhaps "prohibitively expensive" is fair.

 > Also, it remains to be seen how much bloat this adds to deployed web
 > apps.

Putting an entire scripting engine and object model into a browser 
application that already has its own scripting engine and object model 
cannot achieve size, performance, and integration features as well as a 
web-native implementation.

If you truly need a browser as your only deployment option, it's kinda 
hard to argue against going with the grain of the browser.

But most apps that might make good candidates for LC's HTML export have 
characteristics that lend themselves very well to not doing HTML at all, 
instead using a one-time download of an LC standalone which then 
downloads and runs stack files (a practice that, in the absence of a 
more common label, I like to call "streaming apps").

Fits most of the same uses cases, but provides a more focused user 
experience that integrates with the OS as only a native app can.

Extra bonus points that they're cheap and easy to build in LC, fast 
cheaper to deliver sophisticated works than even web-native implementations.

For the sorts of vertical audiences where LC's HTML would seem 
interesting, I believe simply streaming stacks in a standalone is the 
most underappreciated and underutilized opportunity in our community.

MetaCard promoted the idea heavily with some nice example downloads, but 
in all these years only a few of us make streaming apps regularly.

If you're waiting for LC's HTML to get good, let's discuss streaming 
apps for those where they might be a great solution.  We really don't 
need to wait for anything to have the benefits of net-distributed apps. 
You can have it all today, with the LC you know and love already.

  Richard Gaskin
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  Ambassador at      

use-livecode mailing list
use-livecode at
Please visit this url to subscribe, unsubscribe and manage your subscription

More information about the use-livecode mailing list