This voluntary guidance provides an overview of product security bad practices that are deemed exceptionally risky, particularly for software manufacturers who produce software used in service of critical infrastructure or national critical functions (NCFs).
I interpreted your comment as being dismissive of understanding basic memory safety because no jobs care about this.
I thought it ridiculous that people don’t care that their programs explode. I guess it changes your mindset when your service going down isn’t a matter of costing the company money, but affecting real people.
I was being serious. I offhandedly expressed some excitement, in a comment I forgot I even wrote, about interviewing at a place that writes modern c++. Which, if you don’t know, c++11 and especially beyond has features to manage lifetimes, ownership, memory, and other important things just as Rust does (but it’s still C++, so of course it has all the baggage C++ must carry and a compiler that doesn’t enforce any of this).
But you rushed at the opportunity to be a complete ass about it and insult me for no reason. Presumably you also dismissively assumed I’ve never written Rust. Or that in 2024 the Rust jobs are so overflowing that I can just take my pick at one at my own leisure. As if my first preference is to write software in a language that still requires forward declarations.
Yeah. You had such a good point, though. I really would rather not have an income in favor of writing perfectly memory safe software that nobody uses. Surely you have advice on that?
Sorry about the friendly fire then, I guess. You seem to realize that in C++ you still have to think about lifetimes, only the compiler doesn’t really hold your hand. I thought you were the ASSHOLE who dismissively declared that Rust programmers don’t know how to write a linked list, without realizing that the problem is that C++ programmers usually don’t know how to write C++ either. And that’s why everything is on fire.
But you had to make more presumptions about my assumptions, and throw in a “nobody uses” because you genuinely have no idea how much my software is used, lol. So long as it keeps humming along you’ll never have to.
You’re god damn right I am. But my patience for trying to bring people up to my level has more than worn thin because of arrogant thought terminators like I originally responded to.
Fingers crossed I get this job I’m applying for where they actually care about this.
oh okay you’re actually stupid
wow
I am blown away that even in a socialist space people like you are obsessed with employment, and not with whether your program actually functions.
excuse me?
I interpreted your comment as being dismissive of understanding basic memory safety because no jobs care about this.
I thought it ridiculous that people don’t care that their programs explode. I guess it changes your mindset when your service going down isn’t a matter of costing the company money, but affecting real people.
But maybe you weren’t being sarcastic?
I was being serious. I offhandedly expressed some excitement, in a comment I forgot I even wrote, about interviewing at a place that writes modern c++. Which, if you don’t know, c++11 and especially beyond has features to manage lifetimes, ownership, memory, and other important things just as Rust does (but it’s still C++, so of course it has all the baggage C++ must carry and a compiler that doesn’t enforce any of this).
But you rushed at the opportunity to be a complete ass about it and insult me for no reason. Presumably you also dismissively assumed I’ve never written Rust. Or that in 2024 the Rust jobs are so overflowing that I can just take my pick at one at my own leisure. As if my first preference is to write software in a language that still requires forward declarations.
Yeah. You had such a good point, though. I really would rather not have an income in favor of writing perfectly memory safe software that nobody uses. Surely you have advice on that?
Sorry about the friendly fire then, I guess. You seem to realize that in C++ you still have to think about lifetimes, only the compiler doesn’t really hold your hand. I thought you were the ASSHOLE who dismissively declared that Rust programmers don’t know how to write a linked list, without realizing that the problem is that C++ programmers usually don’t know how to write C++ either. And that’s why everything is on fire.
But you had to make more presumptions about my assumptions, and throw in a “nobody uses” because you genuinely have no idea how much my software is used, lol. So long as it keeps humming along you’ll never have to.
No, I get it. You’re God’s gifts to computers. Carry on.
You’re god damn right I am. But my patience for trying to bring people up to my level has more than worn thin because of arrogant thought terminators like I originally responded to.
it costs nothing not to be toxic