I wonder how they have discovered the name though. /j

There’s a list of Chrome extensions

If you don’t want to have an enshittified internet, it would be reasonable to not use and thereby support software by a company which actively works on enshittifying virtually everything it touches.

In other words: stop using Google / Alphabet products.

It’s for people who suffer from severe anxiety when they see stuff like: -> or * for example. /j

You can install things from random websites for Linux too, though.

"They would probably not want me to tell you that you can change your settings so that Facebook and Instagram cannot profit as much from your data anymore,” Oliver said, before directing viewers to a guide set up in collaboration with the Electronic Frontier Foundation on how to prevent Meta from tracking you. “If you’d be interested in a step-by-step guide on how to do that, simply visit johnoliverwantsyourraterotica.com.”

Nobody tests their shit well enough nowadays!

I think there is indeed a lack of commitment. Thanks to capitalism and therefore production deadlines. Well, given, you can’t always catch “all” potential bugs, not just memory related issues. That’s sometimes not even theoretically possible. But it’s no secret how software quality increases by testing it thouroughly. And a lot of the time I just don’t see that happening. I’ve worked at institutions where software tests were done by answering the question “does it compile and run?”. And I’ve experienced systematic tests with specialized test engineers, who still had to cut short a lot of the time. But to assume that software is always tested well enough is in my experience naive.

Read all your other comments man!

This is not helpful. If you have critique, be more specific. I know what I’ve written.

I am always open to discussion and changing my views if I see convincing arguments, as I did at another place here. Your lack of patience and quick judgement of my character is not my fault, but yours. I was discussing the issues here neutrally with you so far.

However, this topic is done for me anyway, as the discussions here did indeed change my view regarding memory safety in C++.

And that’s okay. It’s also not a “pile of shame”. If you’re in the mood to play something and then aren’t, that’s fine. Games are supposed to be fun. Don’t treat it as an obligation. Not every fucking choice in your life needs to be financially efficient.

Politicians who know nothing about those subjects should have no say.

Some ethical guidelines are very important though. We usually don’t want to conduct potentially deadly experiments on humans for example.

The article mentions how basic programs are missing. They acknowledge the existence of FOSS alternatives, e.g. GIMP instead of Photoshop Elements, but complain about it being too difficult or that some alternatives are simply not to be found via Mint’s “Software Manager”.

Which is not news and probably one of the reasons why desktop Linux-based distros have still not become mainstream. There’s just a lack of all that “user-friendlyness” less tech-oriented people need.

These things can be changed, although there is an economic barrier. FOSS projects are great and we see how many of them took off. However, if the main portion of users are not on Linux, but on Windoofs, then it doesn’t make much sense to invest time and money into developing and maintaining software for Linux while having commercial interests.
The sad reality is that Microsoft has gained that market dominance. You won’t get end-user oriented software companies on board with Linux as long as the user-share is so comparably low. This is a self-reinforcing cycle.

Windoofs meets UX needs and there is a lot of software people need -> most people use Windoofs -> companies develop and distribute for Windoofs -> people keep using Windoofs, etc…

To break out of that, people need convincing alternatives. Not just for Linux alone, but especially for the software running on it.

Which is hard to achieve, given how a plethora of Linux projects have to survive on donations alone and too few companies take the leap.

There is a silver lining though. With the Steam Deck and Proton, Valve really got a lot more people on board with Linux. I can only hope, that this trend continues.

But at the moment I fear that this will be short lived, especially with Microsofts “handheld Xbox” on the horizon.

So let’s see, how this unfolds. The EOL of Windows 10 is really a strong incentive to switch to Linux. For my part, I will go for the full switch, since I’ve used Windoofs mainly for gaming anyway and am using Linux systems daily for my job. But then again, I am an engineering scientist and I can’t picture, e.g., my parents being satisfied with a Linux distro.

The definition of “a memory safe programming language” is not in debate at all in the programming community.

Yes, my mistake. I’m sorry.

This is incredibly arrogant, and, tbh, ignorant.

You’ve willingly ignored the remaining part of that context, where I explicitly admitted problems in common usage. It was not my intention to come across as arrogant.

there is no language construct in place to protect from these trivial memory safety issues

Depending on what you mean by “language constructs”: there are, e.g. RAII or smart pointers. But they aren’t enforced. So it’s correct to say that C++ is inherently memory unsafe due to the lack of such enforcements. The discussions here changed my opinion about that.

Yupp. I’ve changed my stance on this.

Since C++ doesn’t enforce memory safe programming paradigms, it is inherently memory unsafe.

You’ve missed the context. There are occasions in Rust where you have to use more boilerplate code which you wouldn’t have to implement in C++ to that extent.

But saying that C++ is free of boilerplate is of course ridiculous, if you are not able to heavily leverage templates, CRTPs, macros and alike.

Yes. I stopped now. I was hinted towards the usual definition of memory safe languages at another point in this discussion.

Although it is perfectly possible to write memory safe code in C++, I agree that the lack of enforcement makes it inherently unsafe.

No. I changed my mind just very recently throughout this discussion.

I agree now that the lack of enforcement of memory safe techniques in C++ makes it inherently memory-unsafe.

That doesn’t change the fact though that it’s possible to write memory safe code, if you know what you’re doing, use the right patterns, classes etc…

I’m not. But in my experience, using memory safe programming patterns, classes and possibly additional testing and analasys tools do the job quite well.

But yeah. I changed my mind about this memory-safety-property. The lack of enforcement really does make C++ inherently memory unsafe.

You’re right. Thanks for the links. Although I still think that C++ provides the tools to enable memory-safe programming, I guess the lack of enforcement makes it inherently memory-unsafe.

Point taken, I’ll stop saying that.

does not warn anywhere

This is incorrect. If you properly test your code such errors will become visible. It’s not too much of an ask to conduct systematic software testing. You should do it anyway regardless of the language used.

you are really thinking that you are the perfect coder who jever makes any mistakes. It does not make sense to argue with you

You are quick with being judgemental and ignoring the rest of what I said in that part, which is why I agree with you. This discussion is no longer productive.

I hope they feel welcomed here to stick around. I’ve quit Reddirt in 2023 during the API exodus, came to Lemmy and never looked back.

This is such a weird take. C++ isn’t memory safe. The blanket statement is… true. You say as much in the second sentence.

I suppose we need to make definitions clearer. C++ is memory safe in the sense that you can write memory safe code. It doesn’t enforce memory safety though. But not doing that is not the language’s fault. If someone jumps with a bike from a flying airplane, it’s not the bike’s fault that they will not land safely. It’s the misuse of the bike.

The best developers money can buy still make mistakes with C and C++.

I’d argue those weren’t the best developers then. However, I don’t want to get ridiculous. I see that there are problems in the common use of C++. Although I can’t share that from my experience due to usually proper usage, thorough testing use of additional tools, there is surely a need for aiding C++ devs with writing safe code. I know of the corresponding security concerns as well as probably everyone else in the C++ community.

There are proposals to improve on that. Some of those might already come with C++26. Stroustrup’s favourite are Profiles to provide and enforce further guarantees, while others propsed an extension like Safe C++. Whereever the future will take us with C++, I’m confident that this issue will be sufficiently solved one day.

There was a time when C++ wasn’t even designed for multi-processor systems, lol. That was redesigned pretty late. Much has changed and it will continue to improve as C++ continues to mature.

Edit: Just saw your convention examples after I’ve sent my reply. Idk why it wasn’t displayed before.

Regarding the double free: It’s clear from the documentation that this returns a raw pointer.

Regarding the use after free:
I really don’t want to sound arrogant as this is a simple example of course, but that is such an obvious mistake and looks like a topic which is covered in C++ beginner classes. To me, this is almost on the same level as dividing by zero and wondering about resulting bugs.

but the developer needs to know all of them to not make the mistake

Yes. Not every language is as user-friendly as python. With more flexibility come more risks but also more rewards if you’ve mastered it. It depends on what you want to do and how much you’re willing to invest. I would at least expect a professional dev to rtfm. Which itself is apparently already a problem. But, in the end of the day we want to use tools, which are effective and easy to use. So sure, point taken. I refer to the section before my edit regarding developments upon improving such aspects in C++.

I’ve a very long track record using C++ as well and I can’t share the feeling. I don’t say it’s alyways easy. I’m just saying that it’s doable and therefore whether the software is memory safe depends on the expertise of the devs. Modern C++ practises, programming patterns and as well tools from the STL (or even your own implementation) make life a lot easier. If you don’t use them, that’s not the languages fault. In the end, how you use the language still matters a lot. If you’d like to think less about memory management, go on and use Rust or C# or Java or even Python if performance doesn’t matter. That’s perfectly fine. This can come with other issues, like more boilerplate in the case of Rust for example, but in the end those languages are tools. Choose the tool which gets your job done.