Look up Vatican land holdings across Europe, Africa and Asia.

But then, the opposition to my comment is based on religious ideology and not merit.

Comments URL: https://news.ycombinator.com/item?id=48207428

Points: 1

# Comments: 0

And I saw these malicious (pre-commit) git hooks installed by GitButler, without any confirmation, or prompt seeking my approval.

I'm sure you folks will come up with a "technical explanation" or some "legal-marketing language" to cover up for this — but in my book — redirect `git commit` to `but commit` is dishonest and unethical.

* pre-commit — The malicious one. It intercepted every `git commit` attempt and aborted it with that error message, forcing you to use `but commit` instead. Effectively a commit hijack — no way to commit to your own repo without their tool.

* post-checkout — Fired whenever you switched branches. GitButler used it to track your branch state and sync its virtual branch model. It cleaned this one up itself when we checked out.

* There's also typically a prepare-commit-msg hook that GitButler installs to inject its metadata into commit messages, though we didn't hit that one.

* The pre-commit hook is the aggressive one — it's a standard git hook location, so git runs it unconditionally before every commit. GitButler installs it silently as part of "setting up" a repo, with no opt-in. The only escape (without their CLI) is exactly what we did: delete it manually.

Oh, and, tomorrow, the first version of visualization of Explain will be shipped as well. :)

I still need to figure out correct packaging on OS's I don't use (Fedora RPM for example).

By end of this week, I'll incorporate some of your feedback into the roadmap. Ty.

Quick poll — Are you macOS or GNOME?

Yes. It depends what you compare it with.

> "I have never really seen this as an issue except when opening a new project and even then it’s small notifications."

Tend to agree with you — but I still find it unacceptable to receive notification "ads" for upsells or plugins in a devtool.

I prefer zero-distractions in devtools, and this was the case mostly for a very long time.

> "This is probably true but JetBrains is not totally unusable offline."

Good point.

Not dismissing JetBrains — I was a happy paying customer for over a decade. :)

They're struggling to keep up with a rapidly evolving devtools market.

Thankfully, I / Tusk has no commercial obligations — so I can make it exactly to my liking and taste.