3 ms·

I appreciate your candor educar. I'm also on the fence with some software: - iTerm2 prompted me to opt-in to some pre-beta phase, it was widely discussed on HN

I appreciate your candor educar. I'm also on the fence with some software: - iTerm2 prompted me to opt-in to some pre-beta phase, it was widely discussed on HN and the author was criticized. - Just this week homebrew announced they integrated Google analytics to help understand their user behaviour and were called out and extensively critiqued. - ohh-my-zsh frequently breaks my workflow to prompt me to ask about checking for updates, this is a thinly veiled "statistics" collection.. if I had a problem with my shell, I'd check for updates by hand, I'm a developer I can't work without my shell. Those points fly in the face of the extreme freedom-of-software view, but if people don't want to use the latest version of Capistrano they can stick with the old version, or volunteer to back-port changes they care about and we'd be happy to release a dot-release with any bug fixes for a previous version. Thanks also for the kind words in regard to Cap being "great software", as an infrastructure tool we have a privileged place in a hot, and potentially dangerous path for all our users, right between them, and their uptime! That trust is not lost on us, and we walk the line.

educar 10y ago
If people are concerned about the gem installation (and not the promotion itself), I can suggest that you promote harrow differently. Maybe put it as part of some command's output. Like "Cap by codebreaker (thanks to funding by Harrow.io)" or similar.
- codebeaker 10y ago
  > If people are concerned about the gem installation (and not the promotion itself), I can suggest that you promote harrow differently. Maybe put it as part of some command's output. Like "Cap by codebreaker (thanks to funding by Harrow.io)" or similar. Actually we wanted to ping people once not on every time they use the tool, this is the lesser evil, it also allows us to push something to turn off the integration without having to bump Capistrano's version for no reason, simply by deploying another (noop) version of the integration gem.

educar 10y ago

If people are concerned about the gem installation (and not the promotion itself), I can suggest that you promote harrow differently. Maybe put it as part of some command's output. Like "Cap by codebreaker (thanks to funding by Harrow.io)" or similar.

codebeaker 10y ago
> If people are concerned about the gem installation (and not the promotion itself), I can suggest that you promote harrow differently. Maybe put it as part of some command's output. Like "Cap by codebreaker (thanks to funding by Harrow.io)" or similar. Actually we wanted to ping people once not on every time they use the tool, this is the lesser evil, it also allows us to push something to turn off the integration without having to bump Capistrano's version for no reason, simply by deploying another (noop) version of the integration gem.