Earlier quoted context omitted.
When?
Scalas insane generic type system would be an example of them going wrong. The current proposed Go method seems fairly reasonable.
Scala’s type system goes far beyond simple generics.
The Road to Scala 3
121–130 of 196 posts
Re: The Road to Scala 3
#122Earlier quoted context omitted.
Scalas insane generic type system would be an example of them going wrong. The current proposed Go method seems fairly reasonable.
Scala’s type system goes far beyond simple generics.
and thats fine in an academic setting, but please don't bring that into the real world unless you have a really good use case.
Re: The Road to Scala 3
#123Earlier quoted context omitted.
Nowhere near as good or as seamless as Kotlin interop, Kotlin made interop a priority/first class feature. When using a Java library in Clojure, many times its just better to just write some Java for your Clojure program specifically for the purpose of calling it from Clojure.
> When using a Java library in Clojure, many times its just better to just write some Java for your Clojure program specifically for the purpose of calling it from Clojure. What? Calling Java from Clojure couldn't be any easier. The same as calling JavasScript from ClojureScript
From Cursive's author
https://old.reddit.com/r/Clojure/comments/5twabp/new_clojuri...
Re: The Road to Scala 3
#124Earlier quoted context omitted.
Nowhere near as good or as seamless as Kotlin interop, Kotlin made interop a priority/first class feature. When using a Java library in Clojure, many times its just better to just write some Java for your Clojure program specifically for the purpose of calling it from Clojure.
In what sort of situations have you needed to write more Java to use a Java library from Clojure? I've never felt the need to do this. It's sometimes helpful to write a Clojure wrapper for a Java library on order to use it in a more Clojure-y way.
From Cursive's author
https://old.reddit.com/r/Clojure/comments/5twabp/new_clojuri...
Re: The Road to Scala 3
#125Earlier quoted context omitted.
Nowhere near as good or as seamless as Kotlin interop, Kotlin made interop a priority/first class feature. When using a Java library in Clojure, many times its just better to just write some Java for your Clojure program specifically for the purpose of calling it from Clojure.
That hasn't been my experience. I've always been able to make use of Java libraries directly from Clojure in a straightforward way. In fact, sometimes I joke it's easier to do Java in Clojure than in Java Can you describe the kind of situations that you faced issues in? P.S.: Also, Clojure has first class interop... It's a part of its fudamental design.
From Cursive's author
https://old.reddit.com/r/Clojure/comments/5twabp/new_clojuri...
Re: The Road to Scala 3
#126To all those saying Scala is dying: Personally I am making top money on Scala gigs, and I don't see that changing anytime soon. The people I meet on these gigs share my opinion. Most people wouldn't take a Java job even if it paid more, same for Go or Node ( both of which I have used in production in the last month, and wouldn't take over Scala, with the exception of serverless) Teams in Media, Government and Finance…
I really don't see how people have trouble finding Scala jobs. All the respectable newish companies around me use Scala on the backend (old and large companies are unfortunately still stuck with Java and similar abominations). If someone wanted to hire me for a NodeJS, Python, Ruby or Java backend I would laugh at them.
Re: The Road to Scala 3
#127I love scala, and am very much looking forward to scala 3. For all the complaints about the language that always pop up in these threads: yes, the language lets you shoot yourself in the foot (with great power comes people who don’t apply it responsibly), but it’s precisely that power that makes it so useful and exceptional when judiciously applied. I like to say that scala is as if java and ruby had a love child and…
Scala 3 gets lots of discussion recently yet progress on Scala 2 matters too:
Spark on Scala 2.13 https://issues.apache.org/jira/browse/SPARK-25075
Scala 2 and the Java 9 Module System https://news.ycombinator.com/item?id=20912258
Re: The Road to Scala 3
#128To all those saying Scala is dying: Personally I am making top money on Scala gigs, and I don't see that changing anytime soon. The people I meet on these gigs share my opinion. Most people wouldn't take a Java job even if it paid more, same for Go or Node ( both of which I have used in production in the last month, and wouldn't take over Scala, with the exception of serverless) Teams in Media, Government and Finance…
>If you are a startup then Scala isn't a good fit. FAANG don't need to use Scala because.... Not a FANG, but close, Twitter is a huge Scala shop and was one of the first to run Scala workloads on GraalVM in production. Twitter’s Quest for a Wholly Graal Runtime by Chris Thalinger: https://www.youtube.com/watch?v=PtgKmzgIh4c
Twitter not only early adopted GraalVM but also open sourced the Reasonable Scala Compiler
https://github.com/twitter/rsc/commit/5d86ee2e2577684f49ce1f...
Definitely a large Scala shop.
Re: The Road to Scala 3
#129Earlier quoted context omitted.
Big ol’ “Citation Needed” on this one. The flip-side here is that a language that doesn’t support basic programming language theory concepts dooms its users to repeat the mistakes of those who discovered them. I also would personally disagree that any statically types language without generic types and without non-nullability (e.g. `Option`/`Maybe` and `Result`/`Either`) is severely lacking in the ability to express…
proof is in the pudding on that one, sorry don't think there are academics studying this but it's an obvious outcome from the war that was Go/Scala/Node. Go is eating Scalas lunch because its easy to understand and communities are stronger than individuals. Sure Scala has more 'features' but Rob Pike would say every feature has a cost and you need to weigh that, didn't see that ever happen in Scala. Go is taking the…
Go is one of the worst things to happen to the programming community in recent times, truly a 20 year step back that ignores practically everything we have learned about programming.
> Go is taking the time to get each piece right and I'm glad for it.
Have you ever taken a look at the error handling in Go standard libraries? Rob Pike is constantly badly reinventing monadic error handling patterns and doing it wrong; He even admitted to this himself.
Re: The Road to Scala 3
#130I was initially skeptical of Scala when I landed my first Scala gig a few years ago, but now I'm really glad I picked it. Simple things like pattern matching and immutability are amazing, and Implicits + Macros enables some awesome libraries like Shapeless[1], Chimney[2] which solves real business problems in a succinct and type-safe way. Very excited about what's coming in Scala 3 * Lots of improvements to make the…
Macros and their migration path to Scala 3 have been discussed at the Scala Center, EPFL
https://scala.epfl.ch/minutes/2018/12/05/december-5-2018.htm...