5 ms·

Has nobody mentioned, that this is just wego as a service?

• szszrk 6y ago
  Their github page explains this early in project page, so no harm done, I guess?
  • KitDuncan 6y ago
    Oops, don't know how I missed that. Sorry!
    • igor_chubin 6y ago
      To say truth, it is not just a wego as a service since many years, but is started like that indeed Now it has a lot of additional features: * one-line output for status lines * astronomical information * translation to 70+ languages * geolocation * full fledged multilingual location search * HTML frontend * PNG frontend * Slack support * scalable architecture (it handles 10M+ queries daily for the moment of writing, with avg processing time under 30 msec) It took one weak for the initial wego-as-a-service wrapper implementation, and more than 4 years (and 99 contributors) for the rest. But we of course honor wego, and mention it in the README, and on each HTML page in browser
      • elcomet 6y ago
        Nice ! Did you contribute back your improvements to wego ?
        • igor_chubin 6y ago
          No, because they are not implemented as a part of wego; wego is used just for visualization of one of the views (v1). The rest is implemented outside of it
• suprfnk 6y ago
  What is wego? Google only seems to give me travel companies and alternatives.
  • capableweb 6y ago
    I didn't know either! Searching for "wego weather" shows this CLI: https://github.com/schachmat/wego https://github.com/schachmat/wego Reading the readme for chubin/wttr.in also clarifies what "wego" is: > wttr.in uses wego for visualization and various data sources for weather forecast information. "wego" in that sentence is also linked to schachmat/wego so seems to confirm is that one.
    • igor_chubin 6y ago
      See my comment in the neighbor thread