<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<span style="white-space: pre-wrap">
</span><span style="white-space: pre-wrap">
</span>
<blockquote type="cite"
cite="mid:3639ca85-08b9-4a1d-a089-bd388fb7efb7@ronaldbarnes.ca">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">First three minutes of video art in
<a class="moz-txt-link-freetext" href="https://www.youtube.com/watch?v=d35SlRgVxT8">https://www.youtube.com/watch?v=d35SlRgVxT8</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
That's great - really high production values, writing, and even good
acting for a bunch o' nerds & geeks.
And, Deno is really exciting!
The video features Ryan Dahl of Node.js fame, explaining his new
product: Deono.
Node -> Deno -> Done
I like so, *so* many features he demonstrates.
Particularly interesting: compile your JS website into an executable
(for any platform) and deploy that single file (assuming assets are
separate?).
</pre>
</blockquote>
<p>Yes. It is "compiling executable", with emphasis on executable.
This emphasis hints at bundling as a different thing that may
expect to take in other stuff into resulting pack/out-thing.<br>
</p>
<p>FYI. Usage with packing into docker images (understanding so far,
running processes without random egress, i.e. proper
fire-walling):</p>
<p> - compile and put the whole thing into image</p>
<p> - without compile do all cache pulling at image building stage,
so that everything ends up in the image before going into
production<br>
</p>
<p> - bundling will be nice, letting you use their image with deno,
yet ensuring with single commands that all dependencies are in.<br>
</p>
<blockquote type="cite"
cite="mid:3639ca85-08b9-4a1d-a089-bd388fb7efb7@ronaldbarnes.ca">
<pre class="moz-quote-pre" wrap="">This is exciting and I love it.
Just wish I could keep up!
(From the video:)
Days since release of latest JS framework:
05 --> 00
</pre>
</blockquote>
</body>
</html>