pawurb / devloop

An automated test runner for Rails that instantly executes specs based on a recent git diff output.

Rails and PostgreSQL Performance Consultant

Full Stack web development consultant with over 9 years of experience. Founder of Abot for Slack. Specializing in Ruby on Rails, PostgreSQL and website performance. Experienced in building scalable APIs for startups and refactoring legacy codebases. I'm blogging about web development related topics. After hours I train rock climbing to rest my wrists from the keyboard.

I'm currently available for ad hoc Rails performance consulting sessions.

devloop's Issues

Feedback: why not use Guard?

Hello Paweł,

I hope it's okay if I leave my feedback here. I came across your blog post how learning Rust changed your Ruby workflow. I saw that you started creating this gem and my first question was "why not use Guard"?

In your blog post you mention that guard-rspec is no longer maintained, but I don't think that's true. I know there haven't been any commits in a long time, but that's because "it just works". I've been using it with the latest versions of Rails and RSpec without any issues. Guard continues to be maintained. The listen gem that Guard uses was updated 2 weeks ago.

That being said, I wonder if there is still a reason that makes devloop different/better than using Guard. I can tell you that the main reason I use Guard is for that immediate feedback loop when doing TDD. If there was a better/faster alternative, I would probably switch. The thing that I don't like about Guard is that you have to add it to your Gemfile. I would prefer to use a tool like this that doesn't require me to add it as a dependency to my project.

Have you considered this use-case? Are there other reasons why you are trying to create something better than Guard?