4 ms·

> 1 - Why would you want to replace java on the server? Well one reason, if you look at the paper, is memory consumption. One of the ways Java gets good perfor

> 1 - Why would you want to replace java on the server? Well one reason, if you look at the paper, is memory consumption. One of the ways Java gets good performance despite being a GC'd language is less efficient memory usage. (Although there are many advancements in this area akin to what Go has accomplished but as the paper's metrics show, often Java uses a lot of mem.) Also probably lots of people will agree that it has accumulated some cruft over the years and predates lots of modern trends and things like concurrency and functional programming and whatnot require more complicated code patterns.. a classic example is the getter/setter verbosity of a simple value type (not trying to start a flame war here). However it's fair to say Java is the thing to beat in terms of "goldilocks" languages that blend productivity/safety with performance. > 2 - ...would we not use C++? Because it's a huge regression in productivity and safety. The goal is to reduce memory consumption while achieving great performance and, crucially, consistently low latency which is a greatly underappreciated server metric and really should be the number one benchmark IMHO.

bilbo0s 8y ago
>* is memory consumption...* ??? You're recommending a slower language, that uses more watts, on a presumably 24/7 backend... to save a few bucks on memory? As I said, if you want a company to switch to c++ or rust because you want to save money on memory IN ADDITION to all the money you're saving on watts, while getting the same or better performance? That might make some sense. Switching to go makes, No, sense. You end up paying more money per user session to do the equivalent work. (Even worse, each user waits longer because the work is done slower.) And then, like typical engineers, we'd proceed to explain to our bosses that all of this is actually better... because our new program uses less memory.
- abalone 8y ago
  You’re misrepresenting my statements. I believe I’ve been clear that it’s early days for these languages and that they are good candidates to supplant Java in the future based on their trajectories. Memory utilization is just one efficiency advantage of a reference counted language like Swift. There are other reasons to look beyond Java as well. Also, a request. Try to take it easy on the ???, all caps and excessive italics.
apta 8y ago
> and predates lots of modern trends and things like concurrency and functional programming and whatnot require more complicated code patterns.. And golang does what exactly for this? As a matter of fact, Java is superior here to golang on these fronts, and is only going to get better. There is a lot of unsubstantiated golang hype and people should know better.

bilbo0s 8y ago

>* is memory consumption...* ??? You're recommending a slower language, that uses more watts, on a presumably 24/7 backend... to save a few bucks on memory? As I said, if you want a company to switch to c++ or rust because you want to save money on memory IN ADDITION to all the money you're saving on watts, while getting the same or better performance? That might make some sense. Switching to go makes, No, sense. You end up paying more money per user session to do the equivalent work. (Even worse, each user waits longer because the work is done slower.) And then, like typical engineers, we'd proceed to explain to our bosses that all of this is actually better... because our new program uses less memory.

abalone 8y ago
You’re misrepresenting my statements. I believe I’ve been clear that it’s early days for these languages and that they are good candidates to supplant Java in the future based on their trajectories. Memory utilization is just one efficiency advantage of a reference counted language like Swift. There are other reasons to look beyond Java as well. Also, a request. Try to take it easy on the ???, all caps and excessive italics.

apta 8y ago

> and predates lots of modern trends and things like concurrency and functional programming and whatnot require more complicated code patterns.. And golang does what exactly for this? As a matter of fact, Java is superior here to golang on these fronts, and is only going to get better. There is a lot of unsubstantiated golang hype and people should know better.