home.social

#scalaio — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #scalaio, aggregated by home.social.

fetched live
  1. It's been a ride but ScalaIO has come to a closure, after being very functional. Awaiting continuation. Well done guys!

    #ScalaIO #Scala

  2. And now at #ScalaIO, the part where we say good bye and we all cry a bit

  3. And now at #ScalaIO, the part where we say good bye and we all cry a bit

  4. Great talk about Kyo from Jonathan Winandy.

    Between cats effect, ZIO and Kyo, the latter seems to be the most straightfoward. And the more appealing for people like me who like direct style.

    But it's still a "systemd of Scala": once you want to use a bit, you have to embrace the whole ecosystem.

    #ScalaIO #Scala

  5. And for literally one of the last talks of #ScalaIO, we have the immense luck to have Jonathan Winandy, one of the organisers of the conference, give us a talk on #kyo, one if the amazing demonstration of the power of #scala3 for better developer experience

    github.com/getkyo/kyo

  6. And for literally one of the last talks of #ScalaIO, we have the immense luck to have Jonathan Winandy, one of the organisers of the conference, give us a talk on #kyo, one if the amazing demonstration of the power of #scala3 for better developer experience

    github.com/getkyo/kyo

  7. And now at #ScalaIO for @NicolasRinaudo

    Who is live coding (last try for him!)
    From the last #scalaio conference

  8. And now at #ScalaIO for @NicolasRinaudo

    Who is live coding (last try for him!)
    From the last #scalaio conference

  9. #ScalaIO @MateuszKubuszok
    Talk: Can we have the standard library for macro?

    OH YES PLEASE

  10. #ScalaIO @MateuszKubuszok
    Talk: Can we have the standard library for macro?

    OH YES PLEASE

  11. First and last day of the last ScalaIO!

    Let's see how Scala and the community are doing, learn new things. And meet friends.

    #ScalaIO #Scala

  12. Last #scalaio of all time, here we go!

    And thus starts the last edition of the last community driven Scala event, which should ring a bell for the #scalaCenter success in its mission

  13. Last #scalaio of all time, here we go!

    And thus starts the last edition of the last community driven Scala event, which should ring a bell for the #scalaCenter success in its mission

  14. Wow, this is the last #scalaio.

    After 12 years, that conference had become THE INDIE conference for #scala dev and community. The cheapness, quality of venu, attention to food and specific choices, talks, and general mood and management of a complicated community had always been top.

    I was at the first and each ones following that, speaker on a lot of them... This is really a page of the #scala history that is closing.

    Thank you to Valentin, Jonhatan, @mark and all the other who made that fabulous place in time and space a reality.

    And... In the same time, I understand you so much. And respect what you did during all that time even more. Thank you !

    Let's celebrate that last gathering. One last time, together, enjoying the place and time 🤗

  15. Wow, this is the last #scalaio.

    After 12 years, that conference had become THE INDIE conference for #scala dev and community. The cheapness, quality of venu, attention to food and specific choices, talks, and general mood and management of a complicated community had always been top.

    I was at the first and each ones following that, speaker on a lot of them... This is really a page of the #scala history that is closing.

    Thank you to Valentin, Jonhatan, @mark and all the other who made that fabulous place in time and space a reality.

    And... In the same time, I understand you so much. And respect what you did during all that time even more. Thank you !

    Let's celebrate that last gathering. One last time, together, enjoying the place and time 🤗

  16. I just learn that.

    I only met Brendan a few times IRL, the first one at #scalaio 2013. He was so nice, a reassuring head in the assembly for a novice speaker.

    I never stopped to maintain a social link with him, something that I'm especially bad at, but that he made simple.

    Brendan was obviously brilliant, and not only to find the perfect gif to answer you. The kind of brilliance that doesn't put other under its shadow but make them shine even more.

    He was so human it hurt, with a bottomless kindness.
    He was the kind of people I thought to when humans were too bad, so that I remembered what Humans can be.

    This world will miss you.
    I will miss you.
    I hope you'll will find the peace that eluded you here.

    https://mastodon.social/users/armurray/statuses/113827613111941167
  17. I just learn that.

    I only met Brendan a few times IRL, the first one at #scalaio 2013. He was so nice, a reassuring head in the assembly for a novice speaker.

    I never stopped to maintain a social link with him, something that I'm especially bad at, but that he made simple.

    Brendan was obviously brilliant, and not only to find the perfect gif to answer you. The kind of brilliance that doesn't put other under its shadow but make them shine even more.

    He was so human it hurt, with a bottomless kindness.
    He was the kind of people I thought to when humans were too bad, so that I remembered what Humans can be.

    This world will miss you.
    I will miss you.
    I hope you'll will find the peace that eluded you here.

    https://mastodon.social/users/armurray/statuses/113827613111941167
  18. @arosien I just saw a talk about Kyo at #scalaio and it looks like a step in that direction.

    The slide with "flatMap is just map" (because io is just a type marker) was 🤯

    But the main problems for me are always at the limits, like "does that totally harmless looking function is calling the network for who knows what" or "isn't there a logging framework somewhere in the call stack" (the two being often the same)

  19. @arosien I just saw a talk about Kyo at #scalaio and it looks like a step in that direction.

    The slide with "flatMap is just map" (because io is just a type marker) was 🤯

    But the main problems for me are always at the limits, like "does that totally harmless looking function is calling the network for who knows what" or "isn't there a logging framework somewhere in the call stack" (the two being often the same)

  20. ScalaIO 2024-2 c'est fini ! C'était bien cool, merci beaucoup à l'orga dont @mark qui a bien mérité sa séance de surf sur laquelle il fait beau plusieurs fois !

    #ScalaIO #Scala

  21. Hey there, Paris! 🇫🇷

    We just finished presentations by @adamwarski and Magda Stożek at Scala.io

    Thank you to everyone who joined us... and see you at Scalar in March

    #ScalaIO #scala

  22. Hey there, Paris! 🇫🇷

    We just finished presentations by @adamwarski and Magda Stożek at Scala.io

    Thank you to everyone who joined us... and see you at Scalar in March

    #ScalaIO #scala

  23. This morning at ScalaIO, @adamwarski spoke about "direct-style Scala" and how much it can be qualified as "functional". The answer being: pretty much.

    It seems I was doing direct-style before it even had a name. Never was confortable with suspended effects – may have a look on Kyo though.

    #ScalaIO #Scala

  24. (I will let you discover the part 2: direct style. The base is "direct style is avoiding continuations")

    #ScalaIO

  25. (I will let you discover the part 2: direct style. The base is "direct style is avoiding continuations")

    #ScalaIO

  26. And a "final" assessment after some wandering to Haskell and discussions on the topic

    #ScalaIO

  27. And a "final" assessment after some wandering to Haskell and discussions on the topic

    #ScalaIO

  28. And a sumup: fp is a paradigm where programming constructed by applying and composing functions

    But it is a spectrum, from casual to pure fp

    #ScalaIO

  29. And a sumup: fp is a paradigm where programming constructed by applying and composing functions

    But it is a spectrum, from casual to pure fp

    #ScalaIO

  30. With nice comparisons of different snippets of more or less FP code, like here comparing Java/Haskell/unison

    #ScalaIO

  31. With nice comparisons of different snippets of more or less FP code, like here comparing Java/Haskell/unison

    #ScalaIO

  32. This morning on #ScalaIO , @adamwarski talk about direct style fp and ask the hard question: what is functional programming?

  33. This morning on #ScalaIO , @adamwarski talk about direct style fp and ask the hard question: what is functional programming?

  34. #ScalaIO Hey, i'm looking for an experienced Scala dev with aspirations for mentoring, evolving practices, technical management of projects (derisked path from idea to poc/MVC/milestones, reassessment, etc)

    We're rudder.io, a secops tool for checking and enforcing security configurations, patch, best practices on heterogenous IT infra.

    It's a 15y old Scala project, maintained with love, now mostly zio based and on the verge to switch to Scala 3. We also do elm for front, and the system team does rust and f#.

    Small team (6 for dev), extremely low turnover, floss good citizens, strong and sustainable growth.

    French company based on Paris with up to 90% remote, looking for a French worker based on France. Come talk to me 👋

    (NDR: hum, pas sûr de pourquoi j'ai ecrit ce post en anglais)

    #fediHiring #rudderio #scala #france

  35. #ScalaIO Hey, i'm looking for an experienced Scala dev with aspirations for mentoring, evolving practices, technical management of projects (derisked path from idea to poc/MVC/milestones, reassessment, etc)

    We're rudder.io, a secops tool for checking and enforcing security configurations, patch, best practices on heterogenous IT infra.

    It's a 15y old Scala project, maintained with love, now mostly zio based and on the verge to switch to Scala 3. We also do elm for front, and the system team does rust and f#.

    Small team (6 for dev), extremely low turnover, floss good citizens, strong and sustainable growth.

    French company based on Paris with up to 90% remote, looking for a French worker based on France. Come talk to me 👋

    (NDR: hum, pas sûr de pourquoi j'ai ecrit ce post en anglais)

    #fediHiring #rudderio #scala #france

  36. Wow! @MateuszKubuszok has built a Scala 2/3 automatic type-class derivation system that allows faster compile time and faster execution, even against semi-automatic derivation. Using macros instead of implicit derivation.

    That's only used in Chimney common libs for the moment. Once ready, cost for libraries that want to use it would be increased boilerplate code. So would be only advised for already mature libraries that want to improve performance for their users.

    #Scala #ScalaIO

  37. Not posted a lot about #scalaio but the talk by @MateuszKubuszok on derivation and how jsoniter and chimney bring a new way of more convenient, quicker to compile and faster to execute derivations is very good and brings joy in thinking about what could be done

    You should really look at the video once available!

    (It took him less than a week to optimize chimney with jsoniter techniques)

  38. Not posted a lot about #scalaio but the talk by @MateuszKubuszok on derivation and how jsoniter and chimney bring a new way of more convenient, quicker to compile and faster to execute derivations is very good and brings joy in thinking about what could be done

    You should really look at the video once available!

    (It took him less than a week to optimize chimney with jsoniter techniques)

  39. Keynote très particulier et personnel de Valentin Kasas à ScalaIO ce matin, qui établit le diagnostic et les pistes de guérison sur le déclin de Scala. Il pose les mots sur un sentiment général dans la communauté.

    Des raisons objectives (remoting, cercle vicieux des compétences, conflits dans la communauté, amélioration de Java) comme mystérieuses (des arguments applicables aussi à des langages en forme).

    Conclusion qui demande de répandre l'amour qu'on a pour ce language !

    #ScalaIO #Scala

  40. The conclusion slide: kio is amazing and a much simpler way toward effects than cats/zio/monad transformers/etc.
    And performance are better by construction (fewer flatMap and encapsulation)

    #ScalaIO

  41. The conclusion slide: kio is amazing and a much simpler way toward effects than cats/zio/monad transformers/etc.
    And performance are better by construction (fewer flatMap and encapsulation)

    #ScalaIO

  42. Now a talk about kio and its amazing, but I'm too drained to live post.

    Its just amazing and an other vitrine for Scala 3

    A gist: "no more .succeed/.pure, flatMap is just map"

    #ScalaIO

  43. So,

    • mentor and teach Scala - a lot!
    • build companies and teams and be loud about your Scala success and hiring
    • don't start with fp type wizardry in anew team, strat simple and help people learn the (fp) tools that deal with their pains when they arise

    This is the path to reach the lovely plateau of productivity for Scala ❤️

    #scalaio

  44. That forced crash back from FP skies to earthly imperative code make him realized that it mostly work.
    And that's a big reason for why Scala was not seen much better than Java there.

    Until when case was making people suffer. And that case was easily and cleanly solved with a dedicated state monad.

    And then, it was trivial to make people accept that Scala solution with FP was so much simpler and cleaner and better

    #scalaio

  45. Making thing simpler seems to be an important topic for Scala future, but still use Scala first principle cleaness to really help deal with complicated topics.
    In his last mission, the rules were to "Scala but like Java for code base comodification".

    Hard. No Monads, no recursion schemes where the domain model would have match, no implicit at all.

    #scalaio

  46. So you don't convince mass people on ideas.
    These people were there 15 years ago. They are few.
    But when you have solutions to problems, you can convince people.

    #scalaio

  47. And we are a small community. And their was a decade of internal fight were the position was "you're with our sub group or against", bringing irreversible divisions even omong who just wanted to build bridge between people.
    Perso note: exactly my feeling. Strong JdG and Travis vibes here.
    We lost amazingly kind and nice people in these fights (thinking to @tpolecat for ex)

    #scalaio

  48. He explains that after a few years of thrill and joy in the first years around 2010, a darker period happened.
    Around 2017, he got into some kind of social media retreat. Then covid hit and when he started to look around again, Scala seemed to have deemed a lot.

    #scalaio

  49. Of course there's also external reasons for Scala decreased, standards ones: Java getting more and more interesting on feature side, too complicated, too many way to do the same things, no job market

    But all this reasons are not real reasons: JS has even more way to do things, other trending languages have even smaller job market, etc

    (But JS is the only choice for a huge need.
    Rust is the only choice for typed, secure system programming.)

    #scalaio

  50. Ok, but Scala is still a fabulous language. And Valentin wanted to continue to use it.
    And share his old joy about it.
    So he started mentoring.
    And mentoring is massively rewarding for all people involved, and to demonstrate how much Scala is better in many way to make thing simpler.

    #scalaio

  51. And so #scalaio is starting with Valentin Kasas with his keynote ~Scala love~ DUSK.

    not cheering up people.

    He starts by thanking Scala.io for being the last indi, open Scala conference, independent from editors

    (Note: mist photo won't have description, it should be in the posts)