cron

It's not only that the documentation is quite bad. It's also the rest of go. Here's what it spews when you specidy a dependency incorrectly Dependency: github.com/robfig/cron v3.0.1 go's handling of this: require github.com/robfig/cron: version "v3.0.1" invalid: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v3 Right. What? I solved it by looking through this issue that comes at the top of Google Search for it: https://github.com/golang/go/issues/35732

Thanks :) Yup, I source news from local news portals as shown in the website. Hourly, each source is crawled in each relevant category to get the latest news items, and stored into a database. Another job then goes and fetches the body of all these articles. (I use https://github.com/robfig/cron for cron jobs). Server and HTML templates are both Golang. As for the aggregation (grouping) algorithm, I'll just say that it's straight out of the textbook http://infolab.stanford.edu/~ullman/mmds/ch3.pdf

Totally fair - no experience here in deploying OCaml for production. Agreed that the language and major libraries are phenomenal. My intuition is that the maintenance time cost of writing and extending these abstractions from scratch in the face of changing business requirements is higher than the time cost of using a less perfect language but richer ecosystem; but that could be totally wrong. Glad the language is shining in your situation. Can you elaborate more on team composition, tenure, learning curve, and use case? > 10 minutes with angstrom and unixlib? https://github.com/robfig/cron is ~1.5KLOC - sure, it's Go, but that's a bit more than 10 minutes in any language, especially to change gears and think through edge cases. I'd prefer for things to Just Work. > low quality third party libs (which are usually provided by go) My experi

I like go's anti-magic philosophy, if not simply because of how utterly hard I've being burned by magic. routing is best left to you to write explicitly, there's no pancea, because if you use this solution and you then need to do something even slightly more complicated, then you now have two nomenclatures, and two interacting systems. A simple library is what is needed for parameter parsing and validation, not a framework that provides it wholesale. There are lots of session implementations, a library might intice you with its offerins, not a frameworks im pretty sure this one size fits all solution should work in some manner Templating was already there, they offer it again? There's also competing libraries to go's templating, use those. Caching? You mean for templates? That's not complicated to do. For databases? There are databases th