Always interesting to hear Martin Odersky's talks. I liked this one: "cats blows it out of the water..." at 15:59. Hit the nail on the head, so to speak. Scala as a language is a very fine language and like a lot of people I learnt it from the wonderful MOOCs given by Martin. The main gripe I've always had is the tooling around it. Martin of course mentions "sbt". In comparison, I can fire up vim or emacs and be very productive in C++, Rust, Haskell in pretty short order. Not so with Scala: there's sbt, bloop, metals and so on and they never quite work well together and something always ends up going wrong distracting from the main activity of writing code. Top notch tooling and less language features would have made Scala more successful IMHO.
Funny how Martin equates pure FP with being complex. Taken to the extreme, absolutely yes it is complex. Any paradigm or approach is complex when taken to the extreme. However when used judiciously (especially using a functional core, imperative shell approach), I’d argue that it is much simpler than the alternatives.
Great talk, leading back to Scalas strength in combining functional AND imperative programming. Whereas Scala has been taken over more and more by the FP folks the last few years which I didn’t like because both worlds having their advantages and disadvantages. Great move with Caprese. I am really looking forward to it. 👍
How do you guys came up with measuring the programming languages grammar size mentioned in the slide at [03:25]? Do you have the comparison including other programming languages like JavaScript, etc? Thanks!
Most of the suggestions from this video simply means use Java or Kotlin :/ Most stuffs that I associate with Scala are being said as discouraged... Am I the only one?
Yes and no. He's saying to use context to determine when to use the higher abstractions, that you can write good code without having to overcomplicate things. Aka, some devs will use object oriented design regardless of the use case while others will use functional design regardless use case due to dogmatic reasons when in reality they should be picking the tool that works the best for the case.
People went bananas with Scala early on. Most business requirements aren't very complex and pretty dull, but they still threw all sorts of advanced concepts at simple tasks just for the enjoyment of it and to gain knowledge. No one needs to learn Category Theory in order to understand something as simple as an http route. Yea many cool features utterly misused.
IMO he's trying to say that people are using Scala's properties to adhere to dogmatic principles which isn't necessary or a good idea. Coming from a mainly pythonic background, I always felt this way about Scala, but it has the ability to be very readable and elegant while preserving its functional ideologies.
There is a good "awesome scala" list ... and it turns out most of the linked projects are abandoned. Scala is clearly on the way out, but you can still get jobs maintaining legacy. In Job listings Scala has really fallen behind, and most of the time I see it mentioned as an alternative, like "we use Python but we would hire someone with experience in Java, C# or Scala". For startups, Scala is a complete no-go. You won't be able to hire people, even though the job offerings are so scarce. Most people that know Scala prefer to work with something else these days, but that's not the folks you get listening to Odersky rant about other languages or how most of the Scala community is messing up Scala.
And what programming language gives you the ergonomics of Scala 3 current features but in a way simpler language that composes those features with much simpler primitives? Also i doubt you actually watched the whole talk.
there is a library in Scala3 specifically crafted for Hardware electronics design Chisel and SpinalHDL, the main challenge in Scala is to get something effective productive and manageable using high level testable description. Still evaluating how all of this can fit for an Electronic Engineer where the main focus is not writing software tout court.
martin should never be allowed to touch another programming language. Same thing with C++ bjarne. two professors that have no real world experience, creating PAIN in the industry.
Always interesting to hear Martin Odersky's talks. I liked this one: "cats blows it out of the water..." at 15:59. Hit the nail on the head, so to speak. Scala as a language is a very fine language and like a lot of people I learnt it from the wonderful MOOCs given by Martin. The main gripe I've always had is the tooling around it. Martin of course mentions "sbt". In comparison, I can fire up vim or emacs and be very productive in C++, Rust, Haskell in pretty short order. Not so with Scala: there's sbt, bloop, metals and so on and they never quite work well together and something always ends up going wrong distracting from the main activity of writing code. Top notch tooling and less language features would have made Scala more successful IMHO.
I loved the common sense and pragmatism. Will retry approaching Scala 3 again soon!
Great talk and it's nice to see Martin focus on simplicity.
We just need to get everyone moved to Scala 3 ASAP so everyone can realise the benefits.
Bro is sporting a cartier tank, absolute boss.
Funny how Martin equates pure FP with being complex. Taken to the extreme, absolutely yes it is complex. Any paradigm or approach is complex when taken to the extreme.
However when used judiciously (especially using a functional core, imperative shell approach), I’d argue that it is much simpler than the alternatives.
Great talk, leading back to Scalas strength in combining functional AND imperative programming. Whereas Scala has been taken over more and more by the FP folks the last few years which I didn’t like because both worlds having their advantages and disadvantages. Great move with Caprese. I am really looking forward to it. 👍
How do you guys came up with measuring the programming languages grammar size mentioned in the slide at [03:25]? Do you have the comparison including other programming languages like JavaScript, etc? Thanks!
Great talk
Scala is fun
I'm hoping so.
great talk! 👏
lol, even the people creating the coding languages are copying and pasting stuff they don't understand from the web... 25:30
Most of the suggestions from this video simply means use Java or Kotlin :/ Most stuffs that I associate with Scala are being said as discouraged... Am I the only one?
Yes and no. He's saying to use context to determine when to use the higher abstractions, that you can write good code without having to overcomplicate things. Aka, some devs will use object oriented design regardless of the use case while others will use functional design regardless use case due to dogmatic reasons when in reality they should be picking the tool that works the best for the case.
People went bananas with Scala early on. Most business requirements aren't very complex and pretty dull, but they still threw all sorts of advanced concepts at simple tasks just for the enjoyment of it and to gain knowledge. No one needs to learn Category Theory in order to understand something as simple as an http route. Yea many cool features utterly misused.
@@TJ-hs1qm that's the story of software in general. Overcomplicating a problem without having an adequate reason to do so.
IMO he's trying to say that people are using Scala's properties to adhere to dogmatic principles which isn't necessary or a good idea. Coming from a mainly pythonic background, I always felt this way about Scala, but it has the ability to be very readable and elegant while preserving its functional ideologies.
There is a good "awesome scala" list ... and it turns out most of the linked projects are abandoned. Scala is clearly on the way out, but you can still get jobs maintaining legacy. In Job listings Scala has really fallen behind, and most of the time I see it mentioned as an alternative, like "we use Python but we would hire someone with experience in Java, C# or Scala". For startups, Scala is a complete no-go. You won't be able to hire people, even though the job offerings are so scarce. Most people that know Scala prefer to work with something else these days, but that's not the folks you get listening to Odersky rant about other languages or how most of the Scala community is messing up Scala.
As someone who handled complex code in scala I can say that it's not a simple language. Not by a long shot. 1:38
And what programming language gives you the ergonomics of Scala 3 current features but in a way simpler language that composes those features with much simpler primitives?
Also i doubt you actually watched the whole talk.
@@encapsulatio Shut it fanboy.
there is a library in Scala3 specifically crafted for Hardware electronics design Chisel and SpinalHDL, the main challenge in Scala is to get something effective productive and manageable using high level testable description. Still evaluating how all of this can fit for an Electronic Engineer where the main focus is not writing software tout court.
martin should never be allowed to touch another programming language. Same thing with C++ bjarne. two professors that have no real world experience, creating PAIN in the industry.
I agree.
😂