Oleg Nizhnik

@hmemcpy The problem is that variance is not that important. The important part is that it's Set-valued (or M-valued for M-enriched functors)

What's the problem?

@fwbrasil Sorry if our interaction somehow did it worse. I've never meant anything against you or the lib. Kyo is a great stuff. And people like @kitlangton and you are rare and extremely valuable in scala, especially in the macro-magic department.

Taking a break from Scala development Despite contributing to the Scala ecosystem for over a decade now, speaking at several conferences, two Scala Days, building Quill and more recently Kyo, I still face exclusion because the Scala Center's director decided to label me "clinically insane" for reporting harassment. Just recently, I had to deal with people aggressively questioning my mental health, a conference finding itself unable to enforce its own CoC, and a threat of a year-long ban from official forums. I was hoping I could cope with it while building Kyo but it's become unsustainable. The saddest part? I'm not alone. @propensive has faced much worse and we aren't even the only ones :( When institutional power is used to protect political agendas over community members, contributing becomes impossible. The same dynamics that drove out contributors through cancellation campaigns persist via different actors today. The Scala community has witnessed an extraordinary exodus of talented people over the recent years. Now you know why one more is stepping away: reporting harassment shouldn't result in mental health slurs from institutional leadership. Hopefully, I'll eventually find some inspiration to return. Kyo is fascinating, it'd be difficult to just leave it behind

@adamwarski @jdegoes @kitlangton @propensive Remember those times we used direct-style SM competitor to a renamed scalaz8 competitor to a renamed scalaz-streams competitor to a stdlib copy of twitter competitor to erlang processes? Man, what a time that was.

I'll assume that "SM releasing a ZIO competitor" is a reference to me working on Ox - if not, please correct me. If it is - the supposition that there's a connection between the (social) drama and the work on Ox, or my research of direct-style is false. I understand it fits your narrative, but sorry - there's nothing there! If you feel any of the technical arguments when it comes to comparing ZIO and alternatives are wrong or incomplete, I'll be happy to accept criticism and discuss on those grounds. All of that material is available publicly.

Why did this happen to @propensive? The short version is that Jon Pretty succeeded in angering the woke Scala bros -- principally the leaders of TL, but also various members of Scala Center and the scalac compiler team -- by attempting to play neutral in the many battles that followed the original LambdaConf "free speech" controversy. For one prominent example, Pretty refused to cancel me from Scala World, after Seth Tisue and Adriaan Moors made a coordinated attempt to cancel me from all Scala conferences. This marked a dramatic turn in the way the Scala Center related to Pretty and resulted in many individuals from TL officially promoting Pretty to a member of the outgroup. This was Pretty's original and fatal sin. For if he had not committed this particular sin, then everyone -- from the ringleader and original author of the Y letter -- to the initial set of signers, would have treated second-hand rumours of grumblings from a disgruntled ex-girlfriend the same way they treated a thousand other issues over the years. Instead, when Pretty became public enemy #2, then these second-hand rumours became the ember for a centrally coordinated effort to shape, even groom them into something that could be career-ending. If Pretty had made different decisions -- and here, I don't mean with Y and V, but with Scala politics -- then none of this would have happened. I suppose my involvement in this drama is at least partially why I have been so vocal about encouraging people to remove their signatures from the letter. I remember the exact moment when @djspiewak turned against Pretty. The three of us were sitting in a coffee shop, discussing Scala 3 and the future of Scala. Spiewak, who met with me only because Pretty was there (and organized Scala World, a coveted venue for Scala speakers), listened as Jon explained how we would each target different segments of the Scala 3 market. Jon would build an ecosystem rooted firmly in Scala 3, inspired by Python, and not purely functional -- so it didn't overlap with ZIO or TL. Spiewak was fine with that. But then Jon said that he would support my own effort to turn ZIO into the "Spring of Scala 3". Suddenly a look of abject disgust came over Spiewak's face, which he concealed only with some difficulty. From that moment onward, Spiewak's vote had already been cast. When Kit says, paraphrasing, "This could happen to me for choosing the wrong effect system," he's closer to the truth than most people could possibly imagine. The more history you understand, the more people in the community you know, the more horrifying the whole thing becomes. I could go on and on and tell more stories, some of which I was part of, and some of which I only know second hand. Stories that explain why everyone acted the way they did, why some have not removed their signatures and never will (they signed not because of compelling evidence or deep moral convictions, but to strike out at a perceived enemy). But I won't, at least not now. Because it's just too damn depressing, and what would be the point? Tragedies like this happens when little boys play like 'mean girls', only their egos are far bigger and their tactics far crueller. Justice and decency are casualties in a lustful quest for blood-soaked vengeance and retribution that knows no boundaries and ends only when one "side" or the other is utterly destroyed. Personal peace may come only if you accept that bitterness only poisons you (not the object of your bitterness), and if you deeply understand the meaning of, "'Vengeance is mine and I will repay,' says the Lord." There are some things in life that you cannot fix and that you must let go of, and this is one of those things. In any case, thanks to @kitlangton for all his magical educational and open-source contributions to the Scala community over the years and may his gifts enrich new ecosystems for many decades to come.

@kitlangton @fwbrasil With all due respect, Kyo still hasn't doc section about effect handling. `handle`rs are messy and undertypechecked. If "algebraic affects without PhD" means "use only 15 built-in effects, mark half of the code as Sync ", well, I guess, you won.

@fwbrasil Kyo has already lapped Caprese three times in terms of functionality and ergonomics. What's more, it works with the existing version of Scala 3! It doesn't need 6 years, 5 PHD students, and a new major version of Scala.

FYI I'm still banned from Scala's discord for having posted Jon's account of his cancellation. I've sent these questions to scala-contributors, let's hope I don't get banned there too🤞🏽 contributors.scala-lang.org/t/questions-re…

@guizmaii @odersky A lot of code relies on the fact that TupleN is a single known matchable class. The most used Tuple2 is already specialized on both sides. There was an epic project by @darkdimius targeting auto-specialization, which was possible thanks to the new IR (TASTy), but it's frozen.

.@odersky Why not just compiling Tuples to case classes? That'd avoid the code bloat of specialisation Each time the compiler finds a Tuple, it converts it to a case class We could reuse case classes for similar Tuples found in the codebase 🤔

@Krever01 Programmers: write all the software in the world. Also programmers: can't manage to create a single good application to talk with each other.

I don’t love Discord—but it’s what people use, so that’s where we are. The point is to make it as easy as possible to discuss the projects we care about.

@guizmaii One can figure out a simple conversion macro gist.github.com/Odomontois/75a… You can just import opaque type and write val v: CI["example"] = "Example"

Could it be possible to implement a type-level non-case sensitive String literal type in Scala? 🤔 ```scala final case class Example( v: n"example" = "Example" ) ``` where `n"..."` indicates for case insensitivity? 🤔

@effectfully Honest haskeller reaction to every non-haskell thing

@Odomontois kinda mid tbh

imagine being a programmer and getting paid in citations lol

@effectfully Haskell typesystem is so restrictive, haskellers can't even imagine non-haskell.

I decided to play both the sides, since the other side is too retarded to be capable of producing snappy insults.

@guizmaii @scala_lang @odersky @lukasz_bialy The whole point of enums was to reduce the amount of "PITA"s with sealed hierarchies. Not only reduced syntax but upcasted constructor result types for type inference in code such as yours and infamous foldLefts

@Odomontois @scala_lang @odersky @lukasz_bialy Doesn't seem to make sense to work with `enum` but doesn't work with sealed trait 🤔 But thanks Oleg! 🙂

The fact that @scala_lang fails to compile for this kind of code is a PITA: ```scala sealed trait A derives JsonCodec object A { final case class B(...) extends A final case class C(...) extends A } def f[Z: JsonCodec](z: Z) = ... f(A.B(...)) ``` Cc @odersky @lukasz_bialy Reproducer: scastie.scala-lang.org/jg6VZLpZTlGwNO…

@effectfully Don't worry, you'll get there someday! Just use git, write yaml and perform security analysis or smth

According to AI I'm only a 50% match for the exact job I've been doing for 6.5 years. Imagine being so incompetent at your own job that even AI can identify it.

@guizmaii @java docs.oracle.com/en/java/javase…

@spnlck объяснись

Оказывается, ехать в -5 на велосипеде - максимально хуёвая идея

@effectfully Look how consise it is ! (contains 9 more type references and TTG typeparam)

This is the entirety of GHC Core, the intermediate representation that surface Haskell elaborates to:

@spnlck @softwarevlogger Да, версию о том, что это лебединая песнь лично разработчика я тоже видел (кажется , в "Game On!")

@Odomontois @softwarevlogger он путается в показаниях, буквально вот строкой выше

Если Final Fantasy - последняя фантазия, то почему там столько частей?

@spnlck @softwarevlogger #Origin" target="_blank" rel="nofollow noopener">en.m.wikipedia.org/wiki/Final_Fan…

@softwarevlogger экшуалли 🤓☝️ разработчики (Square) думали, что это действительно их последняя игра, потому что у них кончились деньги

@guizmaii Can you possibly write a small example with specific Action, Rs, and expected result

Any type-level Scala magician around here? 🙏🏼 See: discord.com/channels/62949…

@nikalaikina Получается волшебная формула такой вирусной беззаботности, в которую легко поверить и удобно использовать. Она естественным образом распространялась пока избавление от стресса являлось главной коллективной задачей.

@nikalaikina Суммарно - это моральная база индивидуализма, лишённого рациональности. Т.е. посоветовать кому-то любить себя - примитивный способ получить чьё-то доверие, просто поддерживая капризы, наделяя любые сиюминутные желания безусловной ценностью.

Почему говорят нужно полюбить себя перед тем как полюбить кого-то? Почему не наоборот если полюбишь других людей такими какие они есть то получится полюбить и себя?