Cope

Egg

Prisoner Of War:

Because a commit should be an “indivisible” unit, in the sense that “should this be a separate commit?” equates to “would I ever want to revert just these changes?”.

IDK about your commit histories, but if I’d leave everything in there, there’d be a ton of fixup commits just fixing spelling, satisfying the linter,…

Also, changes requested by reviewers: those fixups almost always belong to the same commit, it makes no sense for them to be separate.

And finally, I guess you do technically give up some granularity, but you gain an immense amount of readability of your commit history.

Same. And even if you were to fuck up, have people never heard of the reflog…?

Every job I’ve worked at it’s been the expectation to regularly rebase your feature branch on main, to squash your commits (and then force push, obv), and for most projects to do rebase-merges of PRs rather than creating merge commits. Even the, uh, less gifted developers never had an issue with this.

I think people just hear the meme about git being hard somewhere and then use that as an excuse to never learn.

Is this about the straight werewolves author?

… are entirely possible, even if rarely the right choice.

Or a CLI with clap.

Curious what you are talking about. Multi-threaded sharing of memory for example is also easy with rust, it just doesn’t let you wrote and read at the same time, and so on.

Yeah. Once you get used to the (verbose, but by no means unergonomic!) syntax, you’ll probably never be happy with another language again. Job-wise, I am currently mostly using Go, and while also a nice language, I miss the confidence and security I took for granted with rust.

Not to mention just how goddamn expressive rust can be. Let bindings like if ok/err, else return? Assign from a match on Some(Ok(x))? Filter, map, and friends on any iterator? Oh my GOD the error handling with the question mark iterator? 100% confidence that if it compiles, no error, possible null value, or case is unhandled.

And all this WHILE giving you the amazing security benefits!

Ah, damn, caught me proselytizing again.

• if your skill is so great that you would never cause the kinds of bugs the rust compiler is designed to prevent, then it will never keep you from compiling, and therefore your complaint is unnecessary and you can happily use rust
• if you do encounter these error messages, then you are apparently not skilled enough to not use rust, and should use rust

In summary: use rust.

A Short Stay In Hell

Short novella based on this exact premise. If you have never encountered it before, I urge you to give it a read. It’s excellent. Also very disturbing.

Chat, is this AI-generated ads on Lemmy?

Sehr basiert. Pinguin sei mit dir!

Ich kann meine Partnerin leider nicht überzeugen. Sie ist Informatikerin, braucht keinerlei properitäre Weichware, aber lässt sich von den kleinsten Kleinigkeiten abbringen

I’m too lazy to insert the “look what they need to mimic a fraction of our power” meme here, so… Please imagine it instead.

I’m switching jobs in a couple of months, and I am SO glad to be leaving a (very well maintained!!) python codebase with type hints and mypy for a rust codebase.

It is just not the same.

Not really, no

DNS over TLS and similar are only encrypted to the first (local) DNS provider, and of course that provider knows the query as well.

It protects against 3rd-party eavesdroppers between you and your primary DNS provider, but does nothing for privacy beyond that.

Also getting rid of my T1 Diabetes and re-doing my transition, but yeah! Hedonism as well!

Spend the rest of my life on a Culture orbital or GSV? FUCK YEAH

How do you keep your hair UP all day?!

Like, seriously asking. Just… Cannot get it to stay up