Finished my first FXHash piece with JSCL

[aerique]

Hi guys,

I just published my first piece on FXHash made with JSCL: https://www.fxhash.xyz/generative/10665

It's a progression on the example project that I finished earlier this week: https://gitlab.com/aerique/fxhash-jscl-example#fxhash-example-project-for-common-lisp (which output is more-or-less the same except more basic, more random and just a single layer).

It's still a simple project but nice to have something up to refer to and continue from.

Given the disclaimers that I read when I started playing around with JSCL, I was surprised how well it worked and how much of CL is actually supported. So thanks a lot! And I hope to be able to contribute to the project as well.

The limitations I ran into while working on this.

• distinguishing floats (1.0) from integers (1), a known JS problem and something JSCL can probably do nothing about
• ~X support for FORMAT, fixed by just dropping down to JS
• have to add a compile-application entry for my source file to jscl:bootstrap and having to rebootstrap for every change (to be honest: I didn't really dive into fixing this)

I was able to compile the bootstrapped jscl.lisp with the Google Closure compiler using the SIMPLE setting, although I have no idea whether it improved things ;-)

[mmontone]

have to add a compile-application entry for my source file to jscl:bootstrap and having to rebootstrap for every change (to be honest: I didn't really dive into fixing this)

I don't do it like that. Instead, call compile-application from the outside, that generates lets' say an app.js file. Then you include that app.js in your html, together with jscl.js. No need to bootstrap jscl on every change.

Also, I'm programming JSCL live from Emacs via websockets, using some new tools I'm working on.

[aerique]

Hi all, it's been a while ;-)

I'm now doing it like mentioned here: https://github.com/jscl-project/jscl/wiki/JSCL-HOW-TO#how-to-compile-my-lisp-file

Which makes my build process already a little more cleaner but I still need to call (bootstrap). What do you do to skip the bootstrap phase once you've done it initially?

It's no real biggy. It shaves a few seconds off my build.

edit: I just realized I can just change my build process. Instead of having entr running on the CLI and checking for changed files I can keep SBCL open with a (bootstrap) already done and just do the compile-application part. I just need to monitor for changed files inside SBCL

[aerique]

(defun hall-monitor (out-js &rest files)
  (loop with write-dates = (make-hash-table :test #'equal)
        for compile = (loop with write-date-changed = nil
                            for f in files
                            for old-write-date = (gethash f write-dates)
                            for new-write-date = (file-write-date f)
                            do (when (or (null old-write-date)
                                         (/= new-write-date old-write-date))
                                 (setf write-date-changed t
                                       (gethash f write-dates) new-write-date))
                            finally (return write-date-changed))
        do (when compile
             (format t "--- ~A ---~%" (get-universal-time))
             (compile-application files out-js))
           (sleep 1)))

😃

[aerique]

I said "no biggie" earlier but I'm always surprised how big a difference removing even a small hurdle can have.

Same reason companies thrive on making unsubscribing harder or the big tech walled gardens make moving away harder.

[davazp]

Fantastic!

It would be really nice to build a compile-application function in JSCL itself.

We could have an option for bundle it together or have a separate jscl.js / app.js and some other options. But exposing a single way to build apps would be nice.

Another idea I had was to , compile each .lisp file to a single .js and use ES6 modules. That could make possible to tree-shake things if for example you don't need the full compiler in the image.
But we'd need a way to specify those dependencies in JSCL source code itself too.

[mmontone]

Fantastic!

It would be really nice to build a compile-application function in JSCL itself.

We could have an option for bundle it together or have a separate jscl.js / app.js and some other options. But exposing a single way to build apps would be nice.

This is working nicely for me: #443 (comment) . Perhaps some variation of that.