Post

I c what you did there

january 6-7 and already post of the year

Where my fellow JAPHs at perl -E 'say join $/, map oct, -t ? @ARGV : map split, <>'

Memory unsafety… sounds interesting

Will Rust developers start putting these warning labels on every GitHub repo now?

Yes, it is : ) But type-safe and memory-safe programming languages, high-performance applications still used unsafe for interoperability and compatibility.

A language can allow memory unsafety, but it can't cause it. Only a programmer can do that.

If you allocate and deallocate enough times, the system turns chaotic…

the building i used to go to for therapy had the california cancer warning on it. i always thought that was funny

Modern Object Pascal is a highly underrated programming language. It does indeed teach good programming habits and how to properly do manual memory management without getting burned.

I c wut u did th3r3

Failure teaches lessons. Learn and rise stronger. Victory is near.

ping <you> -1 65500 -w 1 -n 1

Is this a Prop 65,536 warning?

Obliquely related, I fired up Arduino IDE this weekend (after an idle 6 months) and man, were my libraries out of date. Poor little ESP32 is having a day while I sort my admittedly janky code.

that could be anything

#version65.1.x #TOP100MOSTVISITEDSITES #TOP100MOSTDOWNLOADEDAPPS #DESKTOPOS #MOBILEOS #CLONEEVERYTHING #OPENSOURCE #MITLICENSE #BREAKTHESYSTEM #JUSTSHAREORDOIT -- #findthefulllistbelow2000000000BTC hypernotepad.com/n/87630345e6... -- #ifyoudontsharethiscomment100timesadaydontcallmebrother *74

Swift gaslights me into memory unsafety everyday

I thought you were going to say “to cause the spontaneous collection of garbage”

No -- still unsafe. "I consider myself really competent at writing memory-safe C. When I rewrote a C module in Rust, the code ran faster." -- Bryan Cantrill, Oxide CTO

Only in Commiefornia. 😂

No, I think it’s dissafety.

I have adhd, my memory has always been unsafe 😭

OMG. Flashback to freshman year.

Ah yes, the Prop 404 warning

C++ post

If you aren't blowing up registers with assembly language... Are you really even living?

Isn’t that memory &u&@76:$:&…<null>SEGFAULT

Serengeti Safaris: Home to the Greatest Wildebeest Migration www.kabiraugandasafaris.com/serengeti-sa... #Email: kabirasafarico@gmail.com #Hartford #LosAngeles #Miami #NewHaven #NewYork #Honolulu #SanJuan #Boston #SantaRosa #SanDiego #Sacramento #Seattle #Providence #Springfield #Portland

But randoms on social media are? Thank you arbiter of technology.

Gosh they’re really going overboard with these regulatory warnings.

If I don't see this as a quote of the week, I'm either going to find out it's a repost – or be disappointed.

BUT MUH BUFFER PURGE BRO

Cancer and memory corruption do have a lot in common.

I just put "Safe Harbor" statements in all my code to recuse myself from any responsibility. 🤭

It is a universal warning. There is absolutely no (and cannot possibly be) a product out there which doesn't. It is akin to saying "this person will eventually die".

So, it's made with C?

I don't have to worry about that. I wrote my own memory interface on an fpga so the data will never get there to be overwritten in the fist place.

It's the fault of how the hardware was designed. Let's get rid of it for safety’s sake. 😂

Watch DemocracyNow.org every weekday

your memories on b’sky

It contains a reference to unsafe memories

That worked so well for business locations and cancer causing materials that we should extend it to new domains?

I would not trust the State of California to evaluate computer languages for any property such as memory unsafety. I would not trust Beacon Hill in Boston to evaluate memory unsafety either. Lobbyists would absolutely tell them which computer languages were memory safe, MIT be damned.

Whatt product??? I need to know