what's advocated in that article doesn't exist for mercury either :p
though I wonder if something like that could be achieved with the use of virtual-dom, in the same sort of way that client-side JS can take over a server-side rendered page
I don't know if I quite get the benefit of fp-dom
@eightyeight I don't know either. I tried but then went back to using virtual-hyperscript
the clojurescript people have a nice dsl for html
my goal is to not have a DSL, but to have HTML with the minimal additions necessary for control flow
I need to work with a designer and it's a better workflow for us to stay in HTML as much as possible
anyway, I'll work something out :)
@eightyeight "minimal additions" == dsl
virtual-hyperscript is a kind of dsl too imho
and the one the clojurescript people use is even easier
i am having this constant issue that some elements are reused
instead of replaced
have you tried using key?
hyperscript is definitely a DSL. I meant that I was looking for something mostly HTML rather than something completely different. Even Vue's templates, which are implemented in entirely HTML syntax, are a form of DSL - I guess the difference is it's embedded in HTML rather than in JS
@chrisinajar Can you point me to some documentation about the key ? Is it just a specific property used by the virtualdom ? We can simply set it in virtual hyperscript props then ?
Just found out about mercury and it looks cool. But I don't necessarily want to jump in if it is dead
it's being used, but the repo isn't too active
FWIW on the one large project I've used it on, we found the codebase was so small and sensible that it was pretty easy to manage even without support or development from others
especially because so much of it is just virtual-dom, which is not dead
@evanhackett afaik I know Raynos considers mercury a finished product that is done in the sense that it doesn't really worth building anything on the core. I think that the best way to think about mercury is an example microframework that you can just use as a template. You can add whatever other module you want and replace the things that you don't want. I for example replaced for a project this year all observe-* functions with datascript and added js-csp to it so I can handle all data flow nicely. It became a way more robust and scalable system than mercury is in its current form.