Spend a few hundred dollars on hardware - install once - things run faster. Go about your business.
or
Learn to program in a variety of languages. Join multiple projects. Grab code, start hacking. Lobby to get your patches accepted. Deal with months of political infighting on various projects. Consider forking projects because patches aren't accepted. Deal with your contributions being removed or broken in future commits. Contend with slower hardware during the months (or years) it takes for this process to occur for all the major programs you run (and forget about the dozens of smaller programs you use daily).
Hrm... yeah, I can see why getting faster hardware is a tad silly. Not sure what the OP was thinking.
Given that it takes 2.1 seconds, can we assume that at least some of that time is physical loading from the drive, and has nothing to do with the actual program itself? Faster hardware does indeed work. And I'm saying this as someone with SSD lust, and can't quite justify the expense of a 256g or 512g SSD. :/
I mean, really?
Few second wait times are a real burden to me, because it's too long to go do anything else productive, but still slow me down.
And when this happens multiple times per day for multiple apps - how much coffee can you drink?
A) wait 2 seconds
B) Buy a $200 hard drive
C) Fork Firefox yourself
waiting the 2 seconds seems like the sanest solution. Perhaps I've been working on budget hardware for so long that it doesn't bother me anymore, but the delay just doesn't seem like that big of a deal.
I imagine checking your email or reading HN kills more time per day than waiting for programs to start.