• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Tim Cooke
  • Junilu Lacar
  • Rob Spoor
  • Devaka Cooray
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • Tim Holloway
  • Jj Roberts
  • Al Hobbs
  • Piet Souris

scala 3 vs Java 15? 16?

Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
H Dean,

It looks like java/oracle has been on a war path releasing java every 6 / 18 months.
how do you contrast the new java features that are getting into Java with that of scala 3.
Is java functional enough. Is there a good article that contrasts scala 3 vs Java 16.
Whats your personal take on this.

Posts: 23
Mac OS X Scala Monad
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Off hand, I can't think of a good resource that compares the features of the two languages like that. It would be great to have! Java has been evolving more quickly the last so many years, which is great. The language team even admits they've borrowed ideas from Scala and other languages. Adding lambdas in Java 8 was a massive step forward, IMHO.

Java still has quite a ways to go to be at feature parity with Scala, although that's not a goal for Java. The Java community works harder than the Scala community to retain backwards compatibility unless breakage is absolutely unavoidable. Brian Goetz, the language architect, has handled this masterfully. The Scala community, on the other hand, is more tolerant of changes (well, most of us are ;).

Hence, Java has some idiosyncrasies due to its history, in the type system and how you use types, in the limited form in pattern matching (case expressions) vs. Scala's, and other things that reflect backwards compatibility constraints. That said, a lot of organizations have decided that Java is a better fit for their needs. I respect that, even though it's not what I would do ;)

-- Dean
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic