Programming

17511 readers

359 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Feds: Critical Software Must Drop C/C++ by 2026 or Face Risk (thenewstack.io)

submitted 3 weeks ago by arendjr@programming.dev to c/programming@programming.dev

32 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] wewbull 42 points 3 weeks ago (3 children)

That sounds like policy written by somebody who has no idea what the reality of software development is.

1 year to rewrite critical software in a new language?

[–] nous@programming.dev 77 points 3 weeks ago

Did you read the article at all?

“Putting all new code aside, fortunately, neither this document nor the U.S. government is calling for an immediate migration from C/C++ to Rust — as but one example,” he said. “CISA’s Secure by Design document recognizes that software maintainers simply cannot migrate their code bases en masse like that.”

Companies have until January 1, 2026, to create memory safety roadmaps.

All they are asking for by that date is a roadmap for dealing with memory safety issues, not rewrite everything.

[–] GetOffMyLan@programming.dev 24 points 3 weeks ago

That sounds like a comment written by somebody who has no idea what the article says

[–] IsThisAnAI@lemmy.world 0 points 3 weeks ago

Solid detective work Lou.