Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

500 Lines or Less

github.com

Post reply on HN
Print view View original

31–40 of 70 posts

Re: 500 Lines or Less

#31

Post by avar »

debo_ wrote: post #17

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…

The first thing I looked through, the pedometer/ directory, has a project that itself may be Don't you think including huge external libraries like that defeats the spirit of showing things that are 500 lines or less?

Re: 500 Lines or Less

#32

Post by patrickyeon »

avar wrote: post #31
debo_ wrote: post #17

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…

The first thing I looked through, the pedometer/ directory, has a project that itself may be Don't you think including huge external libraries like that defeats the spirit of showing things that are 500 lines or less?

I would think not. Is the interesting part of the problem drawing charts? If not, it makes perfect sense have that abstracted away somewhere else.

Re: 500 Lines or Less

#33

Post by bertr4nd »

avar wrote: post #31
debo_ wrote: post #17

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…

The first thing I looked through, the pedometer/ directory, has a project that itself may be Don't you think including huge external libraries like that defeats the spirit of showing things that are 500 lines or less?

To me it seems actively good to include examples that use well-developed libraries, to show the types of tools and abstractions that one can build on. Restricting oneself to a language's standard library may give the false impression that anything worthwhile requires a large bootstrapping effort.

That said, it would be fun to provide, e.g., a 500-line graphing library to show how one might begin building something like highcharts.

Re: 500 Lines or Less

#34

Post by agumonkey »

nine_k wrote: post #13

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.)

Oh how I'd like a compilation of 500L APL programs.

Re: 500 Lines or Less

#35

Post by [deleted] »

arsenerei wrote: post #3
archos1 wrote: post #2

*500 Lines or Fewer https://en.wikipedia.org/wiki/Fewer_vs._less

From your reference. > However, descriptive grammarians (who describe language as actually used) point out that this rule does not correctly describe the most common usage of today or the past and in fact arose as an incorrect generalization of a personal preference expressed by a grammarian in 1770. > Many supermarket checkout line signs, for instance, will read "10 items or less"; others, however, will use fewer in…

[deleted]

Re: 500 Lines or Less

#36

Post by dclowd9901 »

debo_ wrote: post #17

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…

How can one contribute to this project? I personally ascribe to the belief that there's no better way to learn something than by implementing it yourself and would like to grant what help and background in writing and development I have.

Re: 500 Lines or Less

#37

Post by dowjones123 »

nojvek wrote: post #24
debo_ wrote: post #17

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…

Will this ever be able as a git book?

I want to know as well

Re: 500 Lines or Less

#38

Post by Nullabillity »

oneeyedpigeon wrote: post #15
curiousgal wrote: post #9

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.

> This is a book people. I shouldn't really need to compile it;

As opposed to what, exactly? txt files?

Re: 500 Lines or Less

#39

Post by BurningFrog »

debo_ wrote: post #17

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…

So you don't have to look it up too:

Code golf is a type of recreational computer programming competition in which participants strive to achieve the shortest possible source code that implements a certain algorithm.

Re: 500 Lines or Less

#40

Post by amelius »

Offtopic. Why, in github, is the README always below the repository files, if the first thing you want to read about a project is the README?

Edit: Could we take the convention on HN to always link to the README in a github repo? In this case that would be:

https://github.com/aosabook/500lines/blob/master/README.md

Post reply on HN