joerdav

3 ms·

1. 1.▲
   Golang: Migrate from Hashicorps go-multierror to standard library multierror(blog.joe-davidson.co.uk)

   1 points by joerdav 4y ago|0 comments
2. 2.▲
   by joerdav 4y ago

   Most tasks should work trivially on windows actually, xc is shipped with a shell interpreted. The only constraint at the moment is if an executable is used that isn't available on the system.
3. 3.▲
   by joerdav 4y ago

   Thanks for pointing that out, I recently did a rewrite of the docs. Seems to be one that works locally but not on remote. Thanks!
4. 4.▲
   by joerdav 4y ago

   The idea was that even if you don't have xc installed or know it exists, then you could benefit from the Markdown based documentation required for xc to work, and in those cases you could copy & paste.
5. 5.▲
   by joerdav 4y ago

   The reason I prefer xc to makefiles is it is more discoverable I think, when you have a project with a Makefile you often have some documentation in the README that outlines what each Makefile command does. I thought why not cut out the mid
6. 6.▲
   Show HN: Xc – A Markdown Defined Task Runner(github.com)

   113 points by joerdav 4y ago|44 comments