![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/b13dd487-9001-491f-b5b2-60fe23af667a.png)
-
Australia’s Northern Territory area: 1.42m km2
-
Australia’s Northern Territory population: 246,500 (2020)
Australia’s Northern Territory area: 1.42m km2
Australia’s Northern Territory population: 246,500 (2020)
deleted by creator
Yes, that’s the difference between “safer” and “actually safe”.
It’s also a fallacy that rust code is memory safe. I audited a couple of large rust projects and found that they both had tens of unsafe constructs. I presume other projects are similar.
You can’t use “unsafe” and then claim that your program’s memory safe. It may be “somewhat safe-ish” but claiming that your code is safe because you carefully reviewed your unsafe sections leaves you on the same shaky ground as c++, where they also claim that they carefully review their code.
deleted by creator
That might be true of VHDL / Verilog programmers I guess.
And the big secret is that plastic recycling happens much, much less often than you think. In Australia less than 10% of what gets collected for recycling is actually recycled. It’s similar in other countries.
Python’s become very widely used in industry - it’s definitely a plus when looking for jobs these days. TIOBE now says it’s the most popular language in the world.
I think the timeline’s a bit off here.
OP describes how primitive computing was in the 80s and 90s, and speaks of a number of developments which appeared “leading up to the year 2000”. Let me give examples of all of these developments which were actually from the 1970s or earlier:
My point is that I think these advancements were made a lot earlier than OP’s saying. Sure, some of them took a while to spread but we pretty much started the 80s with all of this already in place.
Don’t you mean:
class AgreementManagerClass {
public static void main(String[] args) {
System.out.println("I agree.");
}
}
Go’s less verbose than Java in my experience. And I’ve written quite a lot of both. But YMMV.
And yet C with its not at all comprehensive standard library did well. I’m a bit puzzled about these results.
There’s no way that Go is more verbose than Java. I’ve written both in decent quantities and Java was always way more verbose than Go for me. I suspect it’s the nature of code.golf giving these results more than the languages themselves.
Nice. I guess Antarctica’s next.