21–30 of 70 posts
Is there a compiled version somewhere? I don't think I will be able to build this on my phone.
I also attempted to build the ePub and HTML versions but that didn't work. Commented about this on issue #134 [2].
[1]: https://github.com/aosabook/500lines/files/288427/500L_pdf.z...
500 lines of what? 500 lines of APL / J / Q is enormous; 500 lines of Haskell / Scala / Ruby is quite a mouthful, 500 lines of Java or C is rather moderate, and 500 lines of assembly is precious little. Also, since a line of code can contain zero or more statements, something like cyclomatic complexity, or just statement count, could give a better measure. (Edited: fought autocorrect.)
'Cyclomatic Complexity of N or Less' would work against that goal as it says nothing about length and is hard to explain.
What a mindless criticism of a worthwhile project.
500 lines of what? 500 lines of APL / J / Q is enormous; 500 lines of Haskell / Scala / Ruby is quite a mouthful, 500 lines of Java or C is rather moderate, and 500 lines of assembly is precious little. Also, since a line of code can contain zero or more statements, something like cyclomatic complexity, or just statement count, could give a better measure. (Edited: fought autocorrect.)
What on earth do you think this is? It's not a research hypothesis. Nothing is being measured. It's a clever way to get people to show that ideas many people think are beyond their understanding can be illustrated in just a few lines of code. 'Cyclomatic Complexity of N or Less' would work against that goal as it says nothing about length and is hard to explain. What a mindless criticism of a worthwhile project.
Hi, I'm the editor of 500Lines. Thanks for posting this! A few notes: - Code golf was strictly discouraged throughout the review process. When authors were faced with implementing functionality poorly to fit more in, we generally cut scope instead. - 500 lines was selected as a limiting criteria because it is easy to specify and understand. You will see that the chapters written e.g. with Clojure do "more" (for some…
Here is a link to the pdf: https://dl.dropboxusercontent.com/u/29696071/500L.pdf
Earlier quoted context omitted.
I couldn't build it on my laptop. I'd have to install 3.5Gb of Tex dependencies to do it so I'll pass.
Me, either. Tried on OSX. Thought I'd get away with installing ~ 0.5 Gb when I read up about everything, but still run into problems. This is a book people. I shouldn't really need to compile it; even if I absolutely must , it should be at least possible, if not fairly straightforward. Disappointing.
No joy on epub, mobi, or html.
Hi, I'm the editor of 500Lines. Thanks for posting this! A few notes: - Code golf was strictly discouraged throughout the review process. When authors were faced with implementing functionality poorly to fit more in, we generally cut scope instead. - 500 lines was selected as a limiting criteria because it is easy to specify and understand. You will see that the chapters written e.g. with Clojure do "more" (for some…
> canonical problem in software engineering in at most 500 source lines of code I'll reserve judgement of the book for when its in a form I can easily read, but this seems to come up on the wrong side of the "less isn't always more" line. I can implement a lot of logic in 500 lines of code, but I won't be able to go back a month later and understand any of it, at least not without rebuilding the logic from scratch. A…