https://www.onlyoffice.com/saas.aspx - very decent compatibility with Office and speed; is a European company; much of the functionality is open source.
Also check out https://github.com/DIYgod/RSSHub, it's aggressively compatible with websites that refuse to do RSS, and has a large community that keeps it up to date
Anything which doesn't try to process the sql file but instead just passes it to the db to deal with, e.g.
psql -d mydb -f migration.sql
I use a home-built solution that does this (160 lines of go), doesn't seem very exotic to me and did not require lots of work as there are only a few requirements for a working solution: Unique ordered names for migration sql files, use the db to store metadata about migrations run, use the db tools to run migrations.
I searched all over the web for a reliable and scalable plain message queue that could work in a full disk-backed mode, not requiring the data to fit in memory.
Was very impressed with how little RAM and CPU it consumed under load.
Was using it in production before. NATS itself is great and reliable.
However disk persistency is done with nats-streaminh and i had big issues with it's Raft file based store, where it would stop accepting messages after a short network issue, and not get unstuck unless I destroy the whole nats-streaming data storage amd start from scratch.
Also raft means 3x disk usage for one queue, since its fully replicated
I see what you are saying, but I still think it is a far cry from having content providers simply providing the feeds themselves.
In the same way that I don't think that YouTube allowing users to submit closed caption transcripts, or machine generating them, any substitute for the content creator
providing them in the first place. I'm sure in the near future, smart TVs will be able to machine generate closed captions from the audio, but I still don't think we should let television producers off the hook for providing captions.
RSS should be the default. And it is not hard to generate RSS.
I happen to think that big platforms only reluctantly adopted RSS over a decade ago because it was a "standard", and because they felt that it was popular enough to justify the traffic from it. But they do not like RSS. It works against their analytics, their ads, and their control of the presentation.
And while it is cool that people are crowd sourcing scrapers, I think the real solution is to promote RSS itself and encourage more platforms to simply provide it. And organizations like Mozilla taking Facebook's position that RSS is obsolete has been profoundly unhelpful to the web.
