Valencik

@valencik
71 Followers
191 Following
115 Posts

Nerdy for food, drinks, and computers.
Mostly long and slow cooking, mostly bitter drinks, and mostly functional programming.

Thinking a lot about #search lately. Trying to contribute more in #OSS. Maybe start a blog? Maybe just stay on the couch with my cats?

#Typelevel #Scala #FP

Pronounshe/him
LocationOntario, Canada
GitHubhttps://github.com/valencik
🧪 The Typelevel ecosystem has shaped how many of us write Scala today. This talk looks back at where it started, what it became, and what we learned along the way.
Here’s "A Typelevel retrospective" by Arman Bilge
https://www.youtube.com/watch?v=51kW8zK7YhQ
Arman Bilge: A Typelevel retrospective [Scala Days 2025]

YouTube

A perennial misunderstanding I see around content moderation in online spaces for programmers is that moderation consists only of enforcing the Code of Conduct.

No. CoC enforcement is just the *minimum*. It’s the floor, not the ceiling.

Moderators are broadly responsible for keeping our spaces pleasant, professional, and productive...in short, enjoyable places to hang out.

Most of the time, leading-by-example and gentle persuasion suffice to accomplish this. (Not all the time, sadly.)

For those of you using Cats Effect to do real things, it would really mean a lot if you could take 3.6.0-RC1 for a spin together with Fs2 3.12.0-RC1 (doing them both is important!) sometime over the next week. We made significant under the hood changes and we want to make sure we don't break everyone when we push the final releases out!

Both are binary compatible with their respective current stable releases, and the source-breakage was fairly minimal, so it should be pretty drop-in.

A few months back the Typelevel Steering Committee put out a call for new members to join the Typelevel Code of Conduct Committee. Thank you very much to all who applied, it’s lovely to see folks interested in keeping our community safe.

Since that time, the Typelevel Steering Committee voted in three new members to the Code of Conduct Committee! The committee now has five members total.

More details at https://typelevel.org/blog/2024/11/21/new-code-of-conduct-committee-members.html

Typelevel | Code of Conduct Committee

Typelevel is an ecosystem of projects and a community of people united to foster an inclusive, welcoming, and safe environment around functional programming in Scala.

should sbt 2.x be perma-frozen at Scala 3.3 LTS, or evolve together with #Scala 3.x (either 3.5 or 2015 LTS)? join the convo on GitHub discussion

"Don't blame the gymnast, blame the Olympics"
https://github.com/sbt/sbt/discussions/7194#discussioncomment-11062161

Use Scala 3.3 LTS for SBT 2.x? · sbt sbt · Discussion #7194

Not sure if this was considered, but since we are discussing ideas for SBT 2 maybe we should also talk about Scala 3? In my mind, there are some good arguments for using Scala 3 and more specifical...

GitHub

To the FSF:

Remove Stallman. Replace the FSF board. Make the Free Software movement and culture safe for women to participate.

To Everyone:

Stop harboring assholes and start shouting down "reply guys". Make it clear to women that "Yes. You belong here" - not just with words but with actions. Take safety seriously. If you can't be kind to you fellow humans, then no amount of software will benefit the world, no matter its license.

https://mastodon.social/@report_press/113305688857205037

reupping this blog post about being a custodian of (tech) culture, and the phrase "we don't do that here"

https://thagomizer.com/blog/2017/09/29/we-don-t-do-that-here.html

Are you passionate about fostering a positive and inclusive community? Do you want to help shape how Typelevel works with the community to build a respectful environment for all? We’re excited to announce this call for new members to the Typelevel Code of Conduct Committee!

https://typelevel.org/blog/2024/08/24/call-for-code-of-conduct-committee-members.html

Typelevel | Call For Code of Conduct Committee Members

Typelevel is an ecosystem of projects and a community of people united to foster an inclusive, welcoming, and safe environment around functional programming in Scala.

the xz situation, which is too real for me, is a reminder for #Scala community that Zinc, sbt, and many of plugins are maintained in my free time (which is by design, and works while it works)

if your company uses #Scala at work, consider joining Scala Center corporate membership (50k/yr or 15k/yr), or provide % of eng time to them. for these toolchains, Scala Center is often the organization to fix CVEs, alongside compiler stewards like VirtusLab and Lightbend
https://scala.epfl.ch/corporate-membership.html

Scala Center at EPFL

The Scala Center at EPFL. Not-for-profit,

After seeing how the XZ maintainer's burnout and mental health decline was exploited to the potential detriment of the whole world, we're totally going to be supporting our developers more, right guys? We're totally going to fund critical OSS and pay maintainers enough to hire on other maintainers to take the burden off of them and reduce burnout, right? Right?