A very good question, and my answer to that is; "Does it make my job easier?"
If the answer is yes, it's a good thing, at least within the space from where I'm looking at it. This is one of the things we're struggling with at Aista, implying people look at our stuff and ask themselves if it can do everything their existing platform(s) and language(es) can do, at which point the answer obviously is no. However, its purpose is not to solve everything, its purpose is to make parts of our jobs easier, which it delivers by among other things allowing people to extremely rapidly create backend administration types of apps, from where they can control what their database contains, in addition to that it easily allows for rapidly creating micro services and micro "apps" (if that's a word?) taking control over and simplifying some parts of their jobs.
No paradigm, platform or language solves everything, even though JavaScript made a run for it with NodeJS (and painfully failed may I add). What we need is for the great ideas to "bubble up" naturally by themselves, without religious zealots having fallen in love with some particular tech stack, because they've spent years learning it, and it's provided a stable and secure income for them for some specific domain within software development. The latter unfortunately is the status quo, which makes it very hard and difficult to ensure that the best ideas "wins" ...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
When looking at a new paradigm, do you have a method for evaluating if it is useful and what parts of it are superfluous?
A very good question, and my answer to that is; "Does it make my job easier?"
If the answer is yes, it's a good thing, at least within the space from where I'm looking at it. This is one of the things we're struggling with at Aista, implying people look at our stuff and ask themselves if it can do everything their existing platform(s) and language(es) can do, at which point the answer obviously is no. However, its purpose is not to solve everything, its purpose is to make parts of our jobs easier, which it delivers by among other things allowing people to extremely rapidly create backend administration types of apps, from where they can control what their database contains, in addition to that it easily allows for rapidly creating micro services and micro "apps" (if that's a word?) taking control over and simplifying some parts of their jobs.
No paradigm, platform or language solves everything, even though JavaScript made a run for it with NodeJS (and painfully failed may I add). What we need is for the great ideas to "bubble up" naturally by themselves, without religious zealots having fallen in love with some particular tech stack, because they've spent years learning it, and it's provided a stable and secure income for them for some specific domain within software development. The latter unfortunately is the status quo, which makes it very hard and difficult to ensure that the best ideas "wins" ...