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! www.walaber.com/replicube
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.
Whenever you’re tempted to reuse a method that *almost* does what you want: Stop, duplicate the method, make the modifications, and then refactor the actual duplication.
I Googled "capybara drag_to" and the results caught me by surprise.
It starts multi-select and selects the next occurrence of the current selection. Super handy for renaming variables or repeating keystrokes in multiple places. I've tried using Vim macros as a replacement but could never get the workflow as efficient.
I use Vim extension in VS Code and it is pushing me toward Neovim. The undo behavior in particular feels tacked-on. I just wish Neovim had command-D. Zed is promising but not quite there.
Anyone else find GitHub code diffs near impossible to use in Safari lately? Slows to a crawl and/or doesn’t render.
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 aren't included by default.
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. dev.37signals.com/a-vanilla-ra...
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.
In Ruby I always use keyword args if the method takes more than one arg. I find the code much easier to read than positional args. It's less necessary in functional land with a typed language, but it's still easier to read.
Gleam is close, but I find the double `name name: String` to be cumbersome. I understand the reason for it that you explained a while ago. I just run into it a lot in my code.
I like that they aren't just pattern matched records (JavaScript, Roc, Elixir). I imagine it has a performance impact and you need to make the record. Elixir also has keyword lists but I could never figure those out.
Honestly have no idea. Just a google image search. 😄
I feel like GitHub’s marketing is no longer interesting to me as a developer.
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.
I wonder why more functional languages don't support local mutability within the scope of a function. It is convenient and still keeps the function pure.
Hello all! I'll try to post on here along with Twitter/X and ruby.social.
