we have a repl 🙂

(or should)

i.e. it may depend on graalvm to build the server library, but maybe not to use it? i'll have to try

give it a shot when you have an extra moment 🙂

hey there @Damien O'Hara... quick update, hope your holiday was great

@Damien O'Hara elide architecture map just dropped 🙂

oh, also, you can now try out Elide with

npx run @elide-dev/elide@alpha

🙂 🚀

@suresh welcome 🙂 and happy new year! 😛arty-parrot:

@Damien O'Hara wdyt? guest VFS architecture

i think it will be very fast, given the flatbuffer backing and i'm anticipating using LZ4 for compression -- but i'm concerned that a custom binary-only format makes inspection difficult for devs

i like that it's a standard tarball but maybe, for example, it should also have a JSON file, so that it can easily be inspected?

@suresh if you're curious or want to provide feedback, let me know 🙂, about any topic

the steps at runtime, i'm thinking, are 1. if enabled in app configuration: a. load the tarball from JAR resources or file (it having been placed there by the Gradle plugin, or equivalent, modulo toolchain in use) b. look for magic # header, grab

crc32

and

compression

mode c. seek to beginning of

Tree

flatbuffer, load it into memory while decompressing, according to

compression

d. the

Tree

has the file tree and byte offsets for each file, which we have on hand now e. we load the data region as a

RandomAccessFile

, perhaps written to tmp f. the

Tree

and data region are used to build an in-memory JimFS filesystem, decompressing while we go g. at runtime, guest requests file via I/O: i. impl receives request, enforces security policies ii. allowed requests go to JimFS iii. JimFS serves it from memory in already-decompressed form tradeoff decisions proposed: • Init instead of runtime: load and decompress up-front so that file loading at runtime is instant, it's all already in memory • Emphasis on fast decompression: LZ4 won't save a ton of space, but it will also minimize impact on startup time to the greatest extent possible • Non-goal of pre-compressed browser assets: The assets subsystem already pre-compresses assets at build time, so it's a moot issue • Backed by well-tested code: After boot, JimFS kicks in which is well tested and performant (we don't have to deliver crazy runtime performance) • Streaming and copy-free: As much as possible, we shouldn't have to copy while initializing the runtime, which Flatbuffers and streaming compression deliver (for reference, this is the guest FS that will be used to load ESM, NPM, Python modules, etc).

sry let me put that in-thread

future optimizations: • do away with JimFS in favor of purely backing it with

RandomAccessFile

and a compressed flatbuffer • implementation that proxies to pure mmap or something, idk

@Adam Crane, @Sebastian Schuberth, welcome!

@Sebastian Schuberth just made the first contribution to Elide outside the core team. Huge moment! Thank you again! Lol

hey everybody, welcome to the new channel members @manoj s, @César, @ayodele, @Maryna Cherniavska, @S., @Szymon Kaczorowski 😄

sorry the channel has been quiet, because of the rains on the west coast of the U.S. i was flooded out but i'm back at my desk! we should have a contributors guide ready in the next 48 hrs or so.

the virtual filesystem for the JavaScript VM is nearly done -- landing with this release will be support for JS imports and

require

as well.

quick preview of the design for errors that surface in user code

errors: a comparison of js runtimes

very strange behavior from deno tbh

hey guys, wanted to announce that a few changes will be made this evening (Sun Jan 15th, 2023) • the

v3

repo will be renamed to "elide" (the previous "elide" repo has been archived, it was v1/v2, which are now old) • github discussions will get activated • gitter and a button for this slack channel added to README separately, a test version of the CLI is out which has the error support shown above, plus a bunch of other goodies under testing. release coming soon. you can try it by running the one-line installer:

curl -sSL --tlsv1.2 dl.elide.dev/cli/install.sh | bash -s -

hello friends of the Elide Project 🙂 I'm happy to announce that Elide finally has a website! 🥳 there is a short Getting Started guide along with (very thin) docs for using the Gradle plugin. More coming soon. Of course, the site itself is built with Elide. Read below for stats on the finished app. https://elide.dev