A Tour of Scala VS Exercism - Scala Exercises

Martin Odersky is just a very nice guy and I get the impression that he isn't keen on saying "no", which is how you end up with a language that allows you to use xml tags inline (no longer supported in Scala 3),

https://github.com/scala/scala-xml/wiki/Getting-started

The "opinionated" Scala are the Typelevel and Zio stacks, which are very cool.

The problem with the "better Java" approach is that although it has helped Scala's growth a lot, it has also made it susceptible to Kotlin. The Scala code that doesn't use the advanced type magic can be straightforwardly rewritten in Kotlin instead. Kotlin also stops your bored developers from building neat type abstractions that no one else understands.

People who use Scala only has a "better Java" can now use Kotlin has a "better "better Java"".

https://github.com/scala/scala-xml/releases is now published separately from the main language.

Exercism

Nice, this reminds me of Exercism, which I wish was more widely known since they seem to be good folks. (disclaimer, I donate to them)

https://exercism.org/

Exercism, the free programming learning platform has initiated a challenge named: 48in24.

Last year, Exercism put together the #12in23 challenge. The goal was to learn a new programming language each month throughout the year. I was one of 135 people who completed the challenge, and I learned a lot along the way!

The list of languages contains every language on Exercism, excluding ones that I've used before, web languages, or ones that I can't download for some reason.

You might like https://exercism.org/

Learning by doing, with the help of mentors. Excellent way to learn a next language (as you are already familiar with the programming concepts).

Exercism is pretty good for beginners with some programming language, they are open source and worth contributing to.

Exercism

> it might be more sustainable if courses were stored in a version controllable medium to facilitate multiple collaborators

My initial thought was to actually use GitHub to store the content. Either on Markdown or JSON - to have some version control. I like how Exercism [1] does it. But I thought it would be hard for teachers - unfamiliar with Git - to update lessons.

Then, I thought about implementing a version control system for the project but I felt I was overcomplicating things for an MVP. But I like the idea of having some kind of version control to improve collaboration.

[1] https://exercism.org/