The US government wants devs to stop using C and C++ : programming

[–] it_depends_man@lemmy.world 23 points 4 days ago (3 children)

To address this concern, CISA recommends that developers transition to memory-safe programming languages such as Rust, Java, C#, Go, Python, and Swift.

If only it were that easy to snap your fingers and magically transform your code base from C to Rust.

guy_butterfly_meme.jpg is this unbiased journalism?

load more comments (3 replies)

[–] morphballganon@lemmy.world 16 points 3 days ago (1 children)

"Oh, I thought I was coding in Python. Oops!"

Continues coding in C++

[–] magic_smoke@links.hackliberty.org 4 points 3 days ago

Jython's your Python

[–] HiddenTower@lemmy.world 15 points 4 days ago (1 children)

I thought the US Government bought a lot of software in Ada, so I hope they continue with that.

[–] 0x0@programming.dev 1 points 3 days ago

The comment section mentions that conundrum as well... quite interesting.

[–] Swedneck@discuss.tchncs.de 15 points 3 days ago

well, i'm glad the US government is at least aware what C and C++ are!

[–] iAvicenna@lemmy.world 12 points 4 days ago

lol ok.

[–] 0x0@programming.dev 9 points 3 days ago (2 children)

The comment thread in that article is interesting. Grep for Ada.

load more comments (2 replies)

[–] Anticorp@lemmy.world -3 points 4 days ago

Too bad! Stay in your lane, pinche government!

[+] onlinepersona@programming.dev -12 points 4 days ago* (last edited 4 days ago)

Eventually, painfully, slowly, we'll move to memory-safe languages. It really is a good idea. Personally, though, I don't expect it to happen this decade. In the 2030s? Yes, 2020s? No.

This. Unless the government starts introducing fines or financial incentives (like fines) to force the use of memory-safe languages, ain't nothing gonna happen.

Anti Commercial-AI license

[+] ZILtoid1991@lemmy.world -13 points 3 days ago (2 children)

Because they want to replace them with more corporate-controlled languages.

Just add @safe: after your module declaration, and you'll be safe by default if you don't want to wait until D3.

Also, unlike in Rust, you can opt-out from RAII with int foo = void;, although it primarily has a performance advantage with arrays, not singleton variables (might be also useful for aquiring an RNG seed in a dumb way).

[–] UnfortunateShort@lemmy.world 13 points 3 days ago

Jep, you got em, it's all a conspiracy so they poison our mind with the evil tongues and make us corpo slaves with the help of Rust.

load more comments (1 replies)

[+] mercano@lemmy.world -24 points 4 days ago (7 children)

Ok, and what do you think the memory managers were written in?

[–] marcos@lemmy.world 16 points 4 days ago

AFAIK, the first one was written in LISP.

The one most people push around here was written in Rust. It's a really great language to write memory managers anyway.

[–] Mihies@programming.dev 14 points 4 days ago

I don't think those are the problem, but rather how they are used. And in case of managed languages like C#, it's almost impossible to shoot yourself in the foot when it comes to memory management. You still can, if you really wish, but you have to be very explicit in that. 🤷‍♂️

[–] whithom@discuss.online 7 points 4 days ago

If it’s broke, don’t fix it amiright?!

load more comments (4 replies)

Programming

Rules

Wormhole