re: Class Components vs. Stateless Functional Components VIEW POST

VIEW PARENT COMMENT VIEW FULL DISCUSSION
 

I can sometimes be a stickler for precise technical language so don't mind me. The JavaScript ecosystem gave us "isomorphic JavaScript" which to this day I don't understand.

Sticking to community nomenclature is fine if that's what the community has settled on.

Isomorphic just means 'same shape's so it should be the same shape code on both server and client.

I know what the word means formally. I studied pure math in college and grad school. The word is poorly chosen for what it means in the JavaScript ecosystem. They should have used "portable" instead of co-opting a formal mathematical term.

Hey, that's great — not doubting you. Portable tends to be used for software that doesn't need to be recompiled for different machines.

No words going to be perfect though.

code of conduct - report abuse