I dunno, CMake has one of the worst syntaxes I've ever seen, and despite that it's one of the most popular languages used for C/C++ build scripting. This is because it has certain technical benefits compared to its competitors. I'm certain that having "bad" syntax is a disadvantage but it's less important than other factors. Also I don't think that Rusts syntax is universally disliked either.
zygo_histo_morpheus
joined 1 year ago
If you're hobby programming then do whatever you want obviously but if you're part of some sort of larger project that's trying to decide between Rust and C++ then subjective aesthetic arguments probably aren't going to be considered as heavily as technical ones (and rightfully so), which in Rusts case could be that certain classes of bugs are impossible. That's not to say that it's not possible to make a technical case for C++ over rust but syntax preferences probably aren't going to play a large role in how widely used either languages are, which is good.
I don't think that everyone has to switch to rust or anything but "I dislike the syntax" and "I only want familiar things" are really bad arguments for not using a language. Try something outside of your comfort zone for a bit, it will help you grow as a programmer.
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.
I'm surprised that no one seems to have brought up curl, which is maintained by Daniel Stenberg who is Just Some Guy™
Beeper is a free app that is built on the same matrix bridges, and it takes care of hosting for you. Downside is that this requires you to trust beeper
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.
Nice, I'll check it out. I've been meaning to customize the desktop a bit more but it works well enough for the moment.
There are probably better alternatives, but I have a raspbery pi plugged into my tv and use KDE connect to remote control the mouse and keyboard from my phone. If I wanna watch youtube I'll navigate to youtube.com and click on a video.
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.
"Desired" and "Admired" are very strangle labels, it like the question(s) might have been:
Which development environments did you use regularly over the past year, and which do you want to work with over the next year? Please check all that apply.
In which case VSCodes high "desired" score just means that it was widely used?
view more: next ›
What do you mean by its predecessor? C++? I think rust has a bunch of advantages. For one, designing a new language today gives you the benefit of hindsight meaning that they have a more cohesive set of features and a nicer standard library compared to C++ that has some bloat and cruft as a natural result of it evolving over several decades. It's also much easier to reason about undefined behavior in rust thanks to
unsafe. Algebraic data types are really nice and traits are better than classes.The borrow checker isn't just useful for low level programming. One of the other main selling points is "fearless concurrency" or essentially the fact that the borrow checker can help you reason about thread safe vs non thread safe data.