Universal JavaScript
Michael Jackson

I like the name and definitely agree with the “why” — but the designation is a whole other thing. Originally, the term “Isomorphic Javascript” was exactly concerned only with the same JS code running in both the client and the server. The context you are suggesting is different and far broader than Charlie Robbins’s original definition. Regardless of Robbins’s choice of words and whether we can live with it or nay, I can’t see how running JS code in my teapot and my car tire relates to the programming paradigm of running the same code on both the server and client. Whole different terms for whole different topics.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.