Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Scala.js no longer experimental

scala-lang.org

Post reply on HN
Print view View original

131–135 of 135 posts

Re: Scala.js no longer experimental

#131

Post by facepalm »

rtpg wrote: post #106
facepalm wrote: post #104

Earlier quoted context omitted.

There just are programmers who feel static typing is the only correct way to program. Google has always been in that camp (company wide directive, I suppose). Meanwhile, most of the internet runs on PHP. I hope it will play out so that the statical types people can use something with statical types, and the dynamic types people can happily continue with their static types.

(disclaimer: super ultra pro-static-types person) I really wonder whether we won't get more conversion to static types. I think the popularity of dynamic typing languages is more due to the fact that static typing used to be a major pain. But with type inference being where it is, I think most languages can start moving to static typing without any costs to the users The biggest representation of this is all the Pyth…

I've learned Go by doing a MOOC on discrete optimization. Mostly, it was fine and fun. But eventually I switched back to JavaScript out of frustration because some things were simply too complicated.

Just look at the sorting library of Go. I don't think they have solved the problem of static types in a satisfactory way.

Re: Scala.js no longer experimental

#132

Post by frowaway001 »

kybernetikos wrote: post #129

> It’s mostly about the strong typing for me. Nothing revolutionary about that idea, but it’s just as true on the client as on the server: having the compiler type-check your code makes it much quicker to get complex, sophisticated systems up and running. I used to believe that this was obviously true. Then I went from doing a lot of programming in JS where even with a large codebase, I could see the code fail in sec…

Error highlighting is usually instantaneous.

Re: Scala.js no longer experimental

#133

Post by zackangelo »

the_af wrote: post #84
eweise wrote: post #78

Earlier quoted context omitted.

I program in Scala at work full time using Intellij and I'm having a great experience. No weird compilation errors, quick, responsive. Works almost as well as with Java files.

Awesome. My own experience is more with Scala IDE, which is terrible. I tried IntelliJ for a brief time last year, saw it had spurious compilation errors, and the gurus at my office told me it was even worse than Scala IDE (but you know how gurus are...). Out of curiosity: - Do you have incremental compilation enabled with IntelliJ? - Do you ever experience a compile error in the IDE for code that SBT is able to comp…

IntelliJ's Scala support has improved leaps and bounds the past 6 months. I'd give it another try if you have the opportunity.

Re: Scala.js no longer experimental

#134

Post by kybernetikos »

frowaway001 wrote: post #132
kybernetikos wrote: post #129

> It’s mostly about the strong typing for me. Nothing revolutionary about that idea, but it’s just as true on the client as on the server: having the compiler type-check your code makes it much quicker to get complex, sophisticated systems up and running. I used to believe that this was obviously true. Then I went from doing a lot of programming in JS where even with a large codebase, I could see the code fail in sec…

Error highlighting is usually instantaneous.

Not my experience in scala. I've had a lot of places where in the Scala plugin for intellij, it incorrectly highlights errors, or doesn't discover the error until a full build.

Re: Scala.js no longer experimental

#135

Post by CCs »

codygman wrote: post #107
CCs wrote: post #98

Earlier quoted context omitted.

I'm skeptical of any x-to-JS compiler as usually I end up debugging 2 different codes, where the second one is machine generated. After that you try to work around on the first to make the generated one do what you want. On the other hand the Scala people know how to write compilers. We're live, in production, with Scala since 2011 and it's a joy: it actually delivers what's promised. Heard the same thing from Twitte…

> debugging 2 different codes, where the second one is machine generated. After that you try to work around on the first to make the generated one do what you want. Please forgive me for the accusation, but I've heard many people say this same statement to later found out they just meant "Well it's never happened to me... but it could... but it happened to this person I know...". I personally can't think of many situ…

There's a difference between a lightweight transpiler like JSX and a compiler.

ClojureScript is pretty lightweight, but GWT and Scala.js compile process is not an easy one. Even Bootstrap.js optimization with Google Closure Compiler is an uphill battle. Try it with --compilation_level ADVANCED_OPTIMIZATIONS

Sourcemap does not help much with compiler bugs or if the compiler people have different opinion from you on how something should be translated.

Post reply on HN