Suggested integration with listen-compat about jekyll-watch HOT 3 CLOSED

Do you think you're going to change around the Listen API frequently?

from jekyll-watch.

@parkr - actually, no - just that fixing some bugs/issues may need architecture changes (e.g symlinks and encoding). Further more, I thought it would be useful for users to configure Listen "outside" the apps they are using.

If you see no reason to jump on board (which is totally reasonable), you can wait until something does break in a way where using Listen-compat takes care of things.

Listen is just incredibly complex and is getting to a point where fixing one thing is likely to break something else. Also, some people want compatibility, some people want better performance and others want more features - so I'd like to make Listen "hackable" without involving me or authors of apps using Listen.

If I screw up (has happened, no matter how hard I try not to), it doesn't make sense for users to report problems in Jekyll - those version could just be blacklisted in Listen-compat.

Also, a new version of Celluloid could be released which causes issues (likely, given Listen uses Celluloid in a "non-pure" way - I may have to deal with this at some point) - Listen-compat would be a place to let users know if their setup has issues.

Also, some software is locked to old versions of listen, or users can run Jekyll without bundler. And, there are lots of designers who aren't even going to bother updating gems or learning about Bundler and Gemfiles.

"So if it isn't broken, don't fix it" - but if it does break, any "workaround" or "warnings" or other non-Jekyll stuff should go to Listen-compat (because Jekyll shouldn't care in the first place).

from jekyll-watch.

We use pessimistic ~> x.x versioning, so the interface shouldn't be a problem. If you screw up (I do this on occasion, too, it's just human) then release a PATCH 0.0.x ASAP. In the meantime, we can downgrade. Jekyll leaves the user with a lot of flexibility so I don't think we'll need this. But thank you :)

from jekyll-watch.