Canonical could have done a lot better with the explanation message here. The idea is to push apps towards XDG compliance and the use of things like Portals.
That said, unlike Wayland, portals really aren’t there yet from a UX perspective, especially for an app that is heavy on file transfers.I prefer what Flathub does where it puts a nice green checker beside your app for XDG compliance - it’s an encouragement, but not an enforcement.
Tower is pretty nice for mac user too. I paid for it for a few versions back when I was coding full time. Now I just stuck to source tree for occasional freelance and personal projects.
Freaking love TUIs, it’s like they took the convenience of a GUI and the efficiency of the CLI and merged them. As a Neovim and Lazygit user myself it’s amazing what I can accomplish in but a few keypresses.
No matter the GUI you use, you’re leaving a lot of useful functionality on the table. By their nature, you only get a small fraction of git’s features. There are many useful commands I use regularly that are impossible to replicate using GUIs.
A good UI (for you personally) should do all the things you regularly do. Git is a complex and messy enough beast that when I have to use the CLI I’m going off the golden path and copy+pasting something arcane.
I was looking for this comment. PHP storm and git are like best friends. I very very rarely need to resort to the CLI and generally that’s for hard resetting after I screw something up
Good luck doing anything remotely complicated/useful in git with an IDE. You get a small fraction of what git can do with a tool that allows absolutely 0 scripting and automation.
There are automations. You can even add git hooks iirc. Mostly I find the lint and other code quality integrations nice to have in the IDE, since the inline results allow me to navigate directly to the code
It sounds like you don’t speak from experience. I have all the automation I need. It supports git hooks on top of IDE-only features like code checking.
If I have to fire up my CLI for some mass history rewriting (like changing an author for every commit), or when the repo breaks - so be it. But by not using the CLI I save my fingers and sanity, because committing a bunch of files is several click away with little to no room for error.
I can rebase, patch, drop, rename, merge, revert, cherry pick, and solve conflicts with a click of a button rather than remembering all the commands and whatnot.
This post title is misleading. The developer was working with Snap until Canonical didn’t allowed it anymore. He’s pissed with the policy enforcement which is strictly speaking commercial and as bad as Apple’s afaik…
Canonical has been taking bad decisions for quite some time now, and this developer was trying to reach Ubuntu users even while probably knowing these. Which makes sense, of course. The point being that this dev’s disappointment seems quite specific in these notes (against Snap), and imho he might work again towards shipping their app through Snap if he was allowed to. My comment compares Canonical to Apple, to give some context of where Canonical is at so many other idiosyncrasies (for example, I also heard other bad stuff about their H.R., in particular a way too lengthy hiring process.)
programmer_humor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.