If your function takes inputs then it's not stateless, technically. Maybe you mean "side-effect free" in which case I think you can make class components side-effect free as well and the distinction disappears.
In the context of React “Stateless Functional Component (SFC)” is actually the correct term. There is a documented difference between properties and state. While all components in React may take input, that input is always referred to as properties. State is specifically data that a component manages internally. SFCs are thus named due to their inability to possess/manage state.
Technically, one could return a closure and manage state in a SFC, but that would be unusual.
Touché. Typically, the nomenclature I see around this is “stateless functional components” so I figured i’d stick with it.
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.
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.
What do you mean by side effect free?
I mean it doesn't print to console, write to a file, increment some variable somewhere, etc. The output depends only on the inputs.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.