diff options
| author | Olivier Lacan <hi@olivierlacan.com> | 2017-12-13 16:17:06 -0500 |
|---|---|---|
| committer | Olivier Lacan <hi@olivierlacan.com> | 2017-12-13 20:50:27 -0500 |
| commit | acc03bb695d39682c5e7e4b1338ca96ad57d8ec6 (patch) | |
| tree | 87f6b81155fd6edcf8a753911d40e1e46d169ec5 /activerecord/test/cases/finder_test.rb | |
| parent | 924267516723b4cb69be64de456f8552e5ed55e6 (diff) | |
| download | rails-acc03bb695d39682c5e7e4b1338ca96ad57d8ec6.tar.gz rails-acc03bb695d39682c5e7e4b1338ca96ad57d8ec6.tar.bz2 rails-acc03bb695d39682c5e7e4b1338ca96ad57d8ec6.zip | |
Provide instant feedback when booting Rails
I've noticed during pair/mob programming sessions with peers that
despite the speed boosts provided by Bootsnap and Spring, there is a
noticeable latency between firing a bin/rails server command and any
feedback being provided to the console. Depending on the size of the
application this lack of feedback can make it seem like something is
wrong when Rails is simply busy initializing.
This change may seem gratuitous but by just printing one line to STDOUT
we're giving a clear signal to the Rails user that their command has
been received and that Rails is indeed booting. It almost imperciptibly
makes Rails feel more responsive.
Sure the code doesn't look very fancy but there's no other appropriate
place I could think of putting it than boot.rb.
Compare these two GIFs of booting without and with this change:
Before:
After:
Diffstat (limited to 'activerecord/test/cases/finder_test.rb')
0 files changed, 0 insertions, 0 deletions