when the official docs are telling you to use it, then it’s used. You can have no expectation of people to think the tooling isn’t shit when it’s literally the official recommendation.

Anything but the last one. Don’t duplicate the http code in the body, else you’re now maintaining something you don’t need to maintain.

I’m not a fan of codes that repeat information in the body either, but I think if you had used a different example like “INVALID_BLAH” or something then the message covered what was invalid, then it would be fine. Like someone else said, the error data should be in an object as well, so that you don’t have to use polymorphism to figure out whether it’s an error or not. That also allows partially complete responses, e.g. data returns, along with an error.

I completely agree.

I do not. I’m sorry.

https://github.com/nektos/act

it does if the other ones have edible seeds, seeds without arsenic, or fewer seeds… your analogy makes no sense.

Also, writing memory safe code honestly isn’t that hard. It just requires a different approach to problem solving, that just like any other design pattern, once you learn and get used to it, is easy.

the CVE list would disagree with you.

https://en.wikipedia.org/wiki/The_Power_of_10%3A_Rules_for_Developing_Safety-Critical_Code

and their 40 page coding standard document. https://ntrs.nasa.gov/api/citations/20080039927/downloads/20080039927.pdf https://ntrs.nasa.gov/citations/20080039927

and their software safety handbook. https://standards.nasa.gov/standard/nasa/nasa-gb-871913

all 389 pages of it https://standards.nasa.gov/sites/default/files/standards/NASA/Baseline/0/nasa-gb-871913.pdf

It’s also just a huge fallacy. He’s saying that people just choose to not write memory safe code, not that writing memory safe code in C/C++ is almost impossible. Just look at NASA’s manual for writing safe C++ code. It’s insanity. No one except them can write code that’s safe and they’ve stripped out half the language to do so. No matter how hard you try, you’re going to let memory bugs through with C/C++, while Rust and other memory safe languages have all but nullified a lot of that.

You ask them to add a license, you don’t suggest a license.

You can write cross platform mobile (and desktop and even browser) apps with Kotlin.

Candle that never burns out means fire in a vacuum. Pretty powerful stuff.

Man is this relatable this month lol

Skewed priorities like trying to make sure that Firefox continues to exist even with the massive amount of competition in the browser space and everything being taken over by chromium. Yeah. Definitely skewed priorities.

Really weird to compare to Python and C/++ when Java’s closest competitors are definitely C# and Kotlin. If you were to rewrite that list comparing Kotlin and Java it would literally be nothing in favor of Java and all the same benefits for Kotlin plus more safety features. Honestly the whole article seemed forced, like @balder1993 said below. The part about java having ‘functional programming’ is also a laugh. It’s all based on interfaces, and you have to use terminal operations to do anything on a stream, it’s terrible design.

Yeah some dude literally posted a meme the day before.

Thanks for the context. You can really tell by reading it too, they’re clearly trying to make it sound like companies can’t exist without tracking users, absolutely batshit insane.

I spent a lot of time and energy doing that years ago and don’t want to do it anymore. Mailing lists suck because you’re subscribed to a billion things you don’t want to hear about. IRC…honestly…the world has just moved past it.

Hey @db0@lemmy.dbzer0.com, just so you know, this tool is most likely very illegal to use in the USA. Something that your users should be aware of. I don’t really have the energy to go into it now, but I’ll post what I told my users in the programming.dev discord:

that is almost definitely against the law in the USA. From what I’ve read, you have to follow very specific procedures to report CSAM as well as retain the evidence (yes, you actually have to keep the pictures), until the NCMEC tells you you should destroy the data. I’ve begun the process to sign up programming.dev (yes you actually have to register with the government as an ICS/ESP) and receive a login for reports.

If you operate a website, and knowingly destroy the evidence without reporting it, you can be jailed. It’s quite strange, and it’s quite a burden on websites. Funnily enough, if you completely ignore your website, so much so that you don’t know that you’re hosting CSAM then you are completely protected and have no obligation to report (in the USA at least)

Also, that script is likely to get you even more into trouble because you are knowingly transmitting CSAM to ‘other systems’, like dbzer0’s aihorde cluster. that’s pretty dang bad…

here are some sources:

• https://www.law.cornell.edu/uscode/text/18/2258A
• https://crsreports.congress.gov/product/pdf/LSB/LSB10713
• https://www.missingkids.org/theissues/csam
• https://www.cloudflare.com/service-specific-terms-application-services/#csam-scanning-tool-terms
• https://developers.cloudflare.com/cache/reference/csam-scanning/#what-happens-when-a-match-is-detected
• https://developers.cloudflare.com/cache/reference/csam-scanning/#what-action-should-i-take-when-a-match-is-detected

Man I’m so good at sleeping though. I get at least 5 hours a night, so that’s 40 a week! Woohoo!

/s