Yes, at our company we are using it very extensively. I genuinely believe we're near the forefront of usage. We have multiple isolated OpenClaw instances serving as employee within Slack.
it's a venture backed software + services company. the things we use openclaw for are not specific to what our company does. It's literally being used as an additional employee(s). Think about what people do -> OpenClaw does a subset of those things. Emailing, pulling data our of our platform to putting them into PDFs because a customer requested it, updating things in our CRM, answering support tickets, internal help desk type work... "how does so and so feature work in xyz edge case"... etc etc etc.
Those with a bit more experience understand faster is not always better. Databases thought to be battle-tested encounter incredibly complex and near impossible to predict failures of the most absurd kind. You can go back and look at some crazy behavior hundreds of people have worked to resolve regarding TTL contracts within Redis.
The ease of "appearance of value" today is the uncanny valley for software. The repo looks professionally organized, you can PAY for it, the preliminary benchmarks are looking good. Overlooked are the testing, validation, backup, failure recovery, practical behaviors, and most importantly: honesty.
These projects would get more love if it was declared up front that they were heavily AI generated projects and shouldn't be used in production since it has the air of practical utility.
It's probably a great drop-in replacement for Redis for a raspberry pi project that has low stakes. The smaller 1MB disk footprint and the performance difference could be impactful. Personally, I wouldn't be using this in production for at least a few years after hobbyists have their go at revealing its hidden near-guaranteed flaws.
At least I can broach TTL issues and gather reasonable insight on Redis vs Elasticache nuance based on the thousands who have encountered the issues.
Because it's AI slop that some grifter vibecoded yesterday with no unit tests that supports about 2% of Redis's feature set (notably missing transactions and any attempt at data integrity)
How does Codex / Claude Code compare to working within Cursor with the chat and agents? Are they effectively the same thing?
Is one significantly better than the other. Please share your experiences around this I’m trying to be ass effective of an engineer as I can be at our company. - Mike
My best answer is try your 100 free trial searches and compare the search experience. Kagi has every incentive to create a superior search experience or you do not pay. For Kagi, every customer matters.
> How is this better than using Google with an ad blocker?
Rubber duck to a battleship.
The number of times I've found something in seconds that a co-worker was digging around in pursuit of for minutes has by this point escaped me. Were you around for Alta Vista vs. Google? This feels the same. The only difference is it's paywalled, which for the consumer, is generally good--it means the benefits won't be generalised and the product will remain an elite minority offering that doesn't gain traction with SEO bots.
Are these rates for both commercial (part 121/135) and part 91 private pilots? I would imagine the costs to be quite easy to swallow if you're a captain at a big airline but for someone flying occasionally, a per month rate might be expensive. How about a per distance (or time) pricing, if that's possible?
Yes. 15K revenue or even profits per month wont get you few million. Having said that, I buy small software/saas products/companies. If you are interested in potentially selling, hit me up. Criteria is min $10k-$50k/month average revenue.
