712 karma · joined March 19, 2009
They have serious fulfillment issues.
Each core is a RISC processor with local memory. OpenCL is designed to target heterogeneous architectures and map to whatever compute is available.
The "benchmarks game" is largely the same as when it was called the "language shootout" now with more caveats plastered about. Please explain to me which language tribe I am promoting by calling the "benchmarks game" by its original name? Is it the tribe of skeptics? Perhaps use an HTTP 301 to redirect <http://shootout.alioth.debian.org/>; to <http://microbenchmarks.alioth.debian.org/>; and expunge "shootout" from all names?
My guess is that your mistaken view of what the benchmarks game promotes reflects a lack of familiarity with what the website says about itself on the homepage and the Help page and the Conclusions page and ...
Instead of guessing what my "view" "reflects", consider what the "benchmarks game" has promoted in TFA:
Title: "The Go Language is faster than the computer language benchmarks game thinks it is"
Well, this isn't what the "benchmarks game" says it measures anywhere (in fact, the site explicitly decries this interpretation) and yet this is what it indirectly promotes in various language communities (and linkbait tastes good).
Conclusion: "So Go should be between C and Clean, smoking scala, clojure, java and lisp."
Again, this isn't what the site says it measures (it measures some aspects of some implementations, not languages) and yet this is how it is portrayed by third parties. I understand that it is difficult to give people a lot of 'easy' data and simultaneously educate them about the reasonable limits of inference based on those data. I understand that the benchmarks game has taken great pains to try to educate its readers and inform their conclusions. I don't know if it will ever be enough -- people (as we can see) like easy answers and aren't willing to 0.) do the work to get more complete data sets and 1.) temper their findings with objective reality instead of drawing misinformed conclusions.
Do you see how the easily-digestible plots (indirectly) promote tribalism over rationality? Do you see how a plot is worth a thousand words?
What is the relationship between fold + cons (::) and monadic bind? What is the natural transformation from fold to functorial map? Is there a sensical dual?
Thanks.
Why is this source credible?
We know quantum constants. Is a cosmological bivector so different? Should be observable?
If only we could measure universal expansion accurately at small timescales, we could listen to the rain on the roof (horizon).
No dynamic server-side templating language, easily transformable to other XML formats (docbook, atom (see front page of registry)). If the user/client has libxml, the processor command is already installed. The specifications are now provided in an application specific format that is language-agnostic instead of manually maintained ad hoc HTML. The extension registry index page is now automatically generated into static HTML instead of manual HTML+JavaScript for sorting the lists.
Finally, the restricted power of XSLT is an advantage for this application vs PHP, ASP, or JSP. If browsers actually implemented web technologies like XSLT, sending XML specs and generating HTML on the client side with cached XSLT would save bandwidth.
Of course, the "pendulum" isn't discrete and is really a result of the plummeting cost of computing equipment so that both the garage hacker and the mega-corp can deliver outsized value by leveraging their unique traits.
My objection to this turn of events is almost entirely related to the behavior of Google and their search deal with Mozilla. Mozilla has compromised their principles again and again for Google and it is accelerating.
I'm tired of Google's doublespeak and lies about "Open Web" and open standards. If SPDY takes off, we will all have to think about supporting it and if it's built correctly that will be fine. I seriously have my doubts.
It would have been much less suspicious if the second browser to adopt SPDY was Safari or IE. Right now, it looks like Google is essentially bribing an "independent" browser vendor to implement their half-baked standards so they can turn around and claim "it's a web standard!".
It's like 1999 but now with corporate protectorates!
Traffic is harder to debug. Google continues to act like it owns the Web.
These are disadvantages for the world.
Bring on the downvotes of the naive Googlers! This place was getting boring anyway...
Is Mozilla doing the best thing for the Web or further cementing the current browser landscape? Will it be better when I have to write my crawlers to work with HTTP 1.1, SPDY, and HTTP Next?