Is public by default an unsafe default?

[NotYouAgain]

On Wednesday, 1 May 2024 at 13:06:14 UTC, Serg Gini wrote:
> On Wednesday, 1 May 2024 at 11:52:30 UTC, NotYouAgain wrote:
>> Please be respectful in your comments, if you have anything to 
>> say.
>
> Could you be so kind to prepare your post in a more structured 
> way?
> In case this feature you are interested in, check several 
> languages(not only Kotlin. Let’s say Java, Rust, C++, C#, Go, 
> Swift, Julia, Python), provide outcome of their analysis, 
> prepare some code examples which are showing shortcomings of 
> current/proposed behaviour.

I didn't argue its shortcomings, and I gave a link that argued 
the issue both ways.

Plenty of people have written phd's on this topic. I don't need 
to write one as well.

I just wonder what whether national cybersecurity strategy's may 
begin to look more closely at the implication of languages that 
are public by default, and perhaps start to incorporate this into 
their recommendations (in additional to memory safety). I expect 
it is inevitable that they will.

https://nordicapis.com/8-significant-api-breaches-of-recent-years/