What we found with RPCN (redpanda connect)/old benthos is that most systems are very slow and only cpu intensive things require manual CPU instruction optimizations like the snowflake connector we wrote (https://docs.redpanda.com/redpanda-connect/components/output...). The bulk of it is just about completeness. Go feels like the Perl of the 2020s. Cool little libs for just about everything.
It is not FUD. It is deterministic. Reproducible on your laptop. Out of all the banks I work with only a handful of use cases use rf=5. Defaults matter, because most people do not change them.
incorrect. the intend is to have it be a project that is thriving, see the last 2 additional partnerships that landed as apach2 connectors: https://redpanda.com/blog/redpanda-connect w/ peerdb, and ockam.
As the founder and CEO - did you not think to stop and look at the market? For example what happened recently with Terraform/OpenTofu, Redis, etc?
You basically took the same route as these companies and while your intent may be different, from the outside it looks like another company making a grab an Open Source software with changing licences and renaming products.
Again, it may not be your intent but you made the first mistake in marketing which is - see how others have done it and what the outcome it.
For me as a Tech Lead/Architect - currently looking at event-based architecture, this is a bit of a turnoff of the entire product stack - because it suggests you might be lining things up to sell off.
That's not the most constructive way of dealing with criticism.
I get that people having a problem with the way that your company does business might seem like a personal attack (especially if you're the CEO), but that sort of instant aggressive stance does nothing to alleviate people's concerns, and instead rather makes it seem like you're deliberately attempting to shut down a good faith conversation.
we trippled the team. added 3 meaningful connectors for CDC and zero-trust as well multi-lang SDK and kept 99% of the connectors available for ppl to make money on... as well as the core engine remaining MIT. This is about them not wanting to depend on redpanda products which is ok, but the whole thing is hard to believe from a company that has no open source products. it's more like "hey, i don't like it."
I dunno ... when you see some guy from RedPanda on twitter throwing around petty "trademark compliance" [1] threats to memory-hole an entire project ... honestly, it would be malpratice _not_ to immediately fork everything.
The best part of this is "X" is such complete garbage that that post has literally zero context to someone unwilling to ever have an account on the tire fire that it is.
You also managed to be completely tone deaf to the way that developers feel about open source projects. A gradual branding transition can be swallowed, but what you chose to do instead is immediately force everyone to stop using the old name under threat of legal action. Adding new plugins that are proprietary can be tolerated, but if you're surprised that relicensing previously open source code prompted a fork you apparently weren't paying attention to the enormous kerfuffles surrounding recent relicenses by better-loved companies than yours.
you may have not read the blog post i wrote. the engine remains MIT because we had customers that had embedded this in their app and it made sense to keep that. it is 100% about not having to call it "redpanda x" https://redpanda.com/blog/redpanda-connect
at the end of the day, there is plenty of ppl that are making money on this that is not us and that's cool too. we just need to retain the brand of the code we maintain. that's really the thing that matters.
> it is 100% about not having to call it "redpanda x"
It sounds frivolous, but these kinds of trademark shenanigans are a pretty big deal IMO. Mozilla's trademark policies already push the boundaries of what's acceptable in open source--people maintain forks like GNU IceCat just to get around them. Redpanda's forced rebranding goes a lot farther, and personally, it would make me think twice about using your stuff in anything I ship.
> we just need to retain the brand of the code we maintain. that's really the thing that matters.
This is... not really possible with most open source licenses? It's probably possible for you to ban me from using the name "Benthos", but I could almost certainly take your code and distribute it as "Frank's No-Name Blob Thingy" if I retained your copyright notices and license text. I mean that's what this fork is doing, after all.
let's call it what it is. warp never reached out. they do not want to have the name "redpanda" in their UI. that's all. They can* make money on 223 out of 225 connectors. More over the engine* remains MIT.
Not sure that you care, but you are doing an absolutely terrible job representing RP in nearly every comment I’ve seen you make on the topic. You need a coach I guess.
Let's call it what it is: Redpanda took a valuable OSS property, hard renamed it, and applied an arbitrary trademark restriction that did not exist the day before‡ and is not strictly controlled by the open source licence in question — in addition to relicensing part of the repository.
I don't have a dog in this fight. I have never used Benthos. But if someone started what Redpanda with a project that I use — commercially or otherwise — I would instantly fork it. I might not make a big announcement about it the way that Warp did, but I would absolutely be "keeping my powder dry" to see what other nonsense who did the first steps would pull.
You may not like what's happened, and Warp's incentives are certainly not pure, but they are reasonable considering what more than a few corporations have done, including Terraform, Elastic, and Mongo. Please stop pretending that you’re the good guys here.
‡ This is similar to Firefox's trademark restrictions resulting in Iceweasel, etc. There are some people who find Mozilla's restrictions applied to choosing different build settings to be excessive. Are you really surprised that people find your renaming and insta-trademark enforcement to be reminiscent of NewSpeak? Doubleplusungood.
Hey jannesan this is untrue. We pay for ZoomInfo which gives us emails on search engines results. No one is manually filtering on your GitHub. But it should have a link to unsubscribe. Let me know if it doesn’t work and happy to remove. We use a mailing list provider which manages the unsub for us.
