reflex

The article mentions GOW[0] for a file watcher. If anyone is looking for a non-go specific one, I've really enjoyed reflex[1]. Makes it super easy to reload different parts of a project based on what type of file has changed. [0]https://github.com/mitranim/gow [1]https://github.com/cespare/reflex

Reflex for go: https://github.com/cespare/reflex

I have been using reflex https://github.com/cespare/reflex for the same thing in some of our docker projects

entr is written in C, watchexec is written in Rust. There's another one that I've used that is written in go: https://github.com/cespare/reflex I am inclined to use watchexec next time I need one, because like go, I can read it more easily than c, but also because I looked at the web page and GitHub repo and it seems worth trying. For instance, it shows how to use it as a library instead of just as a command-line tool. https://watchexec.github.io/

The best tool I’ve found for this job is reflex[1]. It’s easy to setup, Go agnostic, very « UNIX » in its philosophy, doesn’t get in your way with its own logs, and just works. Before that I used realize but it has the bad behavior of always adding it’s own prefix to the logs, which sucks. [1]: https://github.com/cespare/reflex

I use a similar tool called reflex: https://github.com/cespare/reflex

I would love to see Go have first class support for watch/hot reload while developing Its not first class, but I have been happy using reflex [1] for non-http and gin [2] for http. Combined with Go's fast compile they work as well as a hot reload. [1] https://github.com/cespare/reflex [2] https://github.com/codegangsta/gin

https://github.com/cespare/reflex works well too.

When I edit graphviz, I usually watch my source file(s) with reflex [1] to re-generate the output image, and use an image viewer with auto-reloading support like sxiv [2]. Works really well for me! 1: https://github.com/cespare/reflex 2: https://github.com/muennich/sxiv

If I may engage in a little self-promotion, my tool reflex github.com/cespare/reflex is similar, but more general-purpose. (It's written in Go, but it's not for Go.)

> They are all as complicated if not more complicated than just writing HTML. They all have a bunch of rules and special cases. I'd rather just write in HTML which I already know. I find that Markdown is significantly easier/faster to write than HTML and, more importantly, easier to read in its un-rendered form. To me (and presumably lots of other people, given Markdown's ubiquity) it's well worth learning the relatively small syntax. Edit: Here's a quick comparison with a README.md from one of my projects: Rendered: https://github.com/cespare/reflex/blob/master/README.md Markdown: https://raw.githubusercontent.com/cespare/reflex/master/READ... HTML: https://gist.githubusercontent.com/cespare/ad6c41aa28583cac8... Three things I notice from this example: - The verbosity of an XML syntax with HTML is annoying, particularly the need for clos