As a non-programmer who works very closely with a programmer, I was doing a bit of reading and found this little piece of text that made me laugh, hard.
"Python and Go pick up your trash for you. C lets you litter everywhere, but throws a fit when it steps on your banana peel. Rust slaps you and demands that you clean up after yourself."
🇨🇦Samuel Proulx🇨🇦 reshared this.

Matt Campbell
in reply to Nick Giannak III • • •Matt Campbell
in reply to Matt Campbell • • •Nick Giannak III
in reply to Matt Campbell • • •Nick Giannak III
in reply to Matt Campbell • • •Matt Campbell
in reply to Nick Giannak III • • •Matt Campbell
in reply to Matt Campbell • • •Nick Giannak III
in reply to Matt Campbell • • •Matt Campbell
in reply to Nick Giannak III • • •Nick Giannak III
in reply to Matt Campbell • • •Matt Campbell
in reply to Nick Giannak III • • •Resigning as Asahi Linux project lead
marcan.stNick Giannak III
in reply to Matt Campbell • • •x0
in reply to Matt Campbell • • •Jamie Teh
in reply to Matt Campbell • • •Matt Campbell
in reply to Jamie Teh • • •@jcsteh Interesting perspective. I think it's fair to say that, in cumulative working hours, you've spent more time immersed in C++ than I have. In my Serotek days, I used C and C++ as little as possible, and yes, System Access's performance might have suffered some as a result. I admit that when I joined Microsoft, I was a bit incredulous that Narrator really was written all in C++, and interns even prototyped new features in C++. So maybe I was more open to learning the Rust way?
@nick
Nick Giannak III
in reply to Matt Campbell • • •Matt Campbell
in reply to Nick Giannak III • • •Matt Campbell
in reply to Jamie Teh • • •@jcsteh To actually answer your point though, yeah, I guess the rules around ownership, borrowing, and mutability required some relearning, though certainly not relearning how to program from scratch. I feel it's been worth it, but I know others may not.
@nick