It is hard to take the author seriously, or as an authority, when he rejects materialism and states something like "Physical death is merely a de-clenching of awareness", and he believes in the afterlife.
WARNING: HYPERBOLIC CLICKBAIT. No substance, no informed critique or examples. The headline leads one to believe that there would be a thoughtful analysis, maybe pointing to some sociological research, that illustrates why javascript has gained so much popularity in recent years. Instead, it is a weak protest.
Seems like the "Mods" flagged this as it dropped off of the home page. I used Sacha Greif's http://www.telescopeapp.org in an effort to demonstrate how we can take advantage of open source projects to promote the common good through civic participation.
The goal is to create a prioritized list so that citizens can work together toward those policies initiatives in a concerted, coordinated way regardless of party affiliation. It doesn't have to be an echo chamber if others have substantive ideas. And it is just an experiment.
You might do just fine substituting archetype with template. The readme for https://github.com/electrode-io/electrode-archetype-react-ap... reads: "This "app archetype" provides for common patterns across all app projects so that each app project can standardize on common development behavior and patterns. Its essentially pre-made patterns for build scripts." "A pre-made pattern" sounds a lot like a template. The majority of the documentation focuses on applied concepts, with familiar terms. The only reference to archetypes is found in the first paragraph of What is Electrode, and I think it distracts and confuses more than it helps. If it is a core concept, then it might be good to link to https://github.com/FormidableLabs/builder, but I don't yet see where or if builder is included as part of electrode.
Completely valid. I should have been more direct, but that wasn't the intent. Since you took the bait, I take issue with the seemingly flipant manner in which words are assigned new meanings, and existing concepts are relabeled. While the concept of archetypes is intellectually really fun to consider, it makes more difficult the ultimate project of speaking a common tongue. This is not an orthodox point of view, this is primarily economical. Far too much cognitive effort is required to learn new paradigms that turn out to be fresh takes on old ones, so best to identify them early and move on. But we should be critical as a community to self-regulate, as the marginal utility of each moment of learning is weighed against a million other potentialities.
That was really well crafted, thank you. Much easier to digest than some of the docs. Though, I'm still not convinced it warrants a new way of describing a collection of patterns for various concerns, e.g. a framework.
That was really well crafted, thank you. Much easier to digest than some of the docs. Though, I'm still not convinced it warrants a new way of describing a collection of patterns for various concerns, e.g. a framework.
I'll grant this is a subtle point, but why did you choose to use the word "archetype", borrowing a term to describe what most understand to be generated boilerplate code? Why not call it a framework, or an app generator? Why did you, collectively I will assume, choose to assign a new term to an existing concept?