Tristan Dunn

Found 4 entries tagged "ruby".

Replacing YNAB with a Custom Budget Application

After using YNAB for about ten years, I finally grew tired of the increasing annual price and the endless features that made it feel like it was targeting a completely different audience. I understand the company has to cater to new, less technical users, but I found it frustrating as an experienced user.

In January I started building Budget, a minimal and focused envelope-based budgeting application in Ruby on Rails. I started with the mobile version because that’s the most common entry point for adding a transaction. By May it had enough feature parity with YNAB that I could use both in parallel and look for any remaining gaps. In June I started on the desktop version, which is where I typically assign money and reconcile transactions. Finally, in July, I switched to using Budget exclusively.

I’ve continued adding features as I’ve needed them. And while it supports multiple budgets and users, it’s built around how I use it. I have a number of ideas for improvements, including reports, category management, user management, two-factor authentication, and more.

at 7:48 PM — budget, rails, ruby

Glamorous Christmas: Bringing Charm to Ruby (cache, source)

Ruby developers deserve glamorous terminals too. I want Ruby developers to build terminal applications so beautiful that even people who “don’t like CLIs” find themselves captivated.

I’ve recently been using AI to write CLI utilities in Go with Charm, but I know Ruby much better than Go so this is very exciting news. I’m even more excited about the coming work for the libraries to “feel more Ruby-like and idiomatic”.

at 12:56 AM — cli, open-source, ruby

Ruby 3.4.8 Released (cache)

Ruby 3.4.8 has been released as a routine update that includes bug fixes. The full details are available in the release notes on GitHub.

It’d be nice if the Ruby team maintained the Docker image now that Ruby has a release schedule. Always feels odd to see a new release and then have to wait for an image update to be able to test a deployment.

at 10:28 PM — open-source, ruby

Upgrading to RubyGems/Bundler 4 (cache)

We introduced breaking changes in RubyGems/Bundler 4 in order to improve usability, security, and maintainability of the tool.

I’ve upgraded a few projects and not noticed any issues so far. Restoring the default command to be install is nice for my muscle memory locally, but elsewhere, like in a Dockerfile, I already use bundle install explicitly.

And while new lockfiles include checksums by default, you have to manually add them to existing lockfiles via bundle lock --add-checksums.

at 10:19 PM — rails, ruby