by evantahler on 8/3/23, 7:43 PM with 6 comments
by ssddanbrown on 8/3/23, 9:45 PM
Airbyte has previous of advertising their offering as open source while not really being as per the OSD[2]. This has been raised with them previously but without response [3][4]. They've also been extending their use of ELv2, recently moving many of their existing MIT licensed connectors to be ELv2 [5].
I don't personally take issue with the choice of license here, I respect the right to protect your work and choose a license that works for you, I'm just against the misuse of open source wording.
[1] https://github.com/airbytehq/airbyte/blob/master/LICENSE [2] https://opensource.org/osd/ [3] https://github.com/airbytehq/airbyte/issues/9246 [4] https://github.com/airbytehq/airbyte/issues/17118 [5] https://airbyte.com/blog/update-on-airbytes-license
by thenaturalist on 8/3/23, 9:34 PM
I don't know what it is, some people bring up the crazy valuation, but it just strikes me that a for such a targeted use case their execution game was great initially, but by now when discussing integration tools they are receiving quite some critique with regards to speed, stability and configurability.
It sure seems to me their OSS offering has not received much love while their cloud product is not close to peer functionality (missing custom connectors being a huuuuge one as of two months ago). All the connectors in the world ain't worth much if the core platform to run them on isn't stable, slow or doesn't support all of a company's data sources, inevitably containing long tail ones not covered by the core team?
Am I being overly negative here?
I'd love to hear what others think.