If anything I think that the current rust discourse is a fad. I’m not sure what it is about rust that makes people have so strong opinions about it but I can’t wait for it to become a “normal” language so that people can chill about it a bit.
There are non-propietary versions of android, I use /e/OS for example. Try searching for de googled android if you wanna find out more.
When I’m just locally iterating on stuff I’ll usually do a git commit -m "WIP: Description of what I'm trying to do" and then git commit --amend to it. A bit more ergonomic than stashing if I want to switch branches imo. I can also go back to old versions if I want to through the reflog.
git commit --fixup some-commit is also great for if I discover things in the review for example. You can then do git rebase master --autosquash to flatten them into the commit they belong to and that way you don’t have to bother with commit messages like “fixed typo”. Doing fixups for small fixes is good because it allows you to keep your mr broken up into several commits without also leaving in a bunch of uninteresting history.
Can recommend checking out the –fixup section in the git documentation if you haven’t heard about --fixup before.
The different worktrees share the same .git state. The article has an example where the author uses one tree for writing code and one for fuzzing it. If they used multiple clones they’d have to push from the writing directory and pull from the fuzzing directory to get new commits to fuzz but with worktrees this state synchronization between different git directories happens automatically.
Well he speaks english so in that sense he’s english speaking
Yeah the title of the post makes it sound much worse than what it seems to be in practice? Maybe I’m just naive
Well right now most people develop apps supporting x86 and leaves everything else behind. If they’re supporting x86 + arm, maybe adding riscv as a third option would be a smaller step than adding a second architecture
Don’t know anything about this particular case so while “social engineering to create a backdoor” is certainly a possibility, so is the more straightforward explanation that it is drama about real or perceived problems in the nix community. I think that it’s dangerous to dismiss this altogether because of the recent xz debacle.
You should, there’s a lot of cool stuff going on in the Morrowind community and now is a really good time to get (back) into the game. Province: Cyrodiil, which has adding cyrodiil as based on Morrowind-era lore to the game as a goal, is set to release have its first major release later this year. I’ve also been getting into tes3mp lately which is a fork of OpenMW for multiplayer.
As a big fan of the neverwinter nights community,
You might appreciate this April fools joke from the OpenMW team then :D
This might not be what you mean when you say “addictive”, but since I’ve been addicted to it for the last half year or so, I’m gonna suggest it anyway: Morrowind.
While the original came out in 2002 for Windows and later Xbox, there’s been a fan remake of the engine which runs on linux (and windows and macos) called OpenMW.
It’s an open world role playing game about exploring the island of Vvardenfell, which is a strange and alien place that’s easy to lose yourself in. Most of the wildlife is made up of insect- or dinosaur like creatures. There are forests made up of giant mushrooms, and ancient wizard lords who use magic to grow mushrooms into buildings that you have to be able to fly to navigate. It’s a world with a rich history, featuring several different religions, cultures and overlapping and competing political structures.
Despite its age, it is to this day a game with a very active modding community which can extend and improve the games mechanics and visuals. It also features what is probably the longest running active modding project, Tamriel rebuilt which seeks to add the rest of the province of Morrowind to the game. It’s about half way done and has basically another game worth of content in it at this point.
Like you say, there are always gonna be particular cases where gui/cli is better but for the general case I think it has to do with if your workflow is more terminal or gui oriented in general. I think that many of the tradeoffs in gui/cli git aren’t really unique to git so I think sticking with your general preference in that are makes sense.
Since I’m a vim user (shocking, I know) I actually use git through the fugitive plugin a lot, but it’s a fairly thin wrapper around the cli interface so most things are pretty much just the same as using the cli except that you can call them as vim commands instead (:Git push instead of git push and so on)
Yeah, I mostly use plain git log but on occasion
There are diff plugins that have syntax highlighting, I use delta for example.
For viewing and searching logs, I prefer the terminal because that’s usually where I am anyway so alt-tabbing to a gui window means more context switching which isn’t a big deal but is enough for me to want to stay in the terminal.
You can just diff two commits on the cli with git diff commit1 commit2 but I guess that what you mean is that you might not have any specific reference two either of the commits so you have to browse through the log to find the commit message that describes the commit, which I’ll grant you is easier in a gui because you have two variables that you have to copy and paste if you’re in the terminal.
I don’t get that at all, to me using a GUI just gets in the way while on the CLI I can do whatever I want in a usually straightforward way.
Part of Linux culture is customizing your system. Linux allows you to do much more with your computer, but some of these things require tinkering or might cause you to break your setup. If you don’t tinker much things will most likely be stable, but having the ability to tinker is for me a major part of the appeal. What are you hoping to get out of using linux? It’s a good alternative if you wanna make an old computer run more smoothly, if you care about privacy or if you don’t want to have to pay for your operating system, and if any of those are your main reason go for it and it will probably work out smoothly. If you’re interested in linux because it seems “cool” or “fun” you’re probably gonna have to do some tinkering so in that case you should be prepared to edit some files, read some instructions and possibly ask for help online.
Cleaning up your history before making a PR can make it easier to review so I always try to do that, but it’s not something that should be over done because it can quickly eat up more time than its worth if you go overboard
The benefit with rebase is if you want to have maybe 4 commits insteadd of 10. When reviewing a large pr, I find that it’s helpfull if it’s broken up into a couple of coherent commits so that I can review it commit by commit. It’s easier to follow the logic of why something is being changed if it’s associated with a specific commit.
Sometimes squashing the entire commit is the right choice, in which case you can do what you’re doing or use some built in feature to do that.
UltiSnips is fantastic
Was it the version controlling or writing in markdown part that was a hassle?
As long as you have your windows license key you can change your mind later so really you can do whatever. I’d recommend giving 100% linux a try if that seems fun. Obviously you’re gonna want to back up any interesting files that you have on windows either way.