@Henrik Comparing with general purpose watchers, being Go-specific makes it easier to remember and lets it work well for Go projects with no configuration. Mnemonically, it's invoked exactly like "go". It ignores non-Go files by default. I can imagine the "go" tool eventually getting a "-w" flag that replaces "gow" as-is.
In addition, every other tool I've tried had AT LEAST one of these problems: * noisy output * delays in the file watcher, usually not configurable; this drives me crazy * creates garbage files * eventually needs configuration files * unreliable * can't stop and restart the subprocess * can't clear the terminal on restart * complex codebase, unreasonably difficult to hack on That's just my experience. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
