Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ClojureScript from First Principles [video]

youtube.com

Post reply on HN
Print view View original

1–10 of 31 posts

Re: ClojureScript from First Principles [video]

#3

Post by tekacs »

I was in the audience, asking the question at the end of the video!

I didn't quite get the question across and got an answer to a different question, so to re-state my actual question (that I asked David later), I was curious how heavy a lift it would be to preserve enough information in production ClojureScript compilation to allow re-hydrating. The aim being to re-hydrate enough in production that e.g. in the event of issues or errors, you might attach a REPL to that production build and poke at it.

The answer (which I mostly knew/expected) is... quite a heavy lift. I can imagine some possible solutions, but I'm mostly-Rust nowadays, so no solution from me soon. :)

I also really recommend the other [1] talks [2] from this event!

[1]: https://youtu.be/8K4IdE89IRA (Aaron, on using lenses, this sorta stuff [3])

[2]: https://youtu.be/fcSJAuUGVs8 (Ben, on a core.async error handling strategy that I had totally missed and totally changes the ergonomics of using c.a!)

[3]: https://github.com/tekacs/factor/blob/master/src/factor/lens...

Re: ClojureScript from First Principles [video]

#4

Post by chamomeal »

This is such a good intro to clojurescript in general. I’ve dabbled in clojure for a few months, and CLJS seems really cool but also really confusing to get into. It’s got a whole ecosystem to itself.

Now I’m SUPER excited to try cljs!! It’s crazy how modern it is despite being kinda old in webdev terms

Re: ClojureScript from First Principles [video]

#5

Post by billfruit »

tekacs wrote: post #3

I was in the audience, asking the question at the end of the video! I didn't quite get the question across and got an answer to a different question, so to re-state my actual question (that I asked David later), I was curious how heavy a lift it would be to preserve enough information in production ClojureScript compilation to allow re-hydrating. The aim being to re-hydrate enough in production that e.g. in the event…

What do you mean by re-hydrate?

Re: ClojureScript from First Principles [video]

#6

Post by geokon »

billfruit wrote: post #5
tekacs wrote: post #3

I was in the audience, asking the question at the end of the video! I didn't quite get the question across and got an answer to a different question, so to re-state my actual question (that I asked David later), I was curious how heavy a lift it would be to preserve enough information in production ClojureScript compilation to allow re-hydrating. The aim being to re-hydrate enough in production that e.g. in the event…

What do you mean by re-hydrate?

https://en.wikipedia.org/wiki/Hydration_(web_development)

Re: ClojureScript from First Principles [video]

#8

Post by amadeuspagel »

The way he shows off his REPL in VS code that controls the browser just reminds me how absurd this workflow of constantly switching between the browser and the IDE is, and it's even more absurd since VS code is an electron app, so you're really switching between chrome and chrome.

Re: ClojureScript from First Principles [video]

#9

Post by fud101 »

amadeuspagel wrote: post #8

The way he shows off his REPL in VS code that controls the browser just reminds me how absurd this workflow of constantly switching between the browser and the IDE is, and it's even more absurd since VS code is an electron app, so you're really switching between chrome and chrome.

Right? I'm waiting for that vscode with a browser built in to making crud apps a bit easier. Not yet another stochastic parrot which adds nothing to the heap.

Re: ClojureScript from First Principles [video]

#10

Post by ethan_smith »

tekacs wrote: post #3

I was in the audience, asking the question at the end of the video! I didn't quite get the question across and got an answer to a different question, so to re-state my actual question (that I asked David later), I was curious how heavy a lift it would be to preserve enough information in production ClojureScript compilation to allow re-hydrating. The aim being to re-hydrate enough in production that e.g. in the event…

Shadow-cljs offers partial solutions to this with its runtime code reloading capabilities and source-maps in production, though true REPL attachment to production builds remains challenging due to the optimization/debug information tradeoff.
Post reply on HN