> An aside, I had a Junior who would just load datasets into PowerBI to explore them for the first time, and that was actually a shockingly useful workflow.
What was shockingly useful in PowerBI compared to DuckDB?
It's only available for orgs, not for personal repositories, and when we tried to use it in my team the size of our OIDC claim meant something broke so we had to turn it back off again :P. So I didn't get much experience with it.
But it seems like it gives you a place in a queue, meaning you don't need to keep rebasing as earlier PRs get merged: you can see what the state of the main branch should be by the time your PR reaches the head of the queue and develop accordingly.
I agree. I'm seeing that trend as well (teams using Rust instead of Go, JS, Java). But only for teams that are very experienced and really passionate about programming languages and software engineering (typically most of us here on HN). I'm under the impression that the majority is sticking to the usual tools — Java, C#, Python, Go, JS/TS — and not ready to use Rust.
I also spent some time evaluating a lot of open fonts and I agree that most of them have flaws, especially when it comes to kerning. The exceptions are fonts that have been developed for and are used by very large organizations, such as Public Sans (US government), IBM Plex Sans, Source Sans (Abobe), etc. Then the quality is equivalent (or even better) than what you get from proprietary fonts.
What was shockingly useful in PowerBI compared to DuckDB?
reply