Re:Jaspy – A Python VM written in JavaScript
by ludamad on Saturday April 16, 2016 @09:02PM
(#11513022)
The extent to which all your points matter really depends, but I find myself able to use types just for some logic, and code in a functional style far removed from oldschool Java with lots of destructuring / structuring. I'm not denying it's a lipstick pig, but the improving-JavaScript situation is what it is, and it does a good job at doing it in an unopinionated way (which is why it's succeeding)
Re:Jaspy – A Python VM written in JavaScript
by mattmanser on Sunday April 17, 2016 @08:26AM
(#11514291)
It all matters a lot. There are great languages available today and typescript isn't one of them. Why should we be forced to choose sub par languages?
I don't see it as a long term solution. It's just the next coffeescript. It's part of the problem rather than a solution, the problem being the massive churn in the JS ecosystem as we desperately hunt for a way of writing JS code that isn't awful.
The actual solution is to give us other languages in the browser. We need Python or Ruby or Go or C# or PHP or whatever. We need real choice, not javascript 2.0.
If Firefox wanted to stay relevant today it could stop dogmatically promoting a broken language and that's what they'd be working on right now. They're too rigidly fixated on the past though.
And, ultimately, your code still ends up being a load of garbage boilerplate code like you're writing oldschool Java from the early 2000s.
It's a nasty language written on top of a nastier one, lipstick on a pig.