Hi, I made an interactive and visual blog post int...
# show-and-tell
d
Hi, I made an interactive and visual blog post introducing some actuarial terminology. This post uses calculang for calculations - but that's kinda spurious at this simplified level. It uses vega-lite to visualize the numbers and ObservableJS for interactivity, and I was very happy to dust off and apply a bit Gemini: a (json) grammer for animated transitions, which I used to introduce Reserves [Gemini Paper] It's quite simplified but I hope will serve as useful context for other - less simplified! actuarial models and materials I'll publish. Here it is and happy to hear any feedback or suggestions: https://calcwithdec.dev/posts/actuarial-terms-i/
❤️ 1
j
Interesting you use Quarto - I've found a lot of overlaps with Quarto and Observable, but for the sake of web-publishing finding Observable Framework to be better fit besides that - Quarto development speed has been pretty impressive, feels like it could be better suited for industries that using R based repos (biotech/pharma/finance potentially), seems like a bigger development team because of R / Posit. Also on Gemini - do feel like this is the progression project after that https://vis.csail.mit.edu/pubs/animated-vega-lite/ "Animated-Vega"
d
Hey Jung - I actually develop in Framework, but my blog is Quarto so to release I migrate over to Quarto. Quarto integrates the ObservableJS runtime so the code can stay in reactive form and quite consistent, but it's still annoying to migrate, and I hope one day to switch my blog to Framework (I'd find it hard to reproduce Quarto quality output for the entire site, rss feed, etc. atm - but I hope we'll see more of this with Framework!) I don't use any of the Python/R features and I sometimes feel like I'm the only Quarto user like this, but output quality of Quarto is very high. It looks like Gemini came before Animated Vega Lite 🙂 I saw some PRs to add animated VL upstream recently and really look forward to playing with it! But there is a difference versus gemini: gemini is it's own grammar to define animated transitions between 2 visualizations. Sadly, the code that was built went a bit stale and it isn't maintained (I did a bit of hacking for my specific needs though) Some examples of gemini animated transitions if interested: changing a barchart (only works in one direction atm): https://observablehq.com/d/37da3cd777ecce02?collection=@declann/gemini Stepping to bouncing ball logic, something I'll use for a little tutorial for calculang: https://observablehq.com/@declann/gemini-calculang-bouncing-ball?collection=@declann/gemini But if interested, the gemini paper is very good: https://idl.uw.edu/papers/gemini I like a lot declarative development approach - I actually needed to do too much work to make the transitions above, but now they are patterns I can develop to help with a lot of problems. (d3 works for a lot of people here, but I think geminis abstrations are also useful! e.g. the gemini grammar is easy to manipulate, and the transition I used in the blog evolved to be far different/more elaborate than what I initially drew - so easy manipulation was very helpful)