Agree about the slow part of Singer based connectors. Singer has some great high level designs but also made some decision decisions poorly.

That’s why we at Mage (https://github.com/mage-ai/mage-ai) adopted Singer Spec but made enhancements on top of them (e.g. batching, unique constraint handling, etc).

Another point that Lauren pointed out about the community driven part is spot on. Some pros of Singer is that it has so many taps and targets. However, some cons of Singer include lack of standardization and ownership,

That’s why, we at Mage wrote some wrappers around the Singer Spec to standardize the way taps and targets are executed while still adhering to the spec.

We’re also open-source; but each Singer tap or target we endorse and bring into the repo, we take full accountability of. So any Singer tap or target you use inside Mage is our responsibility if something goes wrong. So we take the SaaS mindset of accountability. Anyone can contribute, but we’ll maintain and upkeep.