I don't like the sound of `--wet-run`, but on more than one occasion I've written tools (and less frequently services) that default to `dry-run` and require `--no-dry-run` to actually make changes.
For services, I prefer having them detect where they are running. Ie if it's running in a dev environment, it's going to use a dev db by default.
I might be misremembering, but the initial core series (core 2 duo/quad) was still a bit behind AMD's Phenom line. Core was definitely better than the old netburst architecture, but I don't really remember Intel regaining dominance until the core i series/AMD FX.
This was also like high school/college for me, so I could be way off.
I'm not a physicist, but I believe that's the exact insight that led to special relativity. It goes something like: If your moving at 1,000kmh next to a jet moving at 1,100kmh then the jet is moving at 100kmh relative to you. Eventually people realized those wasn't the case with light. No matter how fast the observer is, light still moves at 299,792,458m/s. Einstein figured out that if the speed of light is fixed despite relative motion, then time must slow down as you move faster. So from the perspective of a photon no time has passed since its departure.
Edit: To be completely fair this doesn't anything for the front end, unlike create-react-app. I'm not a web developer so I don't really have a dog in this fight.
For services, I prefer having them detect where they are running. Ie if it's running in a dev environment, it's going to use a dev db by default.