yes man

no grain 🌾, no pain 🥖

[yes man @courieti]

@hytradboi dumb question : how to join the online conférence?

[yes man @courieti]

@guizmaii A Cargo cult ? 🙃🙃🙃

[yes man @courieti]

@GigaHugo @KieferGuillaume @DigitalGanon @dimitripavlenko Par curiosité, cette métrique, le SPA, prend en compte la capacité a acheter en dehors de l'UE ? ( typiquement des produit chinois ou americains )

[Noel Welsh: @noelwelsh.bsky & @[email protected] @noelwelsh]

No more monads! Direct-effects explained:

https://t.co/hOSIuCVoX0

I wrote up the what, why, and how of direct-style effects using Scala 3. It's a chonky piece but I think it's reasonably comprehensive as a result.

[Jon Pretty @propensive]

A Statement
I am a Scala developer and speaker who was cancelled three years ago. Yesterday I attended the High Court in London to hear an apology from several prominent members of the Scala community for making untrue claims about me on 27 April 2021. I sued them for libel, and they admitted fault and settled, paying me costs and damages.

Their allegations were sensational and squalid, but unfounded. Their source was the resentment of one woman following a relationship in 2018, which I ended against her wishes. She fabricated or was offered an alternative narrative, which developed into claims of a pattern of behaviour, and culminated in the defendants’ publication of an open letter, which they now agree is defamatory.

In two years of legal action, the defendants never presented any evidence to support their allegations, and admitted in court that they had no proper reason to make them. They have given undertakings to the court not to publish further or similar defamatory statements, or have anyone else do so on their behalf.

No signatory contacted me about the allegations before publication. I received no warning, and had no knowledge of the claims’ substance. I only discovered what I was accused of at the same time as I learned of my indefinite exclusion from the community; at the same time everyone else found out. I had no opportunity to defend myself. It is no coincidence that the absence of due process led to an abject injustice.

The experience of cancellation and enduring the online hysteria was traumatic. I responded by withdrawing from the life I knew. Its consequences hurt me and people close to me, and have been immiserating.

My employment opportunities were obliterated. My charitable and educational projects, and my small business, could not continue. Despite my transferable skills, the allegations were a transferrable red flag recognised across programming communities and industries, and I have barely earned a living since. It has taken two years of legal action to receive fair scrutiny in a forum reliant on facts. This outcome finally vindicates me.

Many familiar with the open letter will be surprised by this outcome, given the certainty expressed by some of the letter’s supporters. But they should question why no defence of my libel claim was ever offered. They should seek answers for how so many people became so convinced without evidence. And the defendants’ co-signatories should reassess the credibility of everything that compelled them to support the open letter.

Nonetheless, I believe the open letter’s authors were convinced it was the right thing to do. I believe that they wished to show their kindness in response to a story which shocked them. Many of them I have known for years, and know to be good, moral people who were mistaken, and would not wish to be mistaken.

Good people can make mistakes, without becoming bad people. So, I offer them the respect and compassion I believe they deserve. I recognise their good intent, and I interpret its consequences charitably. We owe each other civility in ceding the time and space necessary to reflect upon this in open enquiry, without coercion or urgency, so everyone can reach a better understanding of this outcome, and of one another.

I have avoided naming any third parties here, and I urge others to do the same. I know too well how it feels to be the subject of online harassment, and I do not wish it upon anyone. I reject the culture of blame and escalation.

I have not been idle since 2021. I’ve spent much of my time writing Scala 3, which I believe is an exceptional platform for software development, and deserves far greater success. I am motivated to be part of that success, and I will start sharing my work again soon.

https://t.co/MKp5qukWh8

[yes man @courieti]

@JulienTruffaut @Esteban08240516 deezer of course !

[Scala Space @ScalaSpace]

The Scala 3 compiler will have a new home soon! 🏡
It will be hosted on GitHub as scala/scala3 starting tomorrow.

[yes man @courieti]

@fwbrasil @adamwarski What is kyo?

[yes man @courieti]

@NicolasRinaudo It’s my exact usecase I use to explain usage of value classes to new commer ^^

[Lucie Alexandre @LucyAlexandre]

J’étais dans ce bar hier avant, pendant, et après. J’ai hésité à le raconter ici parce que je n’y étais pas du tout en tant que journaliste, mais simplement pour boire des coups avec des potes. Mais après réflexion ça vaut peut être quand même la peine d’être relaté ⤵️

[yes man @courieti]

@jeromegodefroy @fanf42 @BFMTV @CNEWS @LCI C’est la version livre action de ou est charlie?

[yes man @courieti]

@ScalaWilliam The fuck is scalaPy ?

[yes man @courieti]

@fwbrasil Look like scala syntax but I dont reconise de > in the type définition

[John A De Goes @jdegoes]

Programming language mascots, as designed by GPT-4 and Midjourney 4.

1/n

[juan @juanbuis]

it's about time we update some of the classics for the french market https://t.co/92b0XXmVch

[yes man @courieti]

I annoyed by this #catseffect Sync that extends BracketThrowable.
Why implement Bracket in such way if all error type are in rallity allway a Throwable ?

[Igal Tabachnik @hmemcpy]

@kubukoz Yes, using a real IDE

[yes man @courieti]

@Bottlaeric @princertitude Tricher a super mario

[John A De Goes @jdegoes]

Your app runs inside the JVM...

...which runs inside Docker...

...which runs inside Kubernetes...

...which runs on KVM...

...which runs on Linux...

...which runs on bare metal.

Truly elastic, edge-friendly, cloud-native computing requires rethinking this stack.