It can be nice when you successfully do a rebase (after resolving conflicts), but change your mind about the resolution and want to redo it.
Doesn't come up that much, but it's been handy once or twice, for me. It's also just nice security: no matter how I edit commits, I can always go back if I need to.
I'd say the odds of kids doing that are pretty slim, they usually aren't that strategic when it comes to food. But even if it were the case, it's still no reason to control kids' food intake during mealtime. That's just abusive and is going to give them issues with food.
Kids are generally actually quite good at regulating their food intake naturally in ways that parents often don't understand. Adults tend to think in terms of roughly balanced meals for every meal, but kids often tend to favor one particular food at a time, achieving balance of nutrition over the course of the week. Especially when they're younger, it's often very chaotic what kids want to eat at a given time. They might love something one day and hate it the next. Their taste and palate are still developing, and it's a parent's job to be flexible rather than a child's job to follow arbitrary food rules.
If Republicans didn't gerrymander the fuck out of districts we'd be winning the electoral college vote for the 1st congressional district too.
I've yet to see any actual condescension from Rust developers, just a whole lot of people complaining about Rust.
Go is not something you can use for systems programming.
I'm sure it's fine for small-scale usage, but overall it's extremely inflexible and doesn't really scale well at all. There's also a lot of very basic functionality that's straight up missing. For example, there's no way to have a global epic priority. You can rearrange epics in an epic board, but the ordering of the epics there is not persisted elsewhere. There were many, many other shortcomings we kept running into.
Oh, and after a lot of our tickets had been imported (which itself was a huge undertaking since the auto import tools are complete trash), it started to be very slow. It feels like a very unfinished, unpolished product.
We use Gitlab's CI/CD features extensively at my current job and it's very, very nice. That's what they are actually good at, not project management.
I also wonder if people complaining about Jira are still on Jira Server. Jira Cloud is a much nicer experience. Certainly not perfect, but I've yet to see an actual viable alternative (once worked someplace that tried to move all project management to Gitlab... 🤮).
If you do want to go the web route, I'd highly recommend avoiding SPAs and going with https://htmx.org/ instead. Much simpler, less code, entirely driven by your backend, while still giving you the ability to make nice interactive applications.
As a bonus, since you presumably have been working with Python anyway, the author of htmx has a whole book online walking you through building an app using htmx and Flask, a web framework for Python: https://hypermedia.systems/book/contents/
Uh, there are an absolute fuckload of Java libs out there with nothing more than auto-generated garbage Javadocs.
I dunno, plenty of those sound pretty reasonable.
It's been massively effective and has put them on the defensive in a way no other criticism ever has.
Interactive rebase? There's no GUI that actually does that well, if at all. And it's a massive part of my daily workflow.
The CLI is far, far more powerful and has many features that GUIs do not.
It's also scriptable. For example, I often like to see just the commits I've made that diverge from master, along with the files changed in each. This can be accomplished with
git log --oneline --stat --name-status origin/master..HEAD. What's more, since this is just a CLI command, I can very easily make a keybind in vim to execute the command and stick it's output into a split window. This lets me use git as a navigation tool as I can then very quickly jump to files that I've changed in some recent commit.This is all using a standard, uniform interface without mucking around with IDE plugin settings (if they even can do such a thing). I have many, many other examples of scripting with it, such as loading side-by-side diffs for all files in the worktree against some particular commit (defaulting to master) in vim in a tabpage-per-file, which I often use to review all of my changes before making a commit.