shaneckel

I find this to be relatively true in my interactions here.

Some people want to be left alone in their html `pages` club where they check for errors in the w3c validator. Some people want to make the browser usurp native applications and become the baseline for user interactions.

I don't look back at the 90's with rose-colored glasses. Web was often overlooked and we were considered 2nd rate citizens among `real` software developers. These days, the browser is a competitive alternative to native and it was years of struggle to get here. Over taking a decade of "web" understanding and convincing people that "web" is capable of more than just html.

The web is made up of people's decisions and their technology choices they choose to use. Which is basically written in every alistapart article since 1999. So let's not sit in nostalgia. Push forward with better technology because this thinking only makes it harder for those that invent and struggling for adoption from `thought leaders` who wish the world was just a series of hyperlinked XML pages.

As a yinzer, this is really fun to read.

It depends on your perspective. If you're building an application that passes disjointed components around, then yes, you can combine the three (js,html,css) into a self reliant container. If you're building a website that is basically a series of pages, that is part of a book per say, then it doesn't quite make sense. I would say 10 years ago it was not common to think of the web as a platform. Over the last 5 years using the dom as platform and js as the source code has become much more predominant.

Whether the scope of your business can be used by this architecture would determine whether it would come up in your day to day.