It only has to be less bad than C or C++ though and it's hard to argue that it makes things worse in any major way.
GC languages are pretty awful for anything non-toy. Performance and/or excessive memory usage is abysmal.
-
-
If they have value types, throughput is generally higher and memory usage isn't that bad. Java isn't a good example.
-
Oracle/Sun Java implementation is focused on throughput at all costs, ignoring start-up time, memory usage, latency.
-
It's also focused on large scale things, not small ones. ART in Android is a completely different animal than it.
-
Java is very wasteful since it doesn't have value types or proper generics. Forces so much dynamic dispatch / boxing.
-
C# does things sanely.
End of conversation
New conversation -
-
-
what a general claim! I don't know any sound (but at least sometimes useful) static analyzer not written in GCed language…
-
Sorry, toy is probably the wrong word here. More like "code not intended for deployment and use by general end users".
-
It's not a big deal if you use big resources in things like bug-hunting, scientific, etc. OTOH for code running on 1B+ devices...
-
but there is a large amount of Java and JS running on phones...
-
And that's why I say it's awful.
-
ok, automatic memory management has definitively won
-
Yes. Language-integrated refcounting (with ability to optimize out provably-unneeded ref/deref) is excellent.
-
It's much nicer when it can be non-atomic by default and still safe though.
- 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.