3 ms·
Not being JS, and therefore not having to deal with all the traps that it contains is a pretty big point of difference. It also provides a boost to other langu
by FridgeSeal 6y ago
Not being JS, and therefore not having to deal with all the traps that it contains is a pretty big point of difference.
It also provides a boost to other languages, which I think is good, there's no really good reason why JS should continue to be the only browser 'blessed' language.
- root_axis 6y ago> therefore not having to deal with all the traps that it contains is a pretty big point of difference. The primary complaint expressed regarding front-end churn is that the landscape is confusing because there is too much tooling and too many options and that they're unnecessary and that people should just use JS, if you're saying "not having to deal" with js is a positive thing then you're implicitly saying "churn" is not a problem since "not having to deal with js" is the only reason that "churn" exists in the first place. Either "churn" is bad and something like rust-to-web is another example of unnecessary tools complicating the landscape or tooling that helps to avoid the warts of js is a good thing and "churn" is a non-issue; you can't have it both ways.