… the only language where 90% of the world’s memory safety vulnerabilities have occurred in the last 50 years
Yeah… That’s a shit post alright.
I’m not a C developer myself, but that’s just a low blow. Also, uncited ;).
… the only language where 90% of the world’s memory safety vulnerabilities have occurred in the last 50 years
Yeah… That’s a shit post alright.
I’m not a C developer myself, but that’s just a low blow. Also, uncited ;).
If you look deeper at the recorded PR commit, comments, and package description it’s clearly straight up mean-spirited.
Respectfully, please do not do this. Helium is a non-renewable resource. Once lost to the atmosphere it’s gone for good. Nitrogen on the other hand makes up 78% of the atmosphere and is equally effective.
Stamped with a Wisconsin logo, yep that fits.
My gods. I think this just gave me flashbacks to this week.
I was recently battling node’s import/require shenanigans trying to figure out how to import a typescript module in my basic program. I feel this so hard.
I walked away utterly hating the language and its ecosystem. Utterly defeated, I gave up.
I’m not any kinda fun person. But I did once get a chance to use an FN FiveSeven at a range once and it was fun. I was shocked at how much more I liked it over the 9mm’s.
Quite literally my first thought. Great, but I can’t issue certs against that.
One of the major reasons I have a domain name is so that I can issue certs that just work against any and all devices. For resources on my network. Home or work, some thing.
To folks recommending a private CA, that’s a quick way to some serious frustration. For some arguably good reasons. On some devices I could easily add a CA to, others are annoying or downright bullshit, and yet others are pretty much impossible. Then that last set that’s the most persnickety, guests, where it’d be downright rude!
Being able to issue public certs is easily is great! I don’t use .local much because if it’s worth naming, it’s worth securing.