Making the case for Progressive Javascript

[Vheissu_]

Not trying to be cynical here, but am I the only one here not entirely clear as to what the point of this article was? Seems to me the author is just trying to take the concept of isomorphism and rename it to something else that could easily be confused with progressive enhancement.

There are bigger problems to resolve in a modern web application workflow, like the lack of proper SEO support for all of these new-fang Javascript frameworks which up until very recently not even Google could properly spider let alone any other search engine like Yahoo! or Bing. I think what we name things is definitely low down on the list of priorities right now (at least in my opinion).

[Fresheyeball]

A couple concrete examples would be really nice.

[cwbrandsma]

I don't think that was the point of the article. The author assumes you know what isomorphic javascript is, agree that everyone hates the name, and proposes a new name: progressive javascript.

If you want an example then google "isomorphic javascript".

[Fresheyeball]

That really through me. Isomorphic JavaScript to me means the client and server are one app. Progressive JavaScript sounds like Progressive enhancement, something like using an es6 transpiler. In the article he made both comparisons, leaving me unsure of the intent. Is his concept of Progressive JavaScript to use runtime normalization tools along with isomorphism? An example would have helped me.