@Cody Cig Are we talking about Andy or adam?

LOL

Sure :) I think one example would be the usage of symbolic operators, or over-reliance on such operators. Another would be that sometimes a mutable variable (`var`) is actually ok, as long as it's used locally - so local mutable state is often fine, global mutable state is where problems start. Yet another instance would be using too many implicits - for cases, where normal, "explicit" parameters work just as well - this might include dependency injection. That's not unique to Scala, btw. In Java, we had a similar history with learning (on own mistakes) not to over-use inheritance, for example.

He has written a long post comparing those: blog.softwaremill.com/scalaz-8-io-vs-akka-typed-actors-vs-monix-part-1-5672657169e1

That's a good question! But without a definite answer. Both Akka-Typed, Monix and ZIO are interesting technologies and learning them should be very valuable, not only because you are learning a new library, but because of the overall approach to concurrent/distributed programming that they represent. I think I would try assessing what are the use-cases for which you might end up needing a library like akka or monix or zio, and learning the one which has the highes probability of being used in practice.

Great! I'll read the blog post. Choose the first stack to study without know good/bad part is very hard.

I am just a Scala enthusiast, so maybe my opinion is not so useful, but I decided to start with Akka for two main reasons. 1 - It's easier to find books and other resources. 2 - It seems that Akka is more required in job descriptions in Poland (where I live) I had to start somewhere.

I'd definitely not recommend starting with Akka... It goes against the notion of functional programming in Scala (local reasoning, type-safety) and it's also way too powerful as a tool, meaning that you can apply it to anything, but eventually, it'll be a mess unless a substantial amount of work put into maintenance (which is also against FP notions)

Performance of the base language is comparable, but that depends more on the libraries that you use, rather than the language.

Sure, in the future that will be "the way". But currently Scala 3 is at version 3.0.0-M3, so for any production application, I would still recommend using Scala 2.

It compiles to the JVM, so it's there from the start.

Yes its 100% supported and used in production.

Sure, it's a fine art and you shouldn't be too concise, beyond comprehensibility. The difference with Scala is that you have the option to be concise and you have the option to create more advanced abstractions, unlike in other languages which often lack these capabilities or have them to a limited degree. Just like normal tools - an electric saw gives you much more possibilities than a hand saw, but hurting yourself is much easier as well.

+1

2 big banks in my country uses scala on their enterprise apps that handle very large sums of money by big clients

For everything you need. That is ok solvable on JVM or JS. Any task you like.t Any product you like. Mostly big apps. Like twitter and Spar. Also small frontend apps in JS or Backend services or WebApps.

Hm must be a slip of the tongue :) I don't know what native bytecode is either ;) What's the context, as I can't find where I mention that?

Essentially compiling it to a .exe file, so that it's specific to the platform and it doesn't require any third-party tools such as the JRE to run.

@@amrojjeh Well that's not bytecode anymore then.

@@SaHaRaSquad How come?

@@amrojjeh Bytecode is the term used for intermediary code prepared for VMs(like the Java VM) that's neither human-readable nor machine-readable(by the CPU). It can only be run by a compatible runtime environment. If you compile it to a normal executable file it's (native) machine code. So "native bytecode" isn't really a thing.

Isn't c++20 getting more readable tho?

Yes, and that dirty syntax makes my eyes wet with all those semicolons and return statements missing from my sight; it doesn't even look like code anymore.

This is not beginners video. There are other excellent sources on the internet for that.

I’ve never seen scala but have no issue with the presentation. You must be coming from js or some other front end framework, I use C and targeted assembly language. I forget that most developers probably don’t have a clue how to program, there is difference between someone who builds the tools vs people that use the tools.