Replicube is an awesome little puzzle game. It’s like Picross 3D meets shader programming. The puzzles are a fun challenge and the interface is charming. Worth checking out!
https://www.walaber.com/replicubeReplicube — Walaber Entertainment
90% of the Ruby code I’ve written the past few years has been class methods without shared state. The code has clearer dependencies and is easier to read, test and maintain. OOP has its place, but I don’t think it fits the majority of web-app logic.
I do agree with this thought behind the post: external dependencies should be avoided when not absolutely necessary.
I personally would like to see the default Rails install slimmed down and more things moved into official gems.
That said, this is coming from 37 Signals so it makes sense vanilla Rails is plenty for them. if it wasn’t then they would add it to Rails to fit their needs.
We all have different apps with different requirements. If vanilla Rails is plenty then I think vanilla Rails does too much.
https://dev.37signals.com/a-vanilla-rails-stack-is-plenty/
A vanilla Rails stack is plenty
Minimal dependencies, maximum productivity. Staying vanilla pays long term dividends for your Rails apps.
What’s everyone using these days to cross-post between Bluesky/Mastodon/X?
Ruby’s metaprogramming is like a forbidden fruit. Always there tempting me, and I almost always regret using it.
I love how Ruby handles keyword arguments. I miss them in just about every other language.
After working with Roc and Gleam for a while, full type inference is amazing. Now I want a procedural language with full type inference.
