ScalaItaly

LA conferenza su Scala in Italia. THE Scala conference in Italy. Unisciti alla community italiana degli sviluppatori Scala su Discord

[ScalaItaly @ScalaItaly]

Do you know that yet another speaker joined the roster and will talk on November 11th? Welcome @GianlucaAguzzi1!
More info and tickets on https://t.co/081xJ0px8a

[ScalaItaly @ScalaItaly]

@kubukoz @YOWLambdaJam We moved all our videos to YouTube, here it is https://t.co/k5RezBUHb6

[Akka @akka_io_]

We’re excited to announce our partnership with @Scalac_io! Together, we’re enabling enterprise developer teams to bring large-scale, elastic, and resilient applications to market quickly using #Akka and #Scala. 🚀

Read the full press release to below!
https://t.co/aiFmz2c2uw

[Julien Truffaut @JulienTruffaut]

🚀 Looking for a new opportunity! 🚀

I am currently seeking a new contract as a Backend Engineer.

If you're hiring or know of any opportunities, please feel free to send me a message. DM open.

#scala #typelevel #catsEffect #hiring

[Jonathan Brachthäuser @__protected]

Thanks @odersky for mentioning Effekt (https://t.co/jyu8xGxf1y) and our work on lexical handlers! :)

[Jonathan Brachthäuser @__protected]

Effects are methods of effects traits, handlers are implementations,
capabilities are instances.

You can read more about these analogies in our JFP paper https://t.co/MapAMgQ07u

[Jonathan Brachthäuser @__protected]

I have to say that I am extremely happy that we ended up with multiprompt shift0 as the semantics for delimited control in Scala :)

[Jonathan Brachthäuser @__protected]

Here, Martin is explaining the "effects as capabilities" model and how it simplified effect polymorphic higher-order functions.

[Jonathan Brachthäuser @__protected]

Based on multiprompt delimited control under the hood, Scala supports a lightweight form of effect handlers.

[Jonathan Brachthäuser @__protected]

@odersky is giving his keynote at @icfp_conference talking about effect systems, Scala, and our work on capture checking.

[Li Haoyi @li_haoyi]

Opened a new set of com.lihaoyi issue bounties. ~3,500USD paid out so far, and now a further ~10,000USD worth of bounties up for grabs. If you know #Scala and are looking for fun OSS things to do, and wouldn't mind a cool 500/1000/1500USD, take a look!

https://t.co/8Rk7IWJjpD

[Julien Truffaut @JulienTruffaut]

I am looking for a new contract as a Backend Engineer starting October 1st.

I have 10+ years of experience building scalable and robust systems. DM open.

[ScalaItaly @ScalaItaly]

@pcalcado @gclaramunt https://t.co/TvUuUohpsk 👍🏻

[Li Haoyi @li_haoyi]

For anyone out there using the Mill build tool for #Java or #Scala: what IDE do you use?

https://t.co/EgrN9iglQp

[James Ward @JamesWard]

@josephfounder The topic is Effect Oriented Programming. The first edition will use Scala 3 and Zio.

[DevCycle @DevCycleHQ]

Will @playframework help Andrew get over his fear of @java & @scala_lang? 😰

Find out Friday as he returns for another "Does it Toggle?" attempting to add @OpenFeature compliant feature flags to a Play project 🚩

Streams live at 1pm PT / 4pm ET on https://t.co/wTcxKUlRbz 👀

[Łukasz Biały @lukasz_bialy]

Scala folks, I've been wondering - what are the biggest issues and hindrances with modernisation and maintenance of existing Scala apps? I mean things that have historically caused you the most pain in long term care over an existing codebase in Scala. My personal bet is that it's Spark because how far behind it is in terms of language versions and the write-once, care-never-if-it-runs approach to Spark pipelines but I'm happy to find out if I'm wrong. Beneath is a poll with few predefined options:

1) spark being behind modern Scala versions, also job abandonware status
2) breakage introduced by Scala language proper (2.13 collections, 2->3 migration)
3) ecosystem fragmentation and resulting lack of maintenance or breakage
4) abuse of abstraction for abstraction's sake

If there's nothing in it that fits your experience - leave a comment. Please retweet!

[Julien Truffaut @JulienTruffaut]

Debunking Common Scala Myths

1. Hiring Challenge? Nope!

This year, I interviewed companies building massive Scala teams (100s strong!):
SwissBorg & SiriusXM with Typelevel Scala
Databricks & Netflix for data engineering

2. Expensive Devs? Not True!

As a recruiter (3+ years at @ScalaJobsDev ), I've seen companies find Scala devs COST-EFFECTIVE. Their strong skills (compared to Java/Kotlin) lead to faster hiring and less interview time!

3. Stability Concerns? Unfounded!

Scala 2.13 (released 5 years ago) is actively maintained.
Scala 3 applications can leverage 2.13 libraries (Scala 3 uses the 2.13 standard library!).
Even popular libraries like Typelvel Cats maintain backward compatibility (newest version works with the 2017 release!)

Love Scala? Considering it?

I've been working & hiring in Scala for 10+ years. Reach out for advice!

#Scala #developer

[Codemotion @CodemotionIT]

⏳ Mancano solo due settimane prima del nostro prossimo meetup con @lucazav!

E tu ci sarai?
🎫 hhttps://www.linkedin.com/events/7206195953979056129/comments/

Ti aspettiamo il 17 luglio alle 19:00!

#CodemotionMeetup #CodemotionTV

[Li Haoyi @li_haoyi]

Anyone know how to get in touch with the @intellijidea #Scala folks?

https://t.co/IPcRl5ofnx is a regression that's been broken for three years. It seems likely to be a typo somewhere.

If it's a simple fix, I hope it can be fixed in weeks/months, rather than waiting years more

[Kit Langton @kitlangton]

Wha!? For comprehension improvements are coming!!!