1,077 karma · joined March 2, 2010
Of course, if you notice a broad pattern in every part of your life please consider professional help.
I think this Chrome extension called "GitHub Repository Size" might be exactly what you are looking for
There are many, many real life situations where a developer needs to choose between using JSON, XML or YAML to store their configuration data, message formats etc. Simply stating that JSON is good only in one scenario and XML must be used in every other is over-simplification.
When I start shopping online, I realize that I don't know much about Jen, so I need to call a friend. Lots of discussion later, I finalize on something to buy then I need to think of a personal note to write.
At the checkout, my banking application tells me that my internet password needs to be changed. The whole process gets aborted!
Probably, I exaggerated a little but my point being that each task involves a million micro steps which may or may not be anticipated. No wonder there is a lot of procrastination!
[1]: https://en.wikipedia.org/wiki/Burroughs_large_systems#B5000
Unfortunately, every tool has a quirk and we eventually need to settle on a workflow that somehow works, even though everything might be open source as you have described in the case of Pandoc. But I believe Emacs is the best authoring tool for books due to its versatility.
EDIT: Some more corrections:
1. `List.hd []` doesn't raise an error as its return type is an option. So the result is a `None`.
2. `List.map` and `List.filter` arguments should be reversed. First argument should be a list and the second should be the mapping function.
The title is not entirely falsified either - ReactJS is fast out of the box. Other frameworks can be tuned to achieve comparable speeds. But in most cases, ReactJS still wins.
Pygame Zero seems like the best of both worlds.
Wow, I was not aware of this.
[1]: https://github.com/mineta/taskbuster-boilerplate/blob/master...
[2]: https://github.com/mineta/taskbuster-boilerplate/blob/master...
My guess is that it is because no two software projects are alike. Differences stemming from differing technology stacks, to domains or people skills, it is practically impossible to generalize anything across them.
Unless we all standardize on a one true way of software engineering, such folklores will continue to exists and there will be a dearth in repeatable conclusions.
PS: However, I do agree with Laurent that we can work towards aggregating numbers from several real software projects than rely on unsubstantiated folklore.
[1]: https://github.com/takluyver/mobilechelonian/tree/require-wi...
In the case of the Portable Executable (PE) format, 97 bytes is certainly an impressive feat.
[1]: http://www.gnostice.com/nl_article.asp?id=225&t=The_Smallest...
$ python -c "from decimal import Decimal as D; print(D('.1')+D('.2')-D('.3'))"
0.0
Or if you prefer true rational numbers: $ python -c "from fractions import Fraction as F; print(F('.1')+F('.2')-F('.3'))"
0
$ python -c "from fractions import Fraction as F; print(F('3.1415927'))"
31415927/10000000