Why aren’t “alternate syntaxes” a thing? You can pretty easily just write code to convert between C-like and Python-like syntax. Why aren’t there IDE extensions that let you write in python syntax and automatically commit the standard syntax.
Why would anyone bother writing it like that? That just seems like int main() with extra steps. Like does auto enable some compiler optimisation of the return type that I’m not aware of?
Lack of high quality public transit.
“Just drive bro”
fixes bug
bug fix uncovers code that was relying on the faulty behaviour to work properly
FUUUUUUUU
Reverse engineer it
Sparrows are already semi domesticated due to living near human settlements basically since we started farming.
BABOU!!
Cannabis oil
I don’t know whether to be flattered that they consider Lemmy a serious enough platform to farm responses or be pissed that they have infected Lemmy like they did with sites like Reddit.
Every time Rust takes forever to compile something, I picture in my mind it checking every possible edge case and buffer vulrnability I didn’t check and suddenly I’m a lot more okay with how long it takes.
Reminder that Linux’s decision to write an entire kernel in C and not a mix of C and assembly was just as controversial back then as Rust vs C is now. The pro-assembly programmers used many similar arguments as the anti-Rust programmers (it’s bloated, it’s too high level for the kernel, it has a complicated compiler, it’s just a pointless abstraction over what’s actually happening at the processor level, it’s not mature enough, if you were competent in assembly you wouldn’t need to use C, if assembly is too difficult for you then you shouldn’t even be developing a kernel, etc). Now Linux is hailed as one of the pioneer software projects that led the switch from assembly to C for kernel level code.
If even senior C developers can and regularly do write critical memory vulnerabilities that can give attackers remote code execution as root, then I’d say it’s indeed already broken.
“We don’t need TCAS on commercial airliners because any colisions are the pilot/controller’s fault”
Except that’s literally the reality with computers. Everything evolves and things go obsolete. I’m sure the COBOL and Fortran programmers were pissed when the kids started using C too.
Laptops with no intake dust filters.
Actually, no, any computer with fans that doesn’t have a dust filter is a terrible design.
IMO every distro should have a rolling release option. Kind of like how OpenSUSE has the normal version and Tumbleweed. You have normal version for when you need the OS to work (you’re new to Linux, it’s your main personal/work computer, it’s a server, etc) and then you have the rolling release option for when you’re willing to give up stability for the newest versions of everything as soon as possible.
Sorry to say it (and as much as i like C) but C is already on the path to inevitable obsolescence. Everyone is learning Rust now and fewer people are learning C. Maybe not soon, but definitely eventually. Linux can join C on this path to obsolescence or it can pivot to a language that still has a clear future.
Rust will go obsolete a some point too when the next next generation of languages come out. And software projects using Rust will have to switch languages again to stay relevant.
Don’t forget that languages like COBOL was once state of the art but was replaced by… C.
That’s just the computer circle of life.
No rust?
Guess that proves it’s the best programming language with absolutely zero edge cases! /s
Fedora Linux has been the most stable OS in my experience, having used Windows XP to 10 and switching to Linux before 11 came out. I can leave it on for literally weeks on end and the memory never randomly fills up, nor does it get more and more glitchy/crash prone as you leave it on, both of which I have experienced on Windows.