News for hackers. Stuff that matters.
Re:Isomorphic JavaScript with React and Node by jnmuel on Friday January 02, 2015 @03:50PM (#8828469)
It's essentially the opposite of polymorphism. Polymorphism says that if you look at the same thing in two different contexts you should get two different results. Isomorphism says that if you look at the same thing in two different contexts you should get the same thing. Here the contexts are server and client.
Re:Isomorphic JavaScript with React and Node by nox_ on Friday January 02, 2015 @05:56PM (#8829042)
In which universe is polymorphism the opposite of isomorphism? Couldn't we just have said "JavaScript that runs everywhere" instead of trying to sound educated?
Re:Isomorphic JavaScript with React and Node by aboodman on Friday January 02, 2015 @06:16PM (#8829125)
When you want to refer to the same concept over and over, it helps to give it a name.

Other examples: ajax, lamp, nosql, soa ... they may be buzzwords, but they are helpful. I don't see the problem here.

Re:Isomorphic JavaScript with React and Node by nox_ on Friday January 02, 2015 @07:16PM (#8829310)
Isomorphism was already a word before Nodejitsu abused it. Your examples are acronyms and abbreviations.

Nevermind that this concept is not even worth a name.

Re:Isomorphic JavaScript with React and Node by aboodman on Friday January 02, 2015 @09:47PM (#8829721)
It is common to repurpose words this way. I think it is called 'metaphor'. See also: half the names in technology and all nearly every apple product name.

Anyway, I find the term useful.

Re:Isomorphic JavaScript with React and Node by nox_ on Saturday January 03, 2015 @06:50AM (#8830550)
Metaphors make sense, that reusing of isomorphism doesn't, however you quote Greek words to justify your means.