I tried to quantify some of these smallness vs expressivity tradeoffs in visualization libraries here, with some interesting conclusions IMO: https://notascope.io
Hex | Full Stack Engineer - Visualization | Remote - US | https://hex.tech/
Hex is changing the way people work with data. Our platform makes analytics workflows more powerful, collaborative, and shareable. Hex solves key pain points with today's data and analytics tooling, and is loved by thousands of users all over the world for the beautiful UI, new superpowers, and boundless flexibility.
We are a tight-knit crew of engineers, designers, and data aficionados. Our roadmap is full of big ideas and little details, and we would love your help bringing them to life.
Hex has raised over $100m from great VCs and angels, giving us many years of runway and the ability to pay competitive salaries, offer great benefits, and provide meaningful equity.
We're looking to grow our team with a second full-time Visualization Engineer (in addition to me!) working on no-code tools for visualization. See https://hex.tech/careers/visualization-engineer/ for more details.
Hex is changing the way people work with data. Our platform makes analytics workflows more powerful, collaborative, and shareable. Hex solves key pain points with today's data and analytics tooling, and is loved by thousands of users all over the world for the beautiful UI, new superpowers, and boundless flexibility.
We are a tight-knit crew of engineers, designers, and data aficionados. Our roadmap is full of big ideas and little details, and we would love your help bringing them to life.
Hex has raised over $100m from great VCs and angels, giving us many years of runway and the ability to pay competitive salaries, offer great benefits, and provide meaningful equity.
We're looking to grow our team with a second full-time Visualization Engineer (in addition to me!) working on no-code tools for visualization. See https://hex.tech/careers/visualization-engineer/ for more details.
It's a good question! I think I'd look at this through the lens of the Cognitive Dimensions of Notations, specifically the dimensions of 'consistency' and 'viscosity' (i.e. is the same thing literally called `title` in one place in the API and `name` in another? how hard is it to change from using one component to another?) and/or 'closeness of mapping' (i.e. do domain experts call it `title` but it's `name` in the API?).
Our metrics would maybe capture some aspects of consistency/viscosity, because `title` and `name` would both count towards vocabulary size, and because the distance between specs would be higher if `title` routinely needs to be changed to `name` when iterating, but that's about it. I don't believe a metrics-based approach like ours can quantify much if any of 'closeness of mapping' because that mostly happens in people's heads, not in the source code itself :)
Do the positions of the teams in the squares mean anything? It might be nice to have the teams laid out with two on top (rotated 45 degrees) with the top two being the current point leaders?
That's a good idea, because no, currently only the node's border color indicates rank, not their position. I could get an even denser data-ink ratio with this...
Ehhhhh, I'm a Python guy, and I find all of the Python Shiny alternatives lacking. Shiny delivers an incredible amount of value per line of code. My experiments with Dash and Streamlit required a lot more boilerplate to get something running vs the R equivalent.
Plotly Express author here: yes, seems very similar! I approve! I've been toying with the idea of building what I had been calling "Vega Express" for a while, but now it looks like I don't need to ;)
