4 ms·
I'm tempted to rewrite your comment using s/Scala/JavaScript/g and then wager it would still make perfect sense. I've recently had to bootstrap an Angular proje
by maxaf 11y ago
I'm tempted to rewrite your comment using s/Scala/JavaScript/g and then wager it would still make perfect sense. I've recently had to bootstrap an Angular project using nothing but pure JS and some Sass. This isn't my first in-browser UI, but the first after a long break from heavy front-end development.
My impression is that the quality of tools in the JS world is so damn low, that they're more of a hindrance than help. Gluing together Grunt, Sass, Bower, NPM, Browserify, Uglify and a bunch of internal libraries was a titanic task.
By contrast, in the Scala world tools are easier to reason about, fail more cleanly and usually surface problems at compile/build time.
- saosebastiao 11y agoTrust me...I absolutely prefer scala as a language. I love almost everything about it (except maybe SBT, but it's tolerable). It pains me to know that the TS compiler is catching only a fraction of the problems that Scala could. But ultimately anything I write has to end up as javascript, and the community just isn't there to support it, so I end up having to deal with javascript regardless. And yes, the js tools are loathsome in general. I've found Typescript to be the best tool available to me, and webpack is pretty good as well. Everything else I've been able to cut out thankfully.
- maxaf 11y agoOh, webpack is a great example of my frustration: I suspect it might be better than browserify for my needs, but I'm already so shell-shocked from adopting browserify at work that I no longer have the nerve to disturb the house of cards that I've built here. Thus webpack will have to wait. Anyway, I hear you, although the only way to make Scala.js work better for everyone is to use it. Otherwise building a community is an insurmountable chicken-and-egg problem.