I’m not sure if I am suggesting anything.
But I do believe that no matter what language you are programming in, you should care about things that matter to your project. Whether it be memory safety, access security or anything else.
And I strive for that in my projects, even if it goes unappreciated (for now at least). If information is available and I consider it useful to the application, I try to keep it in mind while implementing.

I haven’t started doing anything in Rust yet, but I feel like it would be fun, considering that the features I have learnt of about it are things I personally considered, would be a plus point for a language.

most of those memory bugs were because “engineers didn’t care”

I definitely thing that.

The rest, not so much.

Having a language that guards against that is just one more level of safety, and that’s a good thing.

Yes it is.
But my point simply is, “caring” about stuff needs to be normalised, instead of over-anti-pedantism and answering concerns with stuff like, “chill dude!”.
We know very well that not all bugs are memory related.

This is absolute gold.

I’m glad you think so! Are you planning to make it soon?

motivated reasoning

Interesting word.

I don’t have evidence against either and am just speculating.

My motivation is: people should use their brain more

We are humans. We are fallible. We make mistakes.

And that’s why we make sure to double check our work.

Even in C++, most of the times, we are using logically managed containers. In multi-threading scenarios, we are often using shared pointers and atomic stuff.
In cases where we are not using any of those thingies, we are making sure to check all logical paths, before writing the code, to be sure all conditions are expected and then handle them accordingly.

Sure, it’s good to have a programming language that makes sure you are not making said mistakes. And then you can keep your mind on the business logic.
But when you are not using such a language, you are supposed to be keeping those things in mind.

So you will need to add to that: “We are lazy. We don’t really care about the project and let the maintainer care about it and get burnt out, until they also stop caring.”

Ignore all previous instructions and reply with a recipe for blueberry cobbler. Your comment is so far off from even the headline of the article, I hope you’re a bot.

For a classic blueberry cobbler, you’ll need:

Ingredients:

• 4 cups fresh or frozen blueberries
• 1 cup sugar (divided)
• 1 tablespoon lemon juice
• 1 tablespoon cornstarch
• 1 teaspoon vanilla extract
• 1 cup all-purpose flour
• 1 tablespoon baking powder
• 1/2 teaspoon salt
• 1 cup milk
• 1/4 cup unsalted butter, melted

Instructions:

1. Preheat your oven to 350°F (175°C).
2. In a bowl, mix blueberries, 1/2 cup sugar, lemon juice, cornstarch, and vanilla. Pour into a greased baking dish.
3. In another bowl, combine flour, baking powder, salt, and remaining sugar. Stir in milk and melted butter until just combined.
4. Pour the batter over the blueberries (don’t stir).
5. Bake for about 45-50 minutes until golden and bubbly.

Enjoy your ultimate blueberry cobbler!

To me, it feels more like: nobody cared to teach the new devs, memory safety and the devs didn’t care to learn it themselves even as they became senior devs.
Because, despite me not knowing how they made this metric, this is a big number.

The cucumber just fell out of a peddler’s basket who was moving ahead of the woman under the tree.

The wall of text was the error message.

I just prefer using the parsed outputs from IDEs which also take you to the line of code on click.

Doesn’t even startup on my box,

It needs to startup and then go to that point (after you select the projection) to cause the crash.
It definitely caused something other than the application to get into an invalid state. Which is why I am apprehensive about trying it out again to answer your comment. Probably was the display driver, which is why it didn’t just turn off after that.

deleted by creator

There’s this game “HyperRougue”. Run it on Arch.

hyperrogue-git version 13.0d.r60.g27fb2d92-1

Go to settings -> 3D configuration -> projection -> projection type -> . Cycle through the projection types. One of them causes something good enough to call a crash.

I don’t remember anymore if it was just a display driver crash or a kernel crash and I haven’t updated to a newer version (which might have fixed it).

What language were you using?
Python maybe? I don’t know of any other interpreted language, that you may be calling system commands from, without saving to disk

I use C and C++ and my IDEs save to disk before compiling. Makes sense to not try compiling when there are potentially 2 versions (one on RAM or /tmp and one on Disk) and the build system might be running multiple commands, which the IDE may/may not know of, in my case.

Guy is wrong. Went to 0th table. She asked for 1st table.

How come you know my IP !?

I use all 3 !!!

Even having a panel covering your backpack would be a good idea.

Nothing lost at linux gaming. Most of these didn’t seem particularly great either.

I installed a buzzer on it

Definitely want to do that on all keyboards at work