Conversation

Notices

1. Embed this notice
   d (deprecated_ii@poa.st)'s status on Monday, 02-Sep-2024 19:08:16 JST d

   in reply to

   • dead_man
   @dead_man I never said Java was supposed to replace C.
   
   A programmer who can't be trusted to touch memory is like a surgeon who can't be trusted with a scalpel, simply incompetent and dangerous. The surgeon doesn't expect the scalpel to miss an artery for him, he has to know where to cut. You, the programmer, should understand where you need to be careful about memory and design your code in such a way that you're not going to blow up the world when you make a mistake. C does not stop you from doing that, it just doesn't do it for you.
   
   The Microsoft problem is the same problem every large, long-running organization has. It has far too many people working on a poorly-architected product, who have little understanding of the product they're trying to modify because they didn't write it, it wasn't documented and they're too lazy/dumb to dig into their little piece to see how it works. That's not a language level problem and it will not be fixed by switching languages.
   • Embed this notice
     ?? Humpleupagus ?? (humpleupagus@eveningzoo.club)'s status on Monday, 02-Sep-2024 19:08:16 JST ?? Humpleupagus ??

     in reply to

     • dead_man
     Most security issue are social engineering hacks. Rust ain't gonna fix that.
   • Embed this notice
     dead_man@dill.burggit.moe's status on Monday, 02-Sep-2024 19:08:23 JST dead_man

     in reply to

     @deprecated_ii@poa.st the Java issue isn't that Java tried to solve C. Java was never meant to be a replacement for C anyways.
     
     Yes, there will still be unsafe code somewhere in some projects. That doesn't mean that writong safer code with guard rails shouldn't be the norm though (as opposed to unsafe code where the prpgrammer can shoot himself in the foot just by touching the gun)

   • Embed this notice
     d (deprecated_ii@poa.st)'s status on Monday, 02-Sep-2024 19:08:24 JST d

     in reply to

     • dead_man
     @dead_man No matter what guard rails you try to erect, someone, somewhere in the stack is going to have to deal with memory directly in "unsafe" ways. That is not a problem you can abstract away.
     
     Microsoft would still be producing dogshit in a "memory safe" language. The problems organizations like Microsoft have cannot be fixed at the language level, which should be obvious in a world where Java is pushing 30 years old.
   • Embed this notice
     dead_man@dill.burggit.moe's status on Monday, 02-Sep-2024 19:08:25 JST dead_man

     in reply to

     @deprecated_ii@poa.st it is a language problem.
     
     Stats showed time and time again that regardless how good of a programmer you are, you're still going to make mistakes.
     
     Top security vulnerabilities from Microsoft engineers, for example, are memory management bugs.
     
     If Microsoft can't get their shit together, I very much doubt a no-name startup can solve it by telling their engineers "just get good bro".
     
     C is a disease of a language that needs to be weeded out and replaced

   • Embed this notice
     d (deprecated_ii@poa.st)'s status on Monday, 02-Sep-2024 19:08:26 JST d
     this is not a C problem
     
     it's a programmer problem
     
     most programmers should not be allowed to touch a keyboard