4 ms·
Did you read the whole article? Towards the end it says: While the “Large tasks – Line count ratio” gives the most impressive result for Mathematica, I think t
by carlob 14y ago
Did you read the whole article? Towards the end it says:
While the “Large tasks – Line count ratio” gives the most impressive result for Mathematica, I think that the “Large tasks – Character count ratio” is the really the fairest comparison.
- jacquesm 14y agoThis is a fairly meaningless comparison. Rosetta code is not written for terseness, there is no fair comparison about code length to be made based on these example solutions to common problems. You can be as terse or as verbose as you want in many languages (think forth, perl, apl). If you want to do a meaningful comparison pick a non-toy problem and write a full sized application, something that in the worst language is a few thousand lines with a proper UI, a web app, a desktop application and a large simulation of something or other. You will still have to account for language gifts such as libraries or built-ins somehow. And you tell the devs they get points for producing short code. Then you can compare along several axis, performance, code maintainability (closely related to how easy it is to read) and so on. That's useful data. This isn't, regardless of whether mathematica looks good. edit: ok. point taken.
- Locke1689 14y agoNo, he was right, I stopped reading when the author started discussing the mechanics of crawling web pages. I assumed that the blog post would be structured sensibly (analysis, then implementation).