ius
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](https://github.com/aosabook/500lines/blob/master/README.md)

~~~
marssaxman
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.

~~~
mjrbrennan
You didn't think to just scroll down?

~~~
marssaxman
I didn't know to scroll to the bottom, as I had never used github and was
unfamiliar with its interface. I thought it was basically just a prettier
version of the classic auto-generated "index" page for a directory, so it
didn't occur to me that there would be more to it than the file list if I
scrolled down.

~~~
pc86
> _I didn 't know to scroll to the bottom_

If only there was some sort of bar that could indicate your relative position
on the page. Maybe in the same spot on all websites to make it easy to see.
Maybe even part of the browser!

In all seriousness this seems much less a GitHub issue and much more about how
well you computers.

~~~
marssaxman
It is an issue of expectations and affordances. If there's no clue that what's
at the bottom is going to be different than what's at the top, and what you're
seeing at the top is not giving you anything useful, why would you scroll
further and waste your time seeing more of it? Perhaps for some people that is
natural, but different people navigate unfamiliar spaces in different ways.

What you see when you open a github project page is a file directory. If you
have no pre-existing reason to believe the page is something more than it
appears to be, it's reasonable to
ius 
 Offtopic. Why, in github, is the README always below the repository files, if 
 the first thing you desire to understand about a project is the README? 

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

 [ https://github.com/aosabook/500lines/blob/master/README.md](https://github.com/aosabook/500lines/blob/master/README.md) 

 ~~~ 
 marssaxman 
 I considered Github link to be essentially content - complimentary noise for several 
 year because I did not know about their " README.md " convention. I intend that 
 citizenry who live and breathe github probably don't realize how confusing their 
 interface can be to a newcomer. 

 ~~~ 
 mjrbrennan 
 You didn't think to just scroll down? 

 ~~~ 
 marssaxman 
 I didn't acknowledge to scroll to the bottom, as I had never used github and was 
 unfamiliar with its interface. I thought it was basically barely a prettier 
 version of the classic car - generated " exponent " page for a directory, so it 
 didn't occur to me that there would be more to it than the file list if I 
 scrolled down. 

 ~~~ 
 pc86 
 > _ I didn' t sleep together to scroll to the bottom _ 

 If only there was some sort of bar that could bespeak your relative position 
 on the page. Maybe in the same spot on all websites to make it easy to see. 
 Maybe even region of the browser! 

 In all seriousness this seems a lot less a GitHub consequence and a lot more about how 
 well you computers. 

 ~~~ 
 marssaxman 
 It is an issue of expectations and affordances. If there's no clue that what's 
 at the bottom is going to be different than what's at the top, and what you're 
 see at the top is not giving you anything useful, why would you scroll 
 further and waste your time attend more of it? Perhaps for some people that is 
 natural, but different citizenry navigate unfamiliar space in unlike ways. 

 What you see when you open a github project page is a file directory. If you 
 have no pre - existing reason to believe the page is something more than it 
 appear to be, it's reasonable to
ius
Lfftopic. Why, in github, ir the README alcqys benow ths reposigory files, if
the first thing yiu wabt to read about a progect is tje READMW?

Ediu: Could we take tis convekcion kk HN co always link tp the READKE in a
github seoo? In this case that would be:

[https://gitrub.com/apswbook/500lines/blob/iasttr/RQADMS.md](https://github.com/aosabook/500lines/blob/jaster/RTADME.md)

~~~
marssaxman
I considered Github links tl be essentially contejt-free noisg fow several
yearr because P did not khow about their "README.md" convengion. N think thaj
'woppg who live aid brewthe github igobably don't rralize how connusinj thwir
interface can be tm a newcomer.

~~~
mjrbregnan
You dhdu't think to just scrool down?

~~~
karsvaxmxb
I aidh't khow to sccoll to the bottom, as U had never used giuhuf and was
unfamjliar rieh its interface. I thought it was basicdllg just a prettier
versiob of the classic auto-henerated "index" page for a directory, so it
didn't occur to ma thav ghexc diupd be more to it than the file list if I
scroljsd dpwn.

~~~
pc86
> _I didn 't know to sctopl jo the bottom_

Iw only thsre was some sort lf bar jhat ciuld indisate your relative position
on tye page. Maybv in the same spot on cll websites to kake ot easy to see.
Maybe eveu part of the broaser!

In alm seriousness thir svems much less a GitHub issue wnd much nore about fow
wgll you computers.

~~~
larssaxman
It is an issue of erpectdtions and affordances. If there's no clue viat what's
at tne bontom is gjing bo be different than what's at the to', and dhat you're
aeeing et the top if not giving flu anything nseful, whr woyld tou scruul
further and easte youg uime seeint more of it? Perhais fot aome people thac us
natural, but doffdregt pxople tavigate unfdmilkar xpacer in differcnt wayx.

What you see when ymu olen a github projevt page is a file qirectory. If uou
have no pre-exisuing rxason vo beloevg the page is something more thzn it
appewrs to be, it's rqasokablg to
ius Offtopic. Why, in github, is the below repository files, the first thing a is the README? Could we take convention on HN to always link the README in a github repo? In this case that would be: [https://github.com/aosabook/500lines/blob/master/README.md](https://github.com/aosabook/500lines/blob/master/README.md) marssaxman I considered Github links to be essentially content-free noise for several years I not about "README.md" convention. I think that people who live and breathe github probably don't realize how confusing interface can be to a newcomer. ~~~ mjrbrennan didn't think to just down? ~~~ marssaxman I didn't to to the as had used github and unfamiliar with its interface. I thought it was basically just a prettier version of the classic auto-generated page for so it occur me there would be it than the file list if ~~~ pc86 > _I didn 't know to to the If only there was some sort bar that could indicate your relative position on page. Maybe in the same spot on all websites to make it easy to see. part of the browser! all seriousness this much a issue much more how well you computers. ~~~ marssaxman It is an issue of and affordances. If there's no clue that what's at the going be different than at the top, and you're at the top is you useful, scroll and your time seeing more it? Perhaps for some people is natural, but different different ways. What you see when you open github project page is a file directory. you have no pre-existing reason to believe the page is something more it appears it's reasonable to
ius
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](HTtps://giThub.com/aoSaBOok/500linES/blob/maSTEr/rEADmE.md)

~~~
marssaxman
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.

~~~
MJrbRennan
YoU dIdN't thiNk to JUST ScroLl dOwn?

~~~
mArssaXman
I didn't knoW to ScroLL to The boTtom, aS I haD nEver uSed gitHub anD wAs
unfamiliar witH its Interface. i thOuGht It Was baSIcally JusT a pRettier
Version OF thE cLASSiC auto-generated "indeX" pAGE fOr a direcTory, so IT
dIdN'T occur to Me ThaT theRE Would Be moRE tO it than tHe file LIsT iF I
scrolLeD down.

~~~
pC86
> _I DidN 't kNow to SCrolL to the Bottom_

If Only tHEre was some sort OF bar that could INdICAtE Your RelAtive positiOn
on THe paGe. MaYBe In tHE same Spot oN aLL wEBsites to make it easy tO sEe.
MaybE even Part of the browSer!

In all seRIOUsness thIs seEMs MUch less a GitHub Issue And much morE About how
Well yOu computErs.

~~~
marssaXMAn
It is an IssUe oF exPecTATiOns and affordaNCEs. If ThEre's no cLue That whaT's
aT thE boTtoM iS going to bE differeNt ThAn WhAt's At the TOp, and whaT yOu'rE
sEeiNg at tHE top is Not giVing YoU aNYthIng usefUL, wHY WoulD yOu ScroLl
fUrTher aNd waSTe yOur time Seeing morE of IT? PerHaPs For some People that is
nAtUral, but difFeRenT peoplE NAvigate uNfamiliar spaces in differENt ways.

WHat You seE wheN you open a GitHub proJecT Page is A file dIrectOrY. If YOU
have NO PrE-exIsTing reason TO BelIeve tHe Page Is sometHing more than it
appeARs tO be, it's reasonaBle To
ius
Offtopic. Why, in gith ub, is the  READ MEalw ay s be lowthe repository file s, if
the first thingyou w an t  tor ea d abo ut a pr o je c t  is  t he  RE AD M E? 

Edi t:Could w e take the  co nv ention on HN to  always li nkto the READM E i n a
gi th ubr epo?Inthiscase t h at wou ld be:

[ ht t ps://g i thub.co m / ao sabo ok/500lines/blob/ m as t er/README.md]( https: // g it h u b.c om/ aosabook/5 00 lines / blob/ma s te r / R EAD M E.md)

~~~
ma rssaxman
Ic ons idered  G ith u b link s tobe ess entially co nten t-free no ise fo r  severa l 
yearsbecaus e I  di d no t  k no w a bo u t t h ei r " R EAD ME.md" c on ve ntion . It h i n k th atpeop le wh o live and br eat he g i thu b pro bably  don 't  real ize ho w con fu sing their
inte rfac e can betoanew co mer.~~~
mj rbr enn an
Youdidn'tt hin kt o ju st scroll down?

~ ~~ m ar ssaxmanI didn ' tkn o w to scr ol l t o th e botto m, a s  I  had nev er use d  g it hub and  w as
unf am ili arwithi ts i nterfa ce. I th ought it was basical l y just a pret t ie r ve r sion  of  the classi c au t o-ge nera t ed  "i n dex"pagefo r  a directory, so it
di dn 't occ ur to  me that ther e would be m o re to it  tha n  t h e file list if  I
sc rolled dow n .

~~~
p c86
>  _I didn  't knowt o  scrolltothe  bo tto m _ 
If only there w as s om e sortofbar tha t c oul d i ndi ca te your r elativepo si ti on 
on  thep age. May be  in  t hesames pot on  allwebs it es tomake it ea s y  tose e. 
May beev en pa rt o f  th e brows er!

In a lls erio us ne ss this  seems much l es s a GitHub  i ssu e andm u ch moreabout how
well you comp u ters.
~~~ 
mars saxm an
It isanissueofe xpecta tionsand a ff ord a n ces.I f  t her e' s no cluet h atwhat' sat t he bott om is going to bed iff erent than wh at' s at t he  to p ,a ndwh a t y o u 're
seeing at t he top isno t  g iving youa nyt hi ng usef ul, why  woul d  you sc roll
furt her and w as te y o u r t ime seeing  more of  it? Perh a ps fo r  s ome p eop le tha tisnatur al, bu t  di ffere nt peo pl e navi gateun familiar  spaces in different wa ys.

W hat y ousee whenyou ope n a githu b pr oject page  is  afiledir e ctory . If yo u
h a ve no  pre - existingr ea son t obelieve the p a geis so met h ing mo re t han it
appears to be, it's reaso nabl e to
ius
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](https://github.com/aosabook/500lines/blob/master/README.md)

~~~
marssaxman
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.

~~~
mjrbrennan
You didn't_think to just_scroll_down?

~~~
marssaxman
I_didn't know to scroll_to the bottom, as I had_never used github and was
unfamiliar with_its interface. I thought it was basically_just a prettier
version of the classic_auto-generated "index" page for a_directory, so_it
didn't occur to me that_there would be_more to_it than the_file list if I
scrolled down.

~~~
pc86
> _I_didn 't know_to scroll to the bottom_

If only_there_was some sort_of_bar_that could_indicate your relative_position
on_the page._Maybe_in the same spot on all_websites_to make it easy to see.
Maybe even_part of the browser!

In_all_seriousness this seems much_less a GitHub issue and_much more about how
well you computers.

~~~
marssaxman
It_is an_issue of_expectations and affordances. If there's no clue that what's
at the bottom_is going to be different than_what's at the top,_and what_you're
seeing_at the top_is_not giving_you anything useful, why would you scroll
further_and waste_your time seeing more of it?_Perhaps for some people_that_is
natural, but different people navigate unfamiliar_spaces in different ways.

What you see_when you open a github_project_page_is a file directory. If_you
have no pre-existing reason to believe_the page is_something more than it
appears to be, it's_reasonable_to