21–30 of 31 posts
Should I start learning scala or typescript? I'm developing nodejs + angularjs apps in my spare time and want to improve the code (native JavaScript 5 currently). Or should I start with babel and ES6?
Babel and ES6 should be fine too.
Should I start learning scala or typescript? I'm developing nodejs + angularjs apps in my spare time and want to improve the code (native JavaScript 5 currently). Or should I start with babel and ES6?
But typescript will get you most of the "quick wins" of type safety and is very easy to migrate to, so it's probably a better choice in the short and medium term (at least in terms of immediate productivity).
Speaking of bringing nice languages to the browser. Kotlin is a simpler language than Scala and also compiles to JS. Unlike Scala.JS which seems to be a completely third party project, Kotlin's compilation to JS is considered one of the primary features of the language. Kotlin is barely at 1.0 at the moment though.
Scala.js uses much of the scala compiler infrastructure and is worked on by many of the same people; while typesafe doesn't support it commercially it's hardly "completely third party".
Should I start learning scala or typescript? I'm developing nodejs + angularjs apps in my spare time and want to improve the code (native JavaScript 5 currently). Or should I start with babel and ES6?
If you're in for the long haul (say 2+ years) I'd go with scala - it's ultimately a better language with a much more complete and powerful type system than typescript. It's also good to learn at least one functional language to pick up the functional techniques (which are ultimately valuable in any language), so if you've never learnt a functional language before I'd recommend it. But typescript will get you most of…
I'm more into a long haul so scala sounds pretty cool.
But what just rushed into my mind is that angular 2 will be in typescript so learning scala would only be relevant for server side code. And using two languages when one can handle both doesnt sound quite convicing :/ Would you still recommend scala when I want to work with angular 2 in the near future?
Should I start learning scala or typescript? I'm developing nodejs + angularjs apps in my spare time and want to improve the code (native JavaScript 5 currently). Or should I start with babel and ES6?
You could get a big improvement by switching to React :p Babel and ES6 should be fine too.
Do you think switching to react would be worth it? My angular pages are not very complex and I'm still relatively new to angular so switching could be possible.
Earlier quoted context omitted.
If you're in for the long haul (say 2+ years) I'd go with scala - it's ultimately a better language with a much more complete and powerful type system than typescript. It's also good to learn at least one functional language to pick up the functional techniques (which are ultimately valuable in any language), so if you've never learnt a functional language before I'd recommend it. But typescript will get you most of…
Thanks for your response :) I'm more into a long haul so scala sounds pretty cool. But what just rushed into my mind is that angular 2 will be in typescript so learning scala would only be relevant for server side code. And using two languages when one can handle both doesnt sound quite convicing :/ Would you still recommend scala when I want to work with angular 2 in the near future?
All that said, if you're thoroughly committed to Angular 2 (a mentality I don't really understand - I love Wicket but if an equally OO framework existed in native Scala then I'd use that instead) then using anything other than Typescript is probably an unnecessary risk factor.
Earlier quoted context omitted.
You could get a big improvement by switching to React :p Babel and ES6 should be fine too.
I started with angular and due to my limited spare time I simply dont have the time to learn both. I'm very interestend in React but focusing on angular (and angular 2 in the near future) sounds more promising (based on random articles and news). Do you think switching to react would be worth it? My angular pages are not very complex and I'm still relatively new to angular so switching could be possible.
For example, look at this: https://docs.angularjs.org/api/ng/directive/ngOptions
Why would you want to learn this kind of obscure syntax, just to make a simple select input (and still be limited in what you can do)? You don't need this kind of stuff in React because you build your views with pure Javascript and HTML.
Earlier quoted context omitted.
You could get a big improvement by switching to React :p Babel and ES6 should be fine too.
I started with angular and due to my limited spare time I simply dont have the time to learn both. I'm very interestend in React but focusing on angular (and angular 2 in the near future) sounds more promising (based on random articles and news). Do you think switching to react would be worth it? My angular pages are not very complex and I'm still relatively new to angular so switching could be possible.
It's not about Facebook - it's about the design that promotes "functionality" and modularity etc. That's the big deal.
Angular and Ember are both needlessly complicated to begin with, but even more so because of all the two-way state-mangling going on.
So yes, switching to React will be ever-increasingly worth it, because the benefits of not having to deal with Angular will keep compounding over time.
So instead of "opportunity costs", you'll have "opportunity benefits" :P
Earlier quoted context omitted.
180KB is comparable to a medium-size image.
Yes you are right. Scripting time however can be massive, take for instance this hs.fi (Finnish daily), they have 354kB of JavaScript, but scripting time with Skylake 6700K is 1.13 seconds of the page load. With Q6600 it was 3.5 seconds. With latest chrome it's easy to measure scripting time as pie chart. Go to "Timeline" tab of developer tools and hit F5. (just few releases back one had to do it manually by starting…
Earlier quoted context omitted.
AFAIK javascript support is put on hold until 1.0 is reached. Kotlin/JS doesn't provide much help to make Kotlin/Java code run without modifications. So, it isn't there yet. ScalaJS on the other hand is fully functional.
Correct me if I'm wrong, but I think the relationship of Java and JS in ScalaJS and Kotlin is about the same: If your Scala/Kotlin code depends on any Java classes, you won't be able to compile it to JS. You can only compile pure Scala/Kotlin code to JS (and that comes with a few caveats in both cases). It's true that Kotlin's JS support is pretty raw today. There are virtually no docs for it for example. They do hav…
Kotlin relies more heavily on the underlying runtime. Unless they re-implement a large part of the Java standard library in JS, they'll never achieve that level of compatibility.