Alessandro D retweeted
I wrote about ownership and non-determinism 👀
cassidoo.co/post/non-determi…
Alessandro D retweeted
Rails 8.1 has been released! It includes job continuations, structured events, local CI, registry-free deployments, and so much more. Over 500 contributors has code in this new version 🤘 rubyonrails.org/2025/10/22/r…
Alessandro D retweeted
The newest add-on tutorial is now live on the Rails tutorials page! In this guide, you learn how to add Wishlist functionality to the e-commerce demo app you already started.
By following this tutorial, you'll also learn:
• Counter caches to track wishlist items
• Friendly URLs for better customer wishlists
• Using Stimulus to copy wishlist URLs
• Admin filtering and controls
• Testing for all wishlist features
Find this tutorial and more on the Rails tutorials page: rubyonrails.org/docs/tutoria…
Big thank you to @excid3 for creating this tutorial, and those who helped by reviewing!
Alessandro D retweeted
Rails 7.2 release candidate 1: Better production defaults, Dev containers, new guides design, and more! rubyonrails.org/2024/8/6/Rai…
Alessandro D retweeted
FULL TIME | #VeneziaCremonese 1-0
Un sogno, una realtà
A dream, A reality
24’ Gytkjaer
#FinalePlayoffSerieBKT
#ArancioNeroVerde🟠⚫️🟢
Alessandro D retweeted
The todo application. 😅
But, seriously, here's the thing...
When Laravel and Rails developers say "full stack", they mean something totally different than when Next or Remix (React Router?) developers say "full stack".
In Laravel and Rails, it means there are built-in, opinionated solutions to things like validation, interacting with a database, authenticating users, scheduling background work, sending an email.
In Next and Remix, it seems to mean that there is simply the bare ability to run code on the server at all and an advertisement for Clerk. 🙃
From my perspective, Next and others are really, really great at the GET part of web development. Get data from some backend, show it on the page quickly. 👌
They are not mature for POST, PUT, and DELETE, especially when things start getting non-trivial.
And, I don't think this is really unique to Next or a single framework. It's something that seems to pervade current JavaScript as a whole - note the current proliferation of "starter kits" that try to bring some sanity to the full-stack story.
I think this has had actual consequences in the JavaScript ecosystem...
Rails and Laravel were built with the express purpose of allowing a single developer to build the next GitHub... or the next AirBnb... or the next Shopify. Prototyped from beginning to end.
That's what I'm passionate about. Empowering a single developer or small team to build something amazing.
I built the 1.0 of Laravel Forge, Envoyer, Vapor, Spark, and the backend of Nova by myself.
$40M in revenue over 10 years from my home office. That's an empowering tool for a solo founder.
I don't see a full-stack story in JavaScript yet that would allow me to realistically sit down and build something like Forge or Vapor from start to finish. Maybe I'm missing it. 🤷♂️
The MVP start-ups I do see fully built on current JS meta frameworks are much thinner. The stereotypical API call to an AI service. Not much meat on the bones.
Laravel / Rails have been building their modern front end story with Hotwire, Livewire, Inertia, and more... Next and others are building their modern back end story.
Smart people on both sides working on these problems, so I'm confident we'll both get to where we want to go. 💪
Alessandro D retweeted
For me, coding in the early 2000’s was terrifying.
I had no tests.
I had no types.
I had no autocomplete. Runtime errors were extremely common.
Our team had no source control. Our code was on a shared folder. No backups. When I accidentally closed a saved file with incomplete/experimental work, I had no way to undo my mistake.
I worked with someone in Hungary while I was in the central USA. We would message each other things like "Stay out of user.js. I'm going to edit it now."
We worked in PHP. The docs were inconsistent, unclear, and listed multiple ways to do the same thing. SQL injection attacks were common. (PHP has matured a LOT since then)
We worked in JavaScript. The language was weak at this time and rarely improved. Browser support and behaviors were inconsistent.
We didn’t have StackOverflow or AI. Finding answers often required sifting through 100’s of messages on various forums.
Deployments were manual. We moved files via FTP.
Our production server was in a closet near my desk. If anyone closed the closet door it would overheat and crash.
I was so stressed I could barely function. I had no idea we were making it hard on ourselves.
Coding today feels like a vacation in comparison!
Alessandro D retweeted
I am checking Solid Queue, and I start seeing a pattern. People are sick and tired of having 1548 different services to run a simple app. Things are slowly imploding back to good old relational databases, server side and simplicity.
github.com/basecamp/solid_qu…
Alessandro D retweeted
If you've ever seen "database is locked" errors in production when using SQLite, you've probably been frustrated by attempts to resolve the issue. After bumping into the issue one too many times, I sat down and dug in to figure out what is going on and how to resolve it. 🧵
Alessandro D retweeted
a good pro-HTML site/article:
html-first.com/
the hypermedia renaissance is building!
Alessandro D retweeted
Bootstrap.
I tried Tailwind and it was just too complex for me. It felt like going a step backward and I was simply too slow. Maybe because I don’t work much on customers facing app? Somebody should probably show me what I am missing out.
Alessandro D retweeted
Pictures from #rubyday2023
🎤@Ridhwana_k ,Lead Software Engineer @forem
🎤@arkh4m , Staff Engineer @Shopify
🎤@GI_MY86 Engineering Manager @teamnebulab
Couldn't you attend the conference?
Video recordings available
📽️ bit.ly/shop-grusp
#rubyday #ruby #rails
Alessandro D retweeted
I just came back from the #rubyday in Verona and it was fantastic! 🤩 I am so happy that this event is finally happening again! 💪
Here are my thoughts about the event, written very quickly immediately after the event, so everything is still very "fresh".
dev.to/coorasse/rubyday-2023…
