You can also disable them.

Also, when the feature is enabled in Supercharge, I cannot even quit the settings of your other menu bar apps like Text Lens or Color Picker from the red traffic light. Clicking it just does nothing. If I disable it, it works fine.

Thanks. Makes sense I guess. BTW it's not just Bitwarden, it's pretty much every app in menu bar. Like if you open preferences of an app and close it, it will quit the app. I've this with Rocket, Laravel Herd, Amazon Q. I guess I can exclude them all.

The new quit an app when closing its last window algorithm seems to be closing menu bar apps too. I can reliably reproduce this with bitwarden. If I close it from traffic lights, it closes the menu bar app too.

Don't think so. Likely the nearest matching one.

It's already there? 👀

Run `npm pack` and then install the generated tarball in another project `npm add ../path/to.tgz`.

bsky.app/profile/cass...

Obviously it would be better if both perf and the pain points can be done in one go (which now I think was your point). But rather than someone porting mdit to native and fixing stuff, I would like something that's not mdit. Most of the things are not fixable without a full rewrite as a new tool.

And we still have to use mdit because the other alternatives aren't flexible enough to support extensions like vue in markdown.

Yeah most likely. But again, might be better to solve real pain points than chasing perf, like async renderer is not supported (a common issue for syntax highlighters), plugin dx is quite bad (at least for beginners), good ast isn't there (can't generate sourcemaps)...

Things have improved in the last 2 years. But time can be better spent to implement new features and tools instead of just porting something that works good.

Yeah I mean you'll need to pass the data (markdown, tokens, config, etc.) between JS (meta framework / plugin) and Rust. That kind of diminishes the gains which weren't too much in the first place.

There were attempts few years back, but it didn't really translate to better perf. I had tried integrating it in vitepress but the perf difference was negligible, mainly because mdit is already very fast and not really a bottleneck for most cases, that coupled with the serialization overhead. 🫠

Example - vuejs.org/guide/reusab...

By keep it reactive, I meant something like `computed(() => toValue(x))` and use to derive your returned object. Or maybe something like `watch(() => toValue(x), () => {...})`.

Not a syntax sugar. It's just a function that accepts ref and getters too. If your function accepts MaybeRefOrGetter, and you keep it reactive and return a reactive value, it will be automatically tracked by Vue. Async or not it doesn't matter.

Found it but not commenting, let others play. How were the first two emojis related to him though? 😅

Use some other client, like deck.blue for example.