Kaleb Lape

Rails development in 2024: 🔐 Authentication-Zero for authentication 👨‍🎨 CSS Zero for styling ⚡️ Ruby WASM for browser execution 🚫 No build configuration The future is simpler than you think. Here's why.

Get the knowledge. Learn the skills. Practice the system.

Whenever I'm doing dishes I try to pile them in async But the stack always overflows

Use AI, but love freedom? Keep your coding skills sharp Be ready for the "I'm sorry Dave. I can't do that." moment

@MichaelGame_Dev I don't always love it but certainly don't miss configuring linters myself, so 👍👍

@RailsQuest I need to try out StandardRB. Rubocop is a bit over the top

My Top Ten Toolbox for ruby on rails development 1️⃣ rails new 2️⃣ gem "foreman" (Next level: overmind and tmux) 3️⃣ Homebrew.sh (to install linux and mac tools) 4️⃣ rails generate 5️⃣ StandardRB 6️⃣ puts 😏 7️⃣ dotenv 8️⃣ heroku 9️⃣ rbenv 🔟 Safari (it's a real browser!)

@happyrubyist Sounds like a good option if you're into svelte! I prefer vanilla myself. Avoid js tooling like the plague.

@RailsQuest Ironically, it is easier, cleaner and less code to just use Rails, Inertia and Svelte.

So you're starting a new Rails app. Why use vanilla Rails instead of a SPA framework? If Rails can do what you need with built-in tools, why would you overcomplicate it? - Learn turbo - Learn stimulus Make it easy.

I'm still looking for a @Ruby on Rails role. Projects I was counting on have fallen through. 🌎 I’m open to remote roles worldwide (have worked for multiple US based companies) or hybrid in the Western Cape. Immediate availability. Please share.

@MichaelGame_Dev @justinamarsh I ran into this issue with morph enabled turbo loads, but only with nested scrolls using overflow-y like Justin said. It was even a little more complicated than that because of the code editor lib I was using. I worked around it with a scroll preserving stimulus controller.

@justinamarsh @RailsQuest for scroll position, have you seen morph? Maybe it won't work, but I saw a video about it recently and that was one of the reasons it was out there. Still new to Rails, so could be missing something.

@RailsQuest a webmaster, if you will

Aspire to mere seniority, anon? Aspire to mastery instead Become a Master Developer Not just a another Senior Developer

Good. Never bow to the mob.

@justinamarsh My experience has been the exact opposite on every point Except the scroll position (which is no biggie really) There is a shadcn project for vanilla rails I prefer css zero Tailwind + templates is ok too, if you must roll your own

Well one reason could be that turbo doesn’t support preserve scroll position once you have a layout with overflow-y. Another reason is that you don’t get to leverage a library like shadCN. You end up create your own design system. AI integration is not really up to date on the stimulus coding standards and makes lots of mistakes that’s hard to debug. You cannot prefetch modal requests if you want something to be fast that’s not changing… AI integration works extremely well when using something like inertiaJS. You can vibe code and utilize type safety for the AI to check against itself to speed up the iteration process. Onboarding engineers is easier because you can find front end developers easier and they can work in their chosen language. The api routes are greatly simplified so you can create a complex admin layout with deferred loading so you render one endpoint for a view as opposed to several mini ones. I’m sure there are many other reasons…

@davidteren @bbatsov We need to support devs who stand their ground to this nonsense. 👏

Oh damn! I missed this. Respect to @bbatsov and the team for standing their ground at the time.

@juliknl 🤯 I had no idea that happened to opal. This stuff has been brewing a long time.

Some folks may not remember this, but if it were not for political warfare in OSS we could have had Ruby in the browser... for 11 years.

@davidteren @PaddaPlays Awesome. Congrats grandpa!

Not even sure I'm ready to be a grandad 😳 😅 Super amped for my son & his wife.

Remember this: we allowed this environment to take root. Think about it. “Master” is suddenly deemed offensive, so we’re told to replace it with “main.” Brendan Eich, a brilliant mind who helped shape the very internet we use today was canceled simply for donating to causes he believed in, causes aligned with his values. These are not just isolated events. They are markers of a culture where reason is abandoned, and offense, left unchecked, is weaponized into destructive energy aimed at the offender. I can’t help but feel both angry and deeply saddened. Because what we’re witnessing isn’t just debate, or even disagreement, it’s the erosion of the very freedom to hold convictions without fear of erasure. Take @dhh, for example. Yes, he’s outspoken. Yes, his convictions come across strong. But why should someone be expected to suppress who they are, to water down their principles just to avoid offending others? Isn’t that the opposite of authenticity, the opposite of truth? This is where modern society has taken a tragic, irreversible turn. We’ve allowed a moral landslide: where private fantasies spill into the public square, normalized and celebrated; where distortions of morality are nurtured as cultural norms; where reality itself is sidelined, and ordinary people are pressured to abandon their values, their identities, their traditions and to nod along with lies they don’t believe in. I’ve seen this play out before. Here in South Africa, so much of what is only now unfolding in the West was already tested here. We became the proving ground for an agenda that seeks to reshape not just systems, but souls. And I can tell you: it comes at a cost. The breakdown of families, communities, and truths that once held people together. And then there are the darker signs like the disturbingly frequent celebration of the assassination of one of the most reasonable, graceful, and sound-minded men of our time. Think about what it means when society cheers the silencing, even the killing, of its most thoughtful voices. That’s not progress. That’s collapse. We didn’t arrive here overnight. It’s been allowed, step by step, compromise by compromise. And unless we choose differently, unless we reclaim courage, reason, and truth; it will only get worse. We need to make a stand! "For we do not wrestle against flesh and blood, but against the rulers, against the authorities, against the cosmic powers over this present darkness, against the spiritual forces of evil in the heavenly places." - Ephesians 6:12

You don't need service objects Just model your domain

I have officially been through enough loops to say this now: Doing Figma LAST really works. What devs need to start is the wiring. Not the final interior. Just like the contractors building your house need to know where the sink is, not the color of the tile or the faucet fixtures. And guess what? In a software system, a lot of the UX is IN THE WIRING. That means: what do you see where, how do you get there, what is shown, what is not? What's the business logic, what's the interaction, what's the flow? High fidelity matters. The final polish matters. And it's SUCH a better experience to do this ON TOP of working software. Because then you don't have to throw away work. A visual artist can put their heart and soul into every pixel, matching the wiring 1:1. This leads to extremely fast turnaround and buildup of momentum. Like when you finally see the drywall going up and the house becomes real. And what if the designer should make contributions to the core interactions or flow, and not only the surface? No problem — we can collaborate during shaping. We can spike interfaces, sketch ideas, and breadboard our conclusions in a whiteboard. But we don't the need to "lock in" the "final, final, final" Figma just to get started. Not at all. Wire it up, click on it, figure out if it does what we want, THEN we can go the extra step to make it beautiful. This really works. It's a way faster kickoff. And the designers are happier too. What about Lovable, v0, etc? The same pattern applies. If you try to give a high fidelity prototype as the "input" to the build step, there will be trouble. Lots of time bombs. Lots of business logic and interaction issues we couldn't see behind the illusion of the finished sheen. Vibe coding is fantastic for trying out ideas. But before we start "construction", better to strip back to the essential wiring that we are really sure of and that we understand. Then layer on the polish later.

TDS is a mental disorder

@DeeperThrill instant visceral disgust

Wait they spent nearly a billion dollars on this?

@yegorckv Back from long and busy summer. Can't wait to check this out.

@RailsQuest Offline mode done github.com/hotwired/turbo…

Question came up at RailsConf: How would a turbo native app work offline? For instance if I'm building a controller for iot devices that needs to work off grid, is there any magic salve for that? Do I need to roll a custom PWA offline cache using a service worker?