GH addresses...just me, or utterly non-nonsensical

Can some more enlightened individual please explain how GH spits out list addresses? It doesn't seem to follow any sense whatsoever, making any attempt at parametric modelling an endeavour I have decided to coin 'smart-idiot' until proven otherwise. 

For example i have the following input:

1. A circle

2. points on that circle (from divide curve). 

Output address of the points: {0;0}

Firstly, what does that mean? I.e in c# i'm familar with lists represented as {0,0} meaning if i want to extract an item from that list, it is as simple as myList[0] etc. In GH that isnt the case. Why isn't its address {0} i.e a list of points with 'tree index' of 0?

Secondly, how does this address system even work? It seems to pluck these sequences out of some kind of secretive GH ether? I know with tree components its possible to control this somewhat, but its so convoluted and requires constant manual adjustment if certain dependencies change. Is there no control of list addresses from the off set? I've been using hoopsnake, and the never-ending address lengths which get longer and longer as it cycles is a joke. Is GH parametric software or semi-parametric because currently I feel short-changed? I'm even more aggrieved when I realise that if i do want to do more sophisticated definitions in GH, or have greater control over lists/trees, the scripting components are the only option, thus rendering the whole advantage of GH's visual programming utterly useless. Salvation please...