Vitthal Mirji retweeted
The Scala Summit 2026 recordings are out! 🎥
All 11 talks from our October 19 conference in San Francisco: AI and agents, capture checking, Chisel, ZIO, GPUs for type inference, and more.
watch.softinio.com/w/p/1y91H…
#Scala #ScalaSummit #BayAreaScala #SFScala #FunctionalProgramming
cc @BayAreaScala @sfscala @Winium @higherkindedtpe @adamwarski @lukasz_bialy @RomanowskiKr @liosedhel @VirtusLab @scala_lang @tstokrk
Columnar on disk, in @ApacheDataFusio, @ApacheSpark too - except in the middle, where row-format quietly sneak-in 😉
SIMD, Arrow IPC, mmap'd zero-copy, all safe with no runtime watching. Inside Arrow's buffers, the borrow checker is lethal on bugs JVM/Python GC around🗑️
And of-course how to scaffold data-pipelines that stay in above lane!
Next week, speaking in @JOTBConf / @Lambda_World
Smart people proved a CEO can think clearly and still fire everyone. Why? The company keeps all the money saved, but the cost of lost customers is shared with everybody else. So don't tax the thoughts. Tax the automation. #AILayoffTrap
Vitthal Mirji retweeted
Caught up with @jonhoo at EuroRust! 🦀
• Rust's static checks matter more than ever
• Safety types could let Rust verify unsafe blocks at compile time
• LLMs are great first-pass reviewers, not final approvers
#rustlang #eurorust #interview
Vitthal Mirji retweeted
If you're a curious #Scala dev and want to see a demo of #EEZO, here is the video of our talk at @scaladays. We created and deployed a web app in the cloud (on Fly . io) from scratch in less than 30 minutes 💨
youtube.com/watch?v=IOsSpHu3…
Vitthal Mirji retweeted
Day 2 at #EuroRust, with the people behind RustRover 🦀
We’ve got the booth, the crew, cool merch and plenty of Rust to talk about. Come find us!
Vitthal Mirji retweeted
This week at @scaladays, we presented our new framework, called eezo 🐲. In #EEZO, the models are case classes, and through #Scala 3 derivation machinery, you can easily get CRUD routes over HTTP and persistence in a Postgres table. The example below mounts 7 routes in a Jetty HTTP server and creates the `book` table.
Web development made eezy again ♥️
Check out our site and say 👋: eezo.io
Vitthal Mirji retweeted
My favorite talk from Scala Days 2026 was about baking refinement types right into the compiler.
Unlike libraries like Iron or Refined, it adds a built-in solver that verifies logic and math across multiple variables at compile time with zero runtime cost.
Moving from simple checks to full verification is how Scala's type system should evolve to constrain LLMs - AI code won't compile unless the math holds up.
Vitthal Mirji retweeted
Found Ferris outside, a bit fashionably late! 🦀
#EuroRust26 #RustLang
Vitthal Mirji retweeted
I just published my slides for my talk “Where are we going with the Standard Library?” From ScalaDays 2026 bishabosha.github.io/scalada… @scaladays
Vitthal Mirji retweeted
Great time in Berlin! Today at @scaladays, @danielciocirlan and I presented our new web framework called eezo. Model routes and entities using #Scala case classes and derivation.
Drop us a ⭐️ on GitHub and contribute!
Here is the site 🌐: eezo.io/
Vitthal Mirji retweeted
On Monday, I'll be in Berlin with the great @danielciocirlan, speaking @scaladays and presenting our new framework. Come to the venue to drop a 👋
Ever wanted a new web framework for Scala? Daniel Ciocîrlan and Riccardo Cardin are building one.
They're at #ScalaDays 2026 to explore the big ideas their framework is built around. It's definitely one to look forward to.
More: scaladays.org/session/shoppi…
12-13 October. Berlin.
Vitthal Mirji retweeted
Can the JVM be faster than Ruby or Rust? (Yes) xitter.cf/i/broadcasts/1vJpPNozn…
the type-system itch. Very satisfying to scratch.
github.com/HyukjinKwon/spark…
The model is 5% of the system. The other 95% is df2_final_v3_FIXED.csv .
We normalized notebook-grade code, called untyped glue "agility" and then acted surprised when the pipeline jungle ate the team.
Not a Python problem. An "nobody carried the pager" problem. And yes, Python in prod without types is still how we got here.
We didn’t make data scientists own production, so they never paid the cost of untyped, untested code. SQL and functional thinking first (the math and stats were already there). Then hand over the pager.
Vitthal Mirji retweeted
Replying to @matej_cerny
Can you imagine if Odersky had a bit of curiosity about how this is a weak form of algebraic effects and the language could instead get native direct effects that integrate with both direct and monadic code? It needs just a bit of CPS but it’s question of a religion not tech. EFFECT SYSTEMS MUST DIE so we’ll keep getting unprincipled features until that’s the case, which is never 🤭






















