If it ain’t broken, don’t fix it.
That’s the thing, it is broken and there is a fix desperately needed. C lacks memory safety, which is responsible for many, many security vulnerabilities. And they’re entirely avoidable.
If it ain’t broken, don’t fix it.
That’s the thing, it is broken and there is a fix desperately needed. C lacks memory safety, which is responsible for many, many security vulnerabilities. And they’re entirely avoidable.
Actually I think this is a pretty common thing. I know several people who use iPhones and other Apple products specifically to avoid the google alternatives.
In what way has Microsoft enshittified GitHub? Since the acquisition they’ve mostly made more services free for open source users, and prices and features haven’t gotten more restrictive.
VSCode runs on the web and has IDE-grade search functionality
The cables Apple includes now are very flexible braided cables and they are excellent for their purpose. Haven’t had one fail yet, or even show major signs on use. Would like to find any other company making a comparable product, but all the “ultra flexible” cables I’ve found seem to not be as flexible.
Depends on if you want your data format to be strict ascii. If you don’t care, then sure, why not?
Maybe that’s what you believe, but allowing commercial use has been a core tenant of free and open source software
This is one of the funnier things I see frequently on here. People both champion free and open source code and data that can be used for anything… until it is used for anything they even mildly dislike.
The phoronix forums are insanely toxic. Everything is bad. Gnome = kid’s toy. systemd = written by Satan himself. Every programming language = too slow. Anything vaguely interested in fostering a diversity, equity, and inclusion = true colors come out in full force.
It’s so toxic yet I subject myself to it every now and again. There’s absolutely no moderation going on and it shows.
Remove the need to, yes. Remove the ability to? No, and rust doesn’t prevent you from doing that, it just makes you mark it
unsafe
so that way if you fuck up and cause a memory error, the root cause can be narrowed down to a tiny fragment of the code base.