gomodest-template VS sci

Its too early for a roadmap. I have tried different approaches and rejected them: https://github.com/adnaan/gomodest-template, https://github.com/goliveview/examples. I want the library to be have a great UX, good for moderately complex apps while building tech which is maintainable(no new rendering layer engine). I could use some help brainstorming the approaches though.

Oh wow someone finally went ahead with the server rendered js in Go ! Looks great. I have been experimenting various ways to build web apps in Go: https://github.com/adnaan/gomodest-template. I have landed on pursuing one approach more deeply: server rendered html templates over websockets. Don’t have a lot of code right now but here are some examples: https://github.com/goliveview/examples.

Since early this year, I started working on https://gomodest-template.fly.dev/samples, https://github.com/adnaan/gomodest-template to experiment with various ways to build user interfaces in Go, html and a bit of javascript. Now, I have taken all the learnings from gomodest-template and started working on https://github.com/goliveview/ . Its super early work.

So I have been exploring server side rendered Go web apps using only sprinkles & spots of javascript: source: gomodest-template , live demo .

I have built an app template which uses Go html/template package to render html on the server. The app is enhanced using sprinkles of javascript(stimulusjs, svelte single file components) on the client, wherever needed.

1. template: https://github.com/adnaan/gomodest-template

gomodest-template

I've tried researching this myself and can't find too much. There's this project metaes which is an mci for JS, and there's the SCI module of the Clojure babashka project, but that's about it. I also saw Triska's video on mci but it was pretty theoretical.

https://github.com/babashka/SCI if it's a requirement for proper sandboxing

Since cherry is a compiler, the code generally runs faster than with SCI which is an interpreter. For many cases SCI is fast enough, but numerical computations in a hot loop isn't one of its strenghts:

Startup and sustained performance are absolutely implementation issues. For example, SBCL will take its sweet time to make machine code out of Common Lisp, but CLISP will interpret and generate bytecode. Both are useful, and both implement the same language. Clojure on the JVM takes also takes plenty of time to start up, so some use an interpreter instead. Furthermore neither of these languages has a cost model, so the cost of anything is an implementation issue.

So far we have relied on an increasing number of home-grown integration points to our platform, where relevant combined with the excellent SCI (so we can write some Clojure-code when adhoc data conversions / calculations / tweaking is required).

Also take a look at SCI, https://github.com/babashka/sci/blob/master/doc/libsci.md

You probably want to take a look at sci if you are creating a DSL or want to use Clojure itself as your DSL.

Built with the lovely SCI library (https://github.com/babashka/sci) + GraalVM, probably the most useful GraalVM project I've seen in the wild so far.

Also, Babashka will probably always support more features than ClojureRS could ever, particularly the interop with the various Java classes/functions, as that'd be very hard to achieve in ClojureRS.