r/scala • • Sep 03 '20

Announcing Cats 2.2.0

Thumbnail
github.com
0 Upvotes

r/scala • • Nov 15 '21

Typelevel: On Recent Events

Thumbnail
typelevel.org
0 Upvotes

r/scala • • Mar 09 '23

I want to pursue a career in Scala but there is so much politics

24 Upvotes

When great speakers are banned from conferences just because they are uncomfortable it’s not good. People have different opinions about the future direction of Scala but it’s so infected. It’s better to be inclusive and allow people with different opinions. But I guess today’s cancel culture has won. But it hurts the Scala community especially when it really needs to show a good light. Java is becoming much better and heaps of developers are adopting Kotlin and TypeScript.

Scala 3 is such a great language and it’s such a shame that things like this destroys the image of the Scala community.

I work as a software architect and have great influence over technical choices. I take lots of factors in to consideration when technologies are chosen. Community is one of them.

Let people have different opinions and don’t cancel people just because you don’t agree with them. Try to set the bar high and don’t let feelings control you or your organisation.


r/scala • • Aug 15 '25

It's not pretty! Using ChatGPT 5 to help undo a wrongful cancellation from the Scala community

Thumbnail pretty.direct
0 Upvotes

Jon Pretty used ChatGPT 5 to perform forensic, neutral analysis of thousands of private messages, in order to counter false claims made against him by two ex-partners, which led to his cancellation from the Scala community in 2021.


r/scala • • Jan 22 '16

Here's why Scala sucks

7 Upvotes

Here's why Scala sucks...

In short, it completely and utterly fails to even begin to apply either the principle that "there is only one best way to do something [syntactically]" or the principle of least surprise or the principle that explicit is better than implicit.

For my style guide, please see... https://www.reddit.com/r/scala/comments/42eg68/scala_style_for_idiots_and_amateurs/


Small example...

def doSomething():Unit = {...}
def doSomething:Unit = {...}
def doSomething() = {...}
def doSomething = {...}
def doSomething() {...}
def doSomething {...}

MyClass.doSomething
MyClass.doSomething()
MyClass doSomething()
MyClass.doSomething(param)
MyClass doSomething(param)
MyClass doSomething param

^ Too many different ways. How do we know which one to use? Oh, right. We have to read a 200 page book and learn the Scala conventions over a series of many months. Personally, I know a lot of people who don't like reading 200 page books in order to use a tool. Side note: whose idea was it to replace the word "void", meaning "emptiness", with the word "Unit", meaning "a unit of measurement" (I know that's not what they meant, but that's what comes to mind when you say the word "unit")?

def addMe(a: Int, b: Int): Int = { a + b }
def function1(intThing: => Int): Int = { 2 + intThing }
def function2(intThing: Int): Int = { 2 + intThing }

val sum: Int = addMe(1,2)
function1( addMe(1,2) )
function2( sum )

^ This reminds me of pass-by-reference vs. pass-by-value in C++. Instead of just picking the more intuitive one or the one that is less verbose (i.e. just making all functions take in method calls instead of executing them first), the user has to figure out the meaning of the ":<=" symbol as used in this context. And when they go to the search engine and type in "meaning of :<= in Scala" the first thing that pops up [for me] is ( http://docs.scala-lang.org/tutorials/FAQ/finding-symbols.html ), a guide that DOES NOT EXPLAIN THE MEANING OF THIS SYMBOL. Yes I know that it's ": <=" not ":<=", but it looks like ":<=".

DO NOT DEFINE SYMBOLS WITHOUT A JAVADOC. I DO NOT KNOW WHAT <>|<> MEANS.


val map1 = Map( 1->2, 2->4, 3->6 )
val map2 = Map( (1,2), (2, 4), (3, 6) )

^ These are exactly the same thing. Couldn't you just pick one and make it the only option?

val list1 = List(1,2,3,4)

val list2 = list1.map( element => element*2 )
val list3 = list2.map( _*2 ) // Do we really need another use for "_" ?

^ Did you know that there are over 12 different uses for the underscore symbol in Scala? Seriously? Over 12 different meaning for THE EXACT SAME SYMBOL. This list is ridiculous: http://stackoverflow.com/questions/8000903/what-are-all-the-uses-of-an-underscore-in-scala. How is that not complicated?

Also, the underscore is not just a stylistic concern. It's also a type inference concern. Let's say you have a line of code that takes in a function like " _ == 'text' ". The compiler cannot infer whether "_" is a String or an Int, but you pass that function in place of a parameter that expects a function that takes in an int, so the compiler infers indirectly that underscore must be type int. All good.

But what happens when you need to re-use that function somewhere else and so you pull that function out of the parameter position and assign it to a variable? Well that variable isn't going to have the right type signature anymore and so when you try to pass it back into the original param, the code won't compile and will throw a weird type error.

In essence, this:

doSomething( _ == "text" )

Is not equivalent to this:

val func = ( _ == "text" )
doSomething( func )

I don't know about you, but I find this behavior surprising.

Note that this:

doSomething( (myJSON: String) => myJSON == "text" )

is the same thing as this:

val func = ( (myJSON: String) => myJSON == "text" )
doSomething( func )

Much better

-- Speaking of symbols, there are FAR too many symbols in the Scala language. So many that they almost collide with one another. And the problem with symbols is unlike with function names, you cannot Google symbols to see what they mean (I mean you can try, but it doesn't always work as well). Beginners cannot sound them out in their heads. And they surprise programmers coming from other languages (like the -> function).

-- The arrows in Scala don't behave the way you would expect. Normally if you see (a -> b), you would expect that to mean "a goes to b" and normally if you then see (a <- b), you would expect that to mean the opposite. But it doesn't. (a -> b) and (a <- b) aren't the same and they aren't the opposite of one another. They are COMPLETELY DIFFERENT THINGS. Same with <: and :> and >: and <= and => and >= and =<. How is that not confusing? This programming language fails when it comes to "the principle of least surprise".

-- Another example: implicits. Scala implicits suck dependencies into functions from god knows where. I see an implicit and it's like magic - I have no idea where that variable is coming from and I cannot right-click on it to find out ([correction: in IntelliJ IDE you can click the function and press "ctrl+Shift+p" to see the implicits]). Stuck using IntelliJ, though, with its slow auto-complete. Unless you have a computer that is less than 5 years old, you're pretty much screwed when it comes to responsive auto-complete and what not.

-- Also, the language is so big that you should probably be using a linter. I mean you have the null keyword pulled in from Java which you should never ever use. You have case classes which require the programmer to manually make them "final" because there is not point not doing so - it's not like they can inherit from one another anyway. You can make case classes mutable which kinda defeats the functional nature of case class. The context of the language is highly nuanced and over-complicated. It could be less complicated and have the same functionality and readability (and be quicker to compile), but it is not.

-- Also, the language is hard to read. When I read Python my eyes start on the left side of the page and they move to the right. When I read English my eyes start on the left side of the page and move to the right. When I read nested Scala "Singleton1 { Singleton2 { Singleton3 { x.do {...} } } }" curly brace functions it's like reading Lisp - hard to tell what is data and what is a function. Ugh. My eyes go inside the innermost curly brace and are going out and going back. This is not how human were trained to read.

-- All in all, the bigger the language, the more careful it must be to keep from becoming bloated or unwieldy. And that's just what Scala is. Bloated and unweildy. Going into the future, this is what Scala needs. Simplicity and minimalism. One way of doing things. For better or for worst, Scala has a lot to learn from Python.


r/scala • • Jul 21 '20

JdG sues Travis Brown for defamation

Thumbnail
twitter.com
0 Upvotes

r/scala • • Aug 26 '19

Scala Almost Succeeded

Thumbnail
medium.com
17 Upvotes

r/scala • • Nov 18 '21

A statement about my Scala open source work(travis)

Thumbnail meta.plasm.us
0 Upvotes

r/scala • • Mar 22 '21

Scala is a Maintenance Nightmare - MungingData

Thumbnail
mungingdata.com
0 Upvotes

r/scala • • Mar 19 '20

Is it a sin to mention Scala's weakness here?

1 Upvotes

Here is a well argued, respectful, non trolling perspective of someone's experience with Scala.

https://www.reddit.com/r/scala/comments/fkncgs/if_haskell_was_a_first_class_language_on_the_jvm/fkv6mct/

A perspective that also mirrors my own experience in the field; but that is besides the point.

The main point here is the amount of down voting that post has received. I have started to notice this mob down voting in response to anyone pointing out the weakness of Scala on this sub, and I think it is unhealthy.

I personally think it is far healthier to point out where you think someone might be making logical fallacies than lazy down voting.


r/scala • • Apr 09 '24

I can nor understand how implicits are useful

5 Upvotes

My new job uses scala 2, so I'm trying to learn it fairly quickly. Implicits are shit. I don't understand how they are useful. Like with implicit parameters...why the hell not just include all the arguments? Why are you leaving shit out to be picked up implicitly? This is just making the code insanely hard to read quickly


r/scala • • Oct 09 '20

[Meta] Homework posts?

2 Upvotes

Can we do something about this sub mods? Like 50% of the posts are homework questions. And almost none of them are related to scala besides syntax errors

I get it's an "academic" language but come on it gets old seeing people ask how to use map or val instead of var for the Nth time


r/scala • • Jan 28 '12

Scala's version fragility makes the Enterprise argument near impossible

Thumbnail
goodstuff.im
1 Upvotes

r/scala • • Apr 02 '24

Wow this language sucks to learn

0 Upvotes

Started a new job that primarily uses scala. Was told no one here really knew it before starting either, so it should be fine. But...wow. been a week and I still feel totally lost with a bunch of concepts. And frequently it feels like the language was designed for maximum non readability

Coming from previous c/c++/java/python professional background


r/scala • • Dec 06 '17

Quora: Is Scala going to take off?

Thumbnail
quora.com
0 Upvotes

r/scala • • Oct 06 '16

Why are Scala developers so rude?

0 Upvotes

My statement is purely based on my interaction with scala people on the web.

I have often seen on stackoverflow and even on reddit any questions posed by any noob are rubbished and criticized harshly. Only intermediate to tough questions are properly answered or taken seriously. This makes a very negative impact on a new learner/enthusiast like me. But in other subreddits of /r/python and /r/learnpython even for silly questions there are many guys who encourage new people in a great way and make the learning enjoyable!

I may be wrong and would it be better creating something like /r/learnscala?


r/scala • • Feb 28 '22

Hi guys, if someone is interested, there are two questions at the end of the article. It would be very helpful if you answer them :)

0 Upvotes

r/scala • • Jun 18 '14

Scala is faster than java

Thumbnail jto.github.io
4 Upvotes

r/scala • • Oct 21 '21

Mini-rant on the Scala community and Scala overspecialization.

2 Upvotes

So I love Scala. It's the kind of love that every time I try to explore some new language, Scala comes in the way whispering "this language lacks this and that".

I've tried Rust, Go, Kotlin, Clojure, and more. None of them is as awesome as Scala... And I'm good, really good actually.

(Yet... What's with Travis Brown? Holy fuck, is this guy's purpose in life is to slowly suffocating the community?)

Besides that... At some point it felt like it was evolving crazy fast. There was a new shiny amazing library to explore every month... And now there's just promises in the air and Scala 3 hasn't really taken off, and seems like it just won't.

There's also the job offers. From what I've seen, only some companies in Europe are hiring (mainly in the Netherlands), and the positions they offer are that of a Senior Scala Engineer with no possibility of growing.

Also, the speed in which the Scala ecosystem grew in the previous years left every company using Scala, having a mix of styles in their software. Some using Play, and then Akka, and then Http4s (with tagless final) and then ZIO and modern functional effects libraries.

I feel like I fell in a pit of overspecialization and now I can't leave.


r/scala • • Feb 12 '22

Programming in Scala, 5th Edition

0 Upvotes

Hello guys,
Where can I find a free dowload of "Programming in Scala, 5th Edition", I also have the VPN of my university (in Germany).
Thanks


r/scala • • Mar 04 '21

Is Java ever better than Scala

0 Upvotes

Is Java better for video games? Large scale graphics? Is there any reason to use/learn Java while Scala exists?


r/scala • • Aug 21 '17

Functional Programming and Modern DevOps: Aaron Contorer. With scathing critique of scala in production environment.

Thumbnail
youtu.be
3 Upvotes

r/scala • • Dec 30 '16

Is it only me or scala is a mess?

5 Upvotes

I'm new to scala (two weeks) but i have worked with Java for the last 10 years including Android. Is it me or Scala is a mess?

You have N ways to do things and it really confuses me. Example:

def doSomething():Unit = {...}
def doSomething:Unit = {...}
def doSomething() = {...}
def doSomething = {...}
def doSomething() {...}
def doSomething {...}

MyClass.doSomething
MyClass.doSomething()
MyClass doSomething()
MyClass.doSomething(param)
MyClass doSomething(param)
MyClass doSomething param

I mean, is there any standard for the language in general? Like Java?


r/scala • • Apr 26 '15

Interview Question: Reverse a linked-list (Scala solution)

Thumbnail
gist.github.com
0 Upvotes