Re:JavaScript Is Bad
by johnisgood on Tuesday August 27, 2019 @07:19AM
(#20808330)
Complaining is recognizing that there is an issue. This article is trying to raise awareness of some issues. It is a start! I do not think that not providing a solution to all (or some) issues invalidates anything that has been said. Having a solution is not a necessity. I may point out flaws in a system, but I do not need to have a solution ready for it, do I? The flaws exist, with or without a solution.
[ Parent
| on HN ]
We've been stuck in this for at least a decade now. That is what I am referring to with "I am not satisfied with the status quo of the discussion".
The author of this specific article doesn't even seem to consider that there may be non-technical factors at play that cannot be fixed by coming up with (yet) a better language.
It's the same over and over again, unfortunately.
Re:JavaScript Is Bad
by smallnamespace on Tuesday August 27, 2019 @07:29AM
(#20808403)
The discussion never resolves, and will never resolve, because the participants aren't the same people - there's literally a constant influx of new, inexperienced developers facing the same issues in a slightly new context (and hence using new language to describe it).
For another example, just go to Reddit's front page. It's the same trendy questions from young people a decade earlier as well.
You'll know an online community is on the path to dissolution when it can 'resolve' problems for good.
The same applies to HN: I'm sure my point has been made many times before, and will be made many times again here.
Re:JavaScript Is Bad
by johnisgood on Tuesday August 27, 2019 @07:25AM
(#20808377)
Well yes, I agree, I would like to brainstorm potential solutions to the issues at hand, too.