Demystifying Scala • Kelley Robinson • GOTO 2017

[@antonnovo695]

Introduction to Programming and Problem-Solving with Scala is how I started. Great book.

[@MarcusHammarberg]

Great stuff! I wished I had this as my intro. Thanks a lot.

[@adhamehab5222]

I know I'm a little late but this is an excellent talk, one of the best I ever watched. Thanks a lot!

[@catmcloughlin927]

Thank you Kelley, this was a very useful and informative talk! I especially appreciated the overview of why people use/like Scala as well as the downsides to some of its features.

[@EdouardTavinor]

Thanks for this talk. It was really positive to hear a very qualified person give an honest appraisal of scala.

[@ricardofilipegomes4396]

What a beautifull talk!!!! Started learning FP out of curiosity, i am ending up writing much more beautifull and elegant code all around, and this talk open my mind to a lot of new ideas on how to approach some things i hated and been looking to solve, exceptions as an error message always bothered my mind Thanks a lot for helping people becoming better :)

[@OurFallenHereos37055]

The java partition example isn't exactly a fair comparison considering we have the streams api and vavr. Scala still looks much more succinct though.

[@karenschwarze6391]

Fantastic. Thank you for presenting this information.

[@mostafaismail5256]

a very helpful introduction, thanks alot

[@leftover7766]

No links to Coursera starts or any others promised. Or am I missing something. Found them easy enough though.

[@oleksiyprosyanko7772]

Try to find job in Scala outsourcing and consider whether to invests in studying Scala.

[@WolvesLink1395]

Just one thing with the val barefootContessa = "Ina Garten" The data within the variable can be changed if you reassign it using val barefootContessa again. However if you do this: barefootContessa = "Jim" You will get a reassignment error. So, to clarify: The data is immutable. val barefootContessa = "Jim" will change the data barefootContessa = "Jim" will give you a reassignment error

[@jpzhang8290]

Very logical presentation

[@iterativeincremental]

Uh nice intro. I will give Scala a shot. Encouraging talk

[@WilliamSnale]

thanks for the info, great talk!

[@grzkv]

Apparently, Scala is supposed to be mysterious :)

[@NinjaDoge]

for my test function i did: def Quick_Maths(x: Int, y: Int, z: Int): Int = { var Operation: Int = x+y; println(x.toString + " + " + y.toString + " is " + Operation.toString) println("minus "+z.toString + " thats " + (Operation - z).toString + ", quick maths") Operation -= z; Operation }

[@legoman777777777]

The ting goes skkkrrraaa

[@vram288]

at 12.0 good

[@jimnewton4534]

I really like the way Kelley approaches the topic. It seems to be a pragmatic point of view based on experience dealing with real people and teams of people. I agree with many of her points about which things are confusing to people. But I disagree with her also about her perspective of Java. For example, she assumes that people are familiar with Java. This may be true in her experience, but it is not true in general. Many things could and should be explained without bringing Java into the equation. And the Java ecosystem DOES NOT make things easier, it makes things very complicated, ands a huge amount of boiler plating. I see it as an unfortunate vestige of our evolution, not as the jewel of our civilisation.

[@SpiritOfIndiaaa]

Kelly is very nice

[@teckyify]

Scala is a minefield, it has super suptle buggy behaviours and with Java 9 it's dead anyways. I go rather for correctness than crazy unpredictable covariant type inference.

[@tactlessturtle]

I've worked with scala for years and I don't share that opinion of the language. What in your experience makes it a minefield?

[@mill7319]

Scala tends to be more "correct" than Java, mostly in terms of it's type system.

[@sosoga1977]

>I go rather for correctnes >writes java instead of scala :D