Meh, I think they have better ways to spend their limited resources than putting them into something Amazon is also investing in.
> PS: that Go memory usage is incredible. Why is it so low when compared with even 'C'.
That study has been posted here and a bunch of other places and just isn't that reliable. It's based on The Computer Language Benchmarks Game. Some of the implementations are painstakingly optimized with SIMD and sophisticated algorithms. Some aren’t. It’s benchmarking N different programs written in M languages (where M<N) that satisfy a given challenge, not the same program ported to N languages. Which languages have high-quality implementations might say more about how obsessed a given language’s community is with this particular set of benchmarks and rules than the actual efficiency of the language in question.
Take a look at the dramatic difference between Javascript and Typescript. Then realize that Typescript is literally the same language. Basically I think someone wrote slow-solution.ts, then someone else wrote fast-solution.js, and no one bothered to cp fast-solution.js fast-solution.ts.
Edit: that said, I do think Rust is genuinely a great language when you need security and efficiency together. And Go is a great language when efficiency is not quite as important as productivity.
The Go problem is not so much that it's inefficient, it's that the lack of compile-time checks encourages bug-prone cowboy coding which is often mistaken as "higher productivity". Because no one's measuring the very real productivity impact of easily preventable software defects.
And using K different standard libraries. Otherwise I can't explain that they put C on a different result as C++, considering they are often the same compiler (and not just the same backend). Probably, it is benchmarking stdio vs iostreams or the like, which is interesting.
None of the current 3 C++ programs use `std::unordered_map` they use `assoc_container.hpp`.
The current C program uses `khash.h`.
Someone who was interested in evaluating "Energy Efficiency across Programming Languages" would have to look at the authors public code archive and understand what they did.
They provided the source code of their programs and makefiles. There's no need for guessing games —
Why do you think that is?
Perhaps it's because "proper" is ill-defined and very much a matter of individual opinion.
Which still significantly lags Java and C# when it comes to productivity.
It's based on these 4 year old programs —
https://github.com/greensoftwarelab/Energy-Languages
> … the same program ported to N languages…
You can write Fortran in any language ?
----
> … no one bothered to cp fast-solution.js fast-solution.ts.
Perhaps figuring out correct type annotations was too much of a barrier.
> It's based on these 4 year old programs —https://github.com/greensoftwarelab/Energy-Languages
Yes, that repo's blurb confirms what I said: "The complete set of tools for energy consumption analysis of programming languages, using Computer Language Benchmark Game"
If you were making some other point, I missed it. As for the programs being four years old, the paper was published in 2017, so that's exactly as expected...
> > … no one bothered to cp fast-solution.js fast-solution.ts.
> Perhaps figuring out correct type annotations was too much of a barrier.
Sure, the details don't interest me. The point is that these two languages with identical compilers (TypeScript gets translated to JavaScript, discarding you're annotations) show wildly different scores, which makes it impossible to take any of these numbers too seriously.
Your "painstakingly optimized with SIMD" doesn't apply much to those 4 year old programs.
> … which makes it impossible to take any of these numbers too seriously.
Never throw the baby out with the bath water.
Never take any numbers too seriously, just seriously enough.
What's this then? https://github.com/greensoftwarelab/Energy-Languages/blob/ma... There are some explicit SIMD instructions, and some programs written to allow autovectorization.
> Never throw the baby out with the bath water.
/eyeroll
There's no baby. There's no significant investment in applying equal levels of optimizations to the programs across languages. TypeScript vs JavaScript is a telling example but hardly the only one.
Yes there were some way back then.
Many more have been contributed since then.
> … equal levels of optimizations to the programs across languages.
How do you propose to measure that exactly?
Or will we like Goldilocks know it when we see it?
Like these —
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
> How do you propose to measure that exactly?
I don't have a proposal, other than to avoid overselling. I like that the Game's website has the text "If the fastest programs are manually vectorized SIMD, does the host language matter? You might be more interested in less optimised programs." The "Energy Efficiency across Programming Languages" paper though is overselling its rigor.
It's difficult to find a balance that works — otoh for some hints give a context, otoh for others hints give stones to throw ;-)
Actix-web is finally getting a stable, production-usable release. That alone ought to amount to a pretty sizeable boost for the ecosystem.
I liked Rocket's syntax, especially the Requests guards [0] I thought seemed like a good idea, but I haven't really looked that close to either since I never started my project.
[0] https://rocket.rs/v0.5-rc/guide/requests/#request-guards
Kind of hard to argue with the article's premise. Though all languages aren't equal for all tasks. For example, its hard to use Rust for web projects because the ecosystem isn't mature enough. May be there should be investments into Rust ecosystem from pro-environment groups.
PS: that Go memory usage is incredible. Why is it so low when compared with even 'C'.