[raises hand] I’ve used MatLab instead of Photoshop, I guess.

Seriously though, as an amateur photographer, working on a new engine instead of just adding more gen AI features to every pixel sounds like a good move. I’ll be sticking with my buy-once option, either way.

As a developer I also found this interesting:

Can make steady progress even when a problem is ambiguous or not fully prioritized yet

That’s a super important skill a lot of people don’t even want to develop.

I still understand the argument of the C greybeard to Rust knowledge gap though. Objectivity, it’s hard to argue for a spidey sense that took years or decades to develop vs a deterministic and strict compiler, but developer (and reviewer) experience often seems to be rooted in personal comfort* more than in language features.

That said, we all have to deal with transitions and learning consistently leads to better outcomes. The argument is sound, but the pragmatic dynamics may take some time.

*”personal comfort“ doesn’t mean the language or tools are somehow objectively comfortable, but that people feel good, confident, productive, and happy working with them. Just yesterday I was thinking that I like the Gir “is hard” - it stimulates my brain on a daily basis. Different people get that in different ways.

I’ve taken to writing .http files which are runnable on a number of IDEs and plugins. I don’t need to know what anybody else is using to run them, they live with the code and I’m happy.

That said, I’ve seen people on QA do really cool end-to-end tests at load via very approachable scripting on Postman.

There’s lots of room for “to each their own” here.

Let’s all just wait for the new versions of languages, frameworks and operating systems. LLMs won’t have been trained on those and won’t have answers, people not asking each other online will generate no answers to train on.

Let’s read and train on docs, right? Yeah, right.

I love how the documentation is in the actual .h file and the read me is a mere formality.

I’m disappointed I didn’t get this as a floppy in the mail.

My thought as well, but those stones were shaped to match each other, reducing the amount of grout needed. It just goes to show the old ways still work, but you have to commit.

I came here to laugh, not to cry!

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

I’ll see myself out.

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?

Industrial controls equipment made by German companies can be programmed in English or German. You can also switch languages (German/English) at any time and the IDE switches over all the keywords.

Shared with my favorite blind iOS dev. Should be a good laugh!

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?