4 ms·
If your time frame is less than 50 years I'll take that bet. But your comment leads me to believe you haven't used Java in some time. The GC has 100s of man y
by djb_hackernews 10y ago
If your time frame is less than 50 years I'll take that bet.
But your comment leads me to believe you haven't used Java in some time.
The GC has 100s of man years worth of research and optimization built in to it, Java provides a lot of higher level concurrency like executor services, fork/join, promises/futures, and with Quasar it has Go like goroutines called fibers. Optional is built in to the language as well (and to be honest find them sort of ho-hum, certainly a bizarre reason to stop using a language.)
- pawadu 10y agoSpeaking of Go... would Swift really have a chance against Go on server?
- alblue 10y agoIt's early days yet, but one advantage of having the same language on the client and the server is that you get a lot of benefit in code and team sharing.
- abalone 10y agoI think it's either 5-10 years or never. I am a huge Java user and fan btw, but I am looking to the next 20 years here. Despite much optimization, GC still struggles with memory efficiency and predictable performance in a diversity of scenarios. You have to tune it. I guess you could simplify my comment to two advantages: No GC, and elegantly baking constructs that make programming safer into the language as opposed to things you can opt-in to. While it may be possible to get these things with Java, if it's a lot simpler to get consistent performance, efficient memory use, protection from null pointers, and safe concurrency.. then there may be an opportunity for Swift.