Nice, but it would have been better with more pictures to match the description IMO

It’s nice, but the previous version wasn’t actually that great compared to Parakeet for example.

We need better independent comparison to see how it performs against the latest Qwen3-ASR, and so on.

I can no longer take at face value the cherry picked comparisons of the companies showing off their new models.

For now, NVIDIA Parakeet v3 is the best for my use case, and runs very fast on my laptop or my phone.

There is https://huggingface.co/spaces/hf-audio/open_asr_leaderboard but it hasn't been updated for half a year.

I like Parakeet as well and use it via Handy on Mac. What app are you using on your phone?

Spokenly has it on Mac and iOS, in both cases for free when using parakeet

Yep, I think a watcher is better suited [0] to trigger on file changes.

I personally can't stand my git commit command to be slow or to fail.

[0]: such as https://github.com/watchexec/watchexec

I prefer to configure my IDE to apply precisely the same linting and formatting rules as used for commits and in CI. Save a file, see the results, nothing changes between save, commit, stage, push, PR, merge.

> I personally can't stand my git commit command to be slow or to fail.

I feel the same way but you can have hooks run on pre-push instead of pre-commit. This way you can freely make your commits in peace and then do your cleanup once afterwards, at push time.

> I personally can't stand my git commit (...) or to fail.

But that's the whole point of locally checking the code, no? Would you prefer to commit broken things, fix them and then rebase and squash each time?

To myself: sometimes I think the background process should be committing for me automatically each time a new working set exists, and I should only rebase and squash before pushing.

That’s reversing the flow of control, but might be workable!

jj already pretty much does that with the oplog. A consistent way of making new snapshots in the background would be nice though. (Currently you have to run a jj command — any jj command — to capture the working directory.)

I don't think you have to, you can run the integrated watcher, no?

You can configure watchman to do it. `fsmonitor.watchman.register-snapshot-trigger = true`

I don't recommend it, though, at least not on large repositories. Too much opportunity to collide with command-line jj write operations.

That website it gold!

I think this could be handled by an open rewrite rule [0], with the side effect that it could also fix it for you.

[0]: https://docs.openrewrite.org/recipes

I forgot about this. It should be a great tool for agents. Does anyone have experience or tips to share? Moderne's thought of it too: https://www.moderne.ai/product/moddy

When I connect my iPhone to my dock with an external screen, it mirror the phone screen to the display, which is nice.

But, the keyboard never activates in any field.

If you use that to charge your phone (so the external screen is off), you can’t talk to people since the phone really don’t want you to have a keyboard at all as long as your connected.

It’s more for safari on Mac OS

I've been using Safari on MacOS for at least 15 years and never run into this problem, either. I've never even heard of it before.

I've been seeing this from time to time since at least 2016. As others have noted, it's more likely to happen when you type quickly or immediately after pasting your search in the url bar.

What would you have done differently in retrospect?

What I would tell my younger self:

Only listen to your users and customers, ignore everyone else.

Don't hire an external CEO unless you're ready to leave. Hiring a CEO will not fix the loneliness of not having a co-founder.

Having haters is part of success. Accept it, and try to not let it get to you.

Don't partner with Red Hat. They are competitors even though they're not honest about it.

Not everyone hates you even though it may seem that way on hacker news and twitter. People actually appreciate your work and it will get better. Keep going.

Or maybe a CI runner service?

Yep, this seems to be the case whenever one types a bit too fast.