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

41–50 of 70 posts

Re: 500 Lines or Less

#41

Post by AstroJetson »

agumonkey wrote: post #34
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.

I worked on a billing system that was written in APL, maybe 60 functions at 5-10 lines each. The corresponding manuals (one development, one user guide) were both over 300 pages.

Maybe some of the APL mavens can do the existing examples in APL and explain them. The write density of APL is pretty amazing. Depending on what you are doing a clear winner at code golf.

Re: 500 Lines or Less

#42

Post by [deleted] »

amelius wrote: post #40

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

[deleted]

Re: 500 Lines or Less

#43

Post by ams6110 »

amelius wrote: post #40

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

Well, it's the first thing you want to read about the first time you visit the project. The rest of the time it's probably the last thing you are interested in.

Re: 500 Lines or Less

#44

Post by agumonkey »

AstroJetson wrote: post #41
agumonkey wrote: post #34

Earlier quoted context omitted.

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

I worked on a billing system that was written in APL, maybe 60 functions at 5-10 lines each. The corresponding manuals (one development, one user guide) were both over 300 pages. Maybe some of the APL mavens can do the existing examples in APL and explain them. The write density of APL is pretty amazing. Depending on what you are doing a clear winner at code golf.

I guess that system could deserve a 4 year cursus to reach understanding. APL breeds fields.

Re: 500 Lines or Less

#45

Post by marssaxman »

amelius wrote: post #40

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

I considered Github links to be essentially content-free noise for several years because I did not know about their "README.md" convention. I think that people who live and breathe github probably don't realize how confusing their interface can be to a newcomer.
Post reply on HN