0.11.0 Release Notes

Re:0.11.0 Release Notes by BaculumMeumEst on Friday August 04, 2023 @03:36AM (#36996689)

the united states government is not going to outlaw the use of memory unsafe languages. that is an absurd idea. nothing in your links suggests they would even consider it. "moving the culture of software development" to memory safe language does not mean "we want to put you in jail for writing C".

[ Parent | on HN ]

Re:0.11.0 Release Notes by grumpyprole on Friday August 04, 2023 @03:42AM (#36996742)

Where did you get the idea that jails are involved? Governments are clearly forming a position, if they fund new projects, they are quite likely to enforce that position. That's a significant market already.

[ Parent | on HN ]

Re:0.11.0 Release Notes by BaculumMeumEst on Friday August 04, 2023 @04:00AM (#36996876)

they can enforce that position by funding projects that are written in languages that they believe are memory safe. they do not need, or want, to legislate that.

[ Parent | on HN ]

Re:0.11.0 Release Notes by pjmlp on Friday August 04, 2023 @04:26AM (#36997081)

Funny that you mention that, EU does sponsor Rust development.

"Logical Foundations for the Future of Safe Systems Programming"

https://cordis.europa.eu/project/id/683289

As for US,

https://media.defense.gov/2022/Nov/10/2003112742/-1/-1/0/CSI...

"NSA advises organizations to consider making a strategic shift from programming languages that provide little or no inherent memory protection, such as C/C++, to a memory safe language when possible. Some examples of memory safe languages are C#, Go, Java, Ruby™, and Swift®. Memory safe languages provide differing degrees of memory usage protections, so available code hardening defenses, such as compiler options, tool analysis, and operating system configurations, should be used for their protections as well. By using memory safe languages and available code hardening defenses, many memory vulnerabilities can be prevented, mitigated, or made very difficult for cyber actors to exploit."

[ Parent | on HN ]

Re:0.11.0 Release Notes by dakom on Friday August 04, 2023 @04:10AM (#36996952)

Agreed, it's absurd. Jail time for writing javascript otoh...

[ Parent | on HN ]

Re:0.11.0 Release Notes by Borborygymus on Friday August 04, 2023 @04:21AM (#36997026)

I guffawed, and I'm not afraid to admit it.

[ Parent | on HN ]

Re:0.11.0 Release Notes by grumpyprole on Friday August 04, 2023 @06:51AM (#36998115)

And this attitude is why it's a serious issue in our industry. You clearly don't take security seriously, to the point that it's a laughing matter for you.

[ Parent | on HN ]

Re:0.11.0 Release Notes by dbalatero on Friday August 04, 2023 @07:07AM (#36998276)

If you can't see why jailing people for writing JS is a comically absurd concept…

[ Parent | on HN ]

Re:0.11.0 Release Notes by grumpyprole on Friday August 04, 2023 @07:13AM (#36998315)

Why is JS relevant to this discussion?

[ Parent | on HN ]

Re:0.11.0 Release Notes by pjmlp on Friday August 04, 2023 @04:19AM (#36997009)

No, however it may require that like with other kinds of dangerous chemicals, or hazourds goods, their use must follow strict requirements, like they already have to for high integrity computing.

[ Parent | on HN ]