I mean, if you want your prints to be asynchronous you’re looking for trouble to begin with.

The previous statement is a joke.

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.

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…

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?

Interestingly enough, you also have amazon.co.uk, which combines the nature (commercial) and location served (UK), but in the opposite order.

But it could limit the usage of its TLD.

I threw together a quick image to ASCII conversion project to actually use a couple of concepts.

Sometime this week I’d like to make it not panic over every little thing. I feel like I should be shifting error handling left, but it’s not very natural for me, just yet.

I will say, the ergonomics for testing with cargo are excellent.

I used that and Rustlings and really liked both, but somebody mentioned this and I decided to take a look. It’s cool that it introduces other concepts.

I’m working through rust-exercises.com and taking notes on my thoughts. I may or may not want to use it for a short workshop at work - mostly for fun, since I work with a very different stack.

So far, I don’t know if I like the exercises, because the target audience doesn’t feel like it’s clearly defined: you both solve is_even with an if/else and overflow an i8 to -1. I don’t think I’ve met the person who is that inexperienced and that knowledgeable…

How are folks liking these exercises?

One of my main concerns with this is the potential for making a lot of separate calls to the DB for a complex data structure. Then again there are trade offs to any architecture.

The insert on their Getting Started guide.

let new_post = NewPost { title, body };

diesel::insert_into(posts::table)
    .values(&new_post)
    .returning(Post::as_returning())
    .get_result(conn)
    .expect("Error saving new post")

Of course the other possibility is this guide is very low on abstractions.

Just learning. I threw together a little CRUD API in Rocket the other day.

Now I’m playing around with Diesel. I don’t love the intermediate New types, coming from EF Core. Is that because Rust ~~~~doesn’t really have constructors?