I’ve said this before only to hear “we don’t have time to set that up and agree on a common style” and “that’s team B’s responsibility since we’re contributing to their code base.” Guess what kind of issue we kept wasting time on?

There are a couple of takeaways here. I think the main one is acknowledging that many technical problems are deeply human problems and the existence of a technical solution doesn’t mean we shouldn’t apply the human solution as well.

And here I was saying using git in the command line instead of a visual form might make me an elitist.

I’ve been living life on easy mode and not putting real care into my work.

Exactly! That’s how I feel.

I always end up using VS Code for projects like that, but I don’t love its Got integration, so that really makes sense. I might give this a try when it’s more widely available.

Call me an elitist, but I think people really need to learn and use Git on the command line. It’s integral to the job and visual clients hide away not just the nitty-gritty, but often basic processes. Why do I end up teaching experienced developers how to use git reset? There’s some day-to-day stuff thaat I do like to do on the IDE though.

[hops off soapbox]

Ranting aside, JetBrains’ visuals and organization for Git are really good. Visaual Studio loses track of commits across forks and time, but Rider can keep up, so I’m sure a standalone client will work pretty well.

So how are you liking it?

Ah, matter of preference I suppose. At least there are a lot of settings to disable that stuff.

Neural network-based full line completion? I feel like the Rust model isn’t as developed as those for other languages. It’s helpful in Rider for C#.

It’s really interesting that Proton feels like a step forward in cross-platform gaming, but it also made it more economical to focus on Windows builds and dependencies.

Steam has a lot of power in the market and a vested interest in making things easier for developers and publishers. I wouldn’t be surprised if they picked up (more of) the slack in keeping systems backwards compatible.

Same as Microsoft, sort of. They can’t afford to have Apple’s “courage” in dropping x86 and then amd64.

Steam, as mentioned, and an old iMac that I’ve been meaning to dual-boot for a while.

This kind of thing is mostly inevitable, but has an impact on software and game preservation.

The i686-pc-windows-gnu target has been demoted to Tier 2, as mentioned in an earlier post.

Fedora is discussing dropping support entirely, right? Interesting times we live in…

Like if the variable is then used in a function that only takes one type? Huh.

And bow to the compiler’s whims? I think not!

This shouldn’t compile, because .into needs the type from the left side and let needs the type from the right side.

I came here to laugh, not to cry!

[clicks light switch off and on repeatedly]

Welp, I guess we’re closed for the week.

I’d say I feel seen, but it’s really dark in here.

let a = String::from(“Hello, world!”).into()

I’ll see myself out.

Good article, thanks for the link! In the context of this conversation, I can agree that being exposed to different ways of solving problems will make you better and faster at doing just that.

My take on a summary: like C/C++, Rust can be relevant in a variety of use-cases and one could conceivably build a long-term career on it, while adjusting to market/technology interests.

Seems like a reasonable prediction?

This is super interesting. I’ll admit I wasn’t even aware of this effort. Even real-time usage of Windows relies on a parallel kernel.

This sounds like it’ll create a lot of cool opportunities and reduce friction.