I had a similar experience. Between the ages of 14-16 I tinkered on my own sphere shard with a friend of mine. I didn't realise what I was doing was programming until I took courses 16-17 and realised what I had been doing the whole time :)
There was one website, Taran's Scripting For Dummies, that was pretty much my bible.
Just a quick comment on the spamfest side of things. Disclaimer that I never got into LoL. I've found over the years playing most of the different MOBAs that when I come into a new one I find it nearly impossible to delineate what is happening in a many-player fight. It only comes after some time playing the game that I'm able to recognise this shade of light in this pattern means this spell is being used, etc. After a point it becomes quite clear what is going on and looks a lot less like a spamfest.
And that is the barrier of entry to MOBA eSports. Also the reason why LOL is the number one eSport is because it is the number on game in the world. Not only that but it is the biggest video game the world has seen.
I think the distinction the grandparent made was they would be happy to see the trait in the leader of the country, not that seeing the trait makes a good leader.
If I recall correctly from the last time I had to deal with this, it's the first 3 towns on the Eyre highway in WA coming from the SA border. This[1] suggests there are actually 4.
I can't speak for the OP, only my experience here. The docs on flux[1] recommend singletons for the dispatcher and stores. If your library is following that recommendation then things start breaking in a server-side environment as multiple requests start hitting, especially in parallel with asynchronous data retrieval.
The default included polyfills tend to cover most things in my experience. I haven't had to worry about if a feature exists in IE8 or if we're polyfillng it for a while now, it's great.
Actually the markdown page on his site mentions exactly that as markdown's intention.
> The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions. While Markdown’s syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown’s syntax is the format of plain text email.
I'm stretching my memory a little but I think there was an Indiana Jones game using what I vaguely recognised at the time as the same engine, which I have equally fond memories of!
> we can make the number of columns depend on the available space, so that a narrow screen will have one column, a wider screen will have two columns, etc. This is all it takes to specify that the optimal line length is 15em and for the number of columns to be calculated accordingly
It looks like the columns property can take a size value, which the browser will use to work out how many columns it can fit.
Wouldn't this leave a bunch of white space on one side if the screen width is not an exact multiple of that size? That doesn't seem like a good solution to me.
There was one website, Taran's Scripting For Dummies, that was pretty much my bible.