eed3si9n, 2 months ago

@vascorsd per 2022 'Long-term compatibility plans for Scala 3' [1], #Scala 3 mimics the post-2017 'Forward Faster' Java approach, wherein few times a year there will be a Scala Next release with language features, while keeping the binary compatibility with Scala 3.0; and every 2 years or so a Long-Term Support (LTS) release, which promises to be patched for 3 years, analogous to Java 8, 11, 17, etc

so books should ignore non-LTSes?
[1]: https://www.scala-lang.org/blog/2022/08/17/long-term-compatibility-plans.html
[2]: https://mreinhold.org/blog/forward-faster

vascorsd, 2 months ago (edited 2 months ago)

When specific syntax like "given .. with..." was suggested a lot of people complained and said that it was a new weird way and to think about another way. The "given" is ok, but the "with" was ugly and should be unneeded...

But no, it went forward.

Now the new pre sip talks about it being ugly and we should change it 🙃🙃😮‍💨

vascorsd, 2 months ago

But let's introduce yet another way to do things with a newer syntax with random arrows in it!

"given [A: Ord] => [Ord[List[A]] as listOrd"

"because more intuitive"

Yeah, I agree.

But it's too late because it's yet another fucking way to write stuff.

Yet another thing to need to know how to read.

Yet another thing that newcomers will not know.

Yet another thing to explain and "what is the correct way"

Yet...

Just accept how it is now!

🤬😡😮‍💨

vascorsd, 2 months ago

And as usual all of this will go through and no matter the complaints or "the talks" about it, since "the lord" has already decided on this path nobody can stop it.

It's as it always happens.

These people cannot hear an "No to all of it" so nobody even tries to say it.

😒

Mgdtyyjff, 2 months ago

@vascorsd whatsapp