mastodon 4.7.3Software Engineer @ Posit working on Open Source & AI. Maths. Physics. I like making things.
I've been working on this over the last few months and in my opinion it is just beyond cool. Grammar of graphics for SQL users!
You can play with interactive examples at ggsql.org, and get up and running by installing ggsql and its Positron extension. We've focused on working with the duckdb SQL engine to start with, so it's super easy to visualise data from CSV, parquet, and other files without having to start a R or Python session!
I'm really proud of our work so far, please give it a go!
Yesterday we announced the alpha release of #ggsql 🎉 In celebration, here is a ggsql plot for #TidyTuesday Week 16 of 2026, using a dataset on global health spending! 💰
ggsql source: https://gist.github.com/georgestagg/0fac879ad994220cc164a22b668f040f
More about ggsql at: https://ggsql.org
webR 0.5.4 has been released! Some new updates include sharing URLs for the webR app, filesystem support for JupyterLite 0.6, and an upgrade to the Emscripten runtime. Read all about it in my latest post on the tidyverse blog: https://www.tidyverse.org/blog/2025/07/webr-0-5-4/
PSA for anyone starting to use #wasm #webR to share R code snippets: We have a new short URL for the webR app: https://webr.sh!
Thanks to some joint work with @jeroenooms@fosstodon.org the latest dev build of webR now supports the {curl} package, along with many other packages that rely on it! 🎉
If you're able and willing to use a WebSocket SOCKS proxy (outside of the browser), you can now use {curl} to make HTTPS requests in webR.
Here's an example using an R package that relies on {httr2} to query a Hacker News API: https://webr.r-wasm.org/latest/#code=eJydUctKxDAUBZf9ijAITbC2PsbNYEFdC8qIoIiUTHvbqaZJyc08uvYL%2FAd3%2FoF7%2F8sk7TCjS3fpueece%2B7p%2B9uH5A183ktTGwHFcTz9aLmZfyVz1UCyglm2QNDJ7rzghn%2FvvdUSDRcibnn%2ByitAmtPR3L5hKmGFo4iMqqoVypy45wsqKWoDI8YCUc801x3dkrfYIGFBcNdhjGBALunl9XV2O715eExDVPkrns0nSWIAzaRTQl2sMNaHC1kvQSPEBSwn4%2FFpaC1mlpKhUboGJOeHpAKT7WK04evMhmowPT5iQVE6krsuLrUthQaE%2BKtJSpC3rejorjoi5ULmplZyC3eMbN%2F7Xswia4O50v%2B28WIW2IOKsvd0OUue2yndQBERsASB6QZ4UroAP%2B%2F1z%2BxXH5nr2ZfiG7e8iHBbydqmHAw7F9hprTefgUh7I0YO7EUVqCbLlaA7n541ALmy%2B7NS1O2GUXlbGl7ZFGRIEfaztVXS8M5d2y8f8K7H3dq%2F%2F9Pn%2FwGX6PLO&a
@djnavarro@hachyderm.io Whenever floating point reproducibility comes up there are always two types of comment: “IEEE 754 floating point is deterministic and this is a solved problem” and “floating point is inherently inexact and consistency is impossible”. And the statements are made with such strong belief from both sides! Of course with differing BLAS, compiler and libraries the truth is somewhere in the middle, but the subtleties are hidden until you dive into the weeds and actually try it.
@ryanmcshane@fosstodon.org @jonthegeek@fosstodon.org The R Langauge Definition manual calls this a “tagged” argument, but I’d probably just say something like “parameter assignment”. https://cran.r-project.org/doc/manuals/r-release/R-lang.html#Function-calls-_0028expressions_0029