RFC: We intend to deprecate support for ECMAScript 5.1 in the next version of #Scala.js. If you are still relying on it, please weigh in on the PR and tell us why. The default has been ECMAScript 2015 since Scala.js v1.0.0. https://t.co/HjdlvoYTQh
Roguelike-Starterkit 0.6.0 (Terminal graphics for Indigo)
This release uses Indigo's new UI capabilities to provide ASCII / Terminal UI components for roguelike games and other terminal applications.
https://t.co/aFCpaC3emy
So! It's been ages! For releases, 2024 was my 'lost' year as I slogged through the surprisingly hard problem of building a component UI system from scratch.
But I'm pleased to announce a raft of new releases. If you want to do some weird stuff with #Scala, look no further.. 🧵
Ultraviolet 0.4.0 (GLSL Shaders)
Not often this one gets much love, despite being the bedrock of our graphics engine.
- Exciting new color value interpolators
- Built-in SDF shapes
- Noise helpers
https://t.co/Jof514fV3q
#Scala.js 1.18.2 is released! It contains one more backward compatibility fix, improves compatibility with Scala 2.13.16, and improves the generated code for js.Dynamic.literal() with Scala 2.13.x. https://t.co/4RyjkPi8D2
Happy New Year! 🎊
Excited to see you tonight for the first Scala Talks of 2025 at Quantexa! Hear from Gabriel Asman on Optics in Scala Using Monocle and from Roberto Tyley on Joyful & Secure Publishing to Maven Central.
https://t.co/6zB23X1bsf
We are pleased to announce the release of #Scala.js
1.18.1 (instead of the expected 1.18.0). This is mostly a bugfix release. It also contains internal improvements that will support future enhancements. https://t.co/wFQs3BDLSI
Metals 1.4.2 has been released! 🦬
This release again focuses on stability, but we have a new code action to infer method added by one of the contributors! 🥳
Try it out in your favourite editor!
https://t.co/c8RenL3bUB
📯 Scala 3.6 is out!
💪 Improved syntax for givens, context bounds (SIP-64)
💪 Multiple, interleaved type parameter lists (SIP-47)
🧪 Experimental features, such as named tuples
🎉 and more; details: https://t.co/5us1MBgx0o
⚠️ use 3.6.2; ignore 3.6.1 and 3.6.0
@Krever01@Anh32920995 I'm not comfy with the connotations of 'smarter', feels too loaded, but I hear what you're saying and agree to an extent. The nuance is probably too subtle for debate here.😇
I am prepared to concede that Scala tends to attract and retain a certain flavour of developer.
@Anh32920995@Krever01 A fair challenge. Scala alone isn't enough and no, Scala dev's aren't smarter. (Well, I'm not anyway!😅)
The advocates here (IMO) are saying Scala and meaning: Scala, with Cats Effect / ZIO (...not Akka), in FP style leveraging advanced types.
That's the sweet spot. (for BE)
@Krever01 I think an easy trap to fall into, is the knee jerk notion that 'growth' means hiring loads of people.
If you're using a language like Scala, where a few can do a lot, then trying to hire like you're scaling a Java/Go shop leads to problems ...and inevitably, layoffs.
@Krever01 My sentiments exactly. 💯
We built and ran TWO big commercial video streaming services with a handful of people.
How you deploy and empower those people matters a lot, however. The language won't fix your engineering culture problems for you.
What's the value proposition of Scala?
You pay x1.5, but you get x3 output.
You get 1/10 of the talent pool but you run 1/50 of the interviews.
You can't grow as fast as with Java but you can do much more with much less. And the cost of running a company (e.g. processes, communication) grows with a number of employees.
So yeah, you won't build another Google with just Scala. But you can't definitely build a lot.