SwiftBar VS vscodium

https://github.com/swiftbar/SwiftBar - Powerful macOS menu bar customization tool

As many of you, I obsess over the current metrics of my TMHI modem. Opening the app to check it is too cumbersome. On MacOS there is a cool free utility that allows simple scripts to run in the menu called SwiftBar (get it here: https://github.com/swiftbar/SwiftBar )

SwiftBar: App to quickly create custom menu bar apps using any language you prefer

Yeah Carrot is definitely expensive. I’ve been looking for SwiftBar, an open source menu bar app that has lots of community plugins. There’s ones for weather too. And free.

Because my programming background is primarily for scientific purposes, I really had little experience with servers and backends. Until now, my only real experience was with my Coffee Counter web application that is hosted on Deta, a great service for beginners. This app (which is still running and I use everyday through a SwiftBar app in my Mac's menu bar) technically has a backend database, but it is relatively rudimentary and completely managed by Deta – a great option for getting started, but the constraints mean that I cannot get a deeper understanding of the technology. Thus, many of the features of Appwrite were completely novel to me.

How does it compare to Swiftbar[0]? Any reasons to use Xbar over SwiftBar given that the latter was built with a stack that is more "native" to Mac than Golang?

[0] https://github.com/swiftbar/SwiftBar

I was wondering about why SwiftBar existed when there was already BitBar, and a lot is explained in this thread on Github: https://github.com/swiftbar/SwiftBar/issues/95

TL;DR: BitBar stopped working well in Big Sur and the old code base was increasingly hard to update and build.

To be fair, there is vscodium[1] which is only a few letters off vscode:

https://vscodium.com/

Curious what you think of https://github.com/VSCodium/vscodium .

I'm not actually familiar with the issues that VSCode has but I seem to recall some key component was not OSS, but I forget the details there and maybe it has changed. I know it has telemetry and such, but AFAICT that can be disabled by some settings.

I recommend using a separate code editor and not the neocities one. Brackets and VSCodium (VSCode but separated from Microsoft) are pretty good ones https://brackets.io/ https://vscodium.com/

> 2. To test/debug CI jobs, use act.

I can't wait for this meme to die, or for act (or gitea's fork thereof) to catch up to the hype train. Then again, I guess this fantasy is being promoted by folks who are all "just use run: and that's it" because any moderately complex one <https://github.com/VSCodium/vscodium/blob/1.84.2.23314/.gith...> for sure fails with spectacularly illegible error messages under both act and gitea's fork

Technically it's not Free (libre) or Open Source. The "VSCode" that people use is a proprietary telemetry-laiden application that cannot be reproducibly built from available source. You're probably wanting: https://vscodium.com/

https://github.com/microsoft/vscode/issues/4490

It looks like there are a number of vscode extensions for recording macros:

- https://www.google.com/search?q=vscode+macro+recorder

- https://marketplace.visualstudio.com/search?term=Macro&targe...

- the macro-commander README explains its JSON-based macro language. YAML might be easier to maintain than JSON. https://github.com/jeff-hykin/macro-commander#what-are-some-...

For teams with multiple editors, you can specify workflow automation scripts with shell scripts or ci container/cmd YAML, and/or pre-commit.yml instead of with an IDE-specific tool.

Isn't there native real-time collaboration functionality in vscode/vscodium that would be useful for a native macro recording feature? (Edit) Live Share can't be installed in vscodium. https://github.com/VSCodium/vscodium/issues/128

Support for jupyter-collaboration Y.js CRDT could be added to vscode-jupyter and/or a more generic extension: "Support for real-time collaboration in the extension?" https://github.com/microsoft/vscode-jupyter/discussions/1293...

jupyterlab/jupyter-collaboration:

Becuase the repo uses github actions to pull changes and build the binary

https://github.com/VSCodium/vscodium/blob/master/.github/wor...

> Telemetry is disabled.

Er...

https://github.com/VSCodium/vscodium/blob/master/DOCS.md#dis...

> Even though we do not pass the telemetry build flags (and go out of our way to cripple the baked-in telemetry), Microsoft will still track usage by default.

There is a section in the docs regarding switching back to the official extension marketplace: https://github.com/VSCodium/vscodium/blob/master/DOCS.md#how...

So if there is a "killer extension" not available on codium's marketplace, you can still use it through microsoft's marketplace.