4 ms·

Also: Scala, TypeScript, F#

43224gg252 9y ago
I've only used Scala and TypeScript. TypeScript is crap compared to Go. It's yet another abstraction layer on top of javascript and it's much slower and even more difficult to program with than Go. There's no point in using TS when Go is there. Scala is yet another language running on a JVM and its syntax is almost as bad and clumsy as Java. Most benchmarks put it on par with Go in terms of performance. I just don't see a point in using these languages when Go is just as capable, more simple, compiled to binaries (and can even run on bare metal in some cases), runs on more platforms, has much better editor support, and is just more fun to use in general.
- Others 9y ago
  Scala has its problems, but it is not anywhere near as clumsy as Java. Where Scala falls flat is implicitness, an overabundance of features, and extreamly dense syntax for very high levels of abstraction. Its syntax is actually quite nice, with relatively few warts. I find it a joy to write, and very fluid.
  - c_shu 9y ago
    Scala is too complicated. It reminds me of C++. But C++ is fast. People use it probably when performance is their first priority. For practical reasons I just bear with C++. Use it as necessary. I would rather not bear with another complicated language, unless there are compelling reasons. I think it's unlikely that Scala can be useful to me in the near future, because there are so many good alternatives.
ice109 9y ago
>Scala functional language with hoards of issues >TypeScript javascript >F# essentially vendor locked to windows
- moogly 9y ago
  >>F# >essentially vendor locked to windows If you by "essentially" mean "not at all". You've been able to run F# on Mono for ages, and now you can run it on either Mono or .NET Core.
  - fiedzia 9y ago
    > You've been able to run F# on Mono for ages But you wouldn't want to, because for a very long time Mono was horribly buggy, and no library or application cared for supporting it. It may be better now in terms of .Net itself, I am not sure how it looks like in terms of community support for non-windows usage.
  - ice109 9y ago
    i have a running f#/mono environment on this computer. on my other computer i cannot get it to work. things like this https://stackoverflow.com/a/41578645/6767912 https://stackoverflow.com/a/41578645/6767912 and this https://github.com/NuGet/Home/issues/2880 https://github.com/NuGet/Home/issues/2880 tells me it's not production ready (yes i've even tried compiling mono from source).

I've only used Scala and TypeScript. TypeScript is crap compared to Go. It's yet another abstraction layer on top of javascript and it's much slower and even more difficult to program with than Go. There's no point in using TS when Go is there. Scala is yet another language running on a JVM and its syntax is almost as bad and clumsy as Java. Most benchmarks put it on par with Go in terms of performance. I just don't see a point in using these languages when Go is just as capable, more simple, compiled to binaries (and can even run on bare metal in some cases), runs on more platforms, has much better editor support, and is just more fun to use in general.

Others 9y ago
Scala has its problems, but it is not anywhere near as clumsy as Java. Where Scala falls flat is implicitness, an overabundance of features, and extreamly dense syntax for very high levels of abstraction. Its syntax is actually quite nice, with relatively few warts. I find it a joy to write, and very fluid.
- c_shu 9y ago
  Scala is too complicated. It reminds me of C++. But C++ is fast. People use it probably when performance is their first priority. For practical reasons I just bear with C++. Use it as necessary. I would rather not bear with another complicated language, unless there are compelling reasons. I think it's unlikely that Scala can be useful to me in the near future, because there are so many good alternatives.

ice109 9y ago

>Scala functional language with hoards of issues >TypeScript javascript >F# essentially vendor locked to windows

moogly 9y ago
>>F# >essentially vendor locked to windows If you by "essentially" mean "not at all". You've been able to run F# on Mono for ages, and now you can run it on either Mono or .NET Core.
- fiedzia 9y ago
  > You've been able to run F# on Mono for ages But you wouldn't want to, because for a very long time Mono was horribly buggy, and no library or application cared for supporting it. It may be better now in terms of .Net itself, I am not sure how it looks like in terms of community support for non-windows usage.
- ice109 9y ago
  i have a running f#/mono environment on this computer. on my other computer i cannot get it to work. things like this https://stackoverflow.com/a/41578645/6767912 https://stackoverflow.com/a/41578645/6767912 and this https://github.com/NuGet/Home/issues/2880 https://github.com/NuGet/Home/issues/2880 tells me it's not production ready (yes i've even tried compiling mono from source).