I think the concept itself is ridiculous. It's 2013 guys, UI response should be instant. If it's not, you need to rethink what you're doing and ponder your life in general.
You're right that we should all strive to build UI that responds instantly. Unfortunately sometimes, for reasons out of a designers control there might be a legitimate reason for a site to reach that level - for that, adding a subtle progress bar does help.
Think of it as a local optimisation before you reach a global one of instant UI.
Are you implying that the author would have better spent his time redesigning HTTP rather than making this library? Because to me, that is even more ridiculous.
But it is not instant. This is used when you are making an external HTTP request over the Internet, to a server that may or may not respond instantly (if at all), over a link that may be saturated at any point in time.
First of all, HTML and CSS is not coding, and second it won't result in a 'serviceable website' as sites need to be dynamic these days, and you won't get paid for a static website anyway. This is a bad post and the author should feel bad.
I kind of feel bad that the switch from "learn to code" to "why schools work" was so jarring. I definitely need to do a better job making it a bit more skim-able. But I definitely don't feel bad about advising people to start learning to code by learning HTML and CSS if their goal is to eventually learn to build web-apps.
It certainly is coding in the most literal sense of writing code to be interpreted by a computer, although it's not a programming language. You are correct about that. Nevertheless, it's a great starting place for beginners.
You definitely can get paid for building static websites. Somehow I did.
Thanks for the good article. It definitely resonates with me and I will be trying to develop some habits in the next 30 days (every day). I am certainly not an absolute beginner (I know some html and css)but I am not a programmer at all and your article gives me some food for thought as I embark on learning a bit about javascript.
What? Did you read the whole article? An excerpt: "all roads lead to HTML and CSS... Once you understand that, then you can move on to Javascript, Ruby, Python, or whatever else you want."
It is the opposite of logical because that would be doing it ass backwards. You don't need to learn HTML, your web app that you make while, you know, actually learning how to code, will generate it. Prettifying it with some CSS can be googled after you have something that actually works and has a purpose.
