sontek

This feels like it doesn't have accurate information. For example it has Domo on the list: "Domo was a startup in the Information space." and "Domo's demise can largely be attributed to its struggle to achieve sustainable profitability despite significant funding."

Domo might not be doing well but its still around and is a publicly traded company `DOMO` on nasdaq.

Same thing for Hootsuite, Evernote, OneLogin, Kik, etc.

Do you have examples of your CUE and Github Actions setup?

I was about to ask the same thing! That first sentence confused me

SELECT COUNT(*) FROM users WHERE date_deleted IS NULL AND date_last_activity >= CURRENT_DATE - INTERVAL '120 days';

They haven't posted since February of 2024, seems inactive?

There doesn't seem to be an RSS feed on there

I love this solution, I've implemented a very similar task scheduler at many companies.

I do think the best solution for this is still RabbitMQ. It has the ability to push tasks in the queue and tell it to run at a very specific time called "Delayed Messages" and then it just processes them at that time.

I disagree with this assumption. I work at organizations that have follow the sun coverage so we ended up having engineers in all timezones even though the majority of engineers are in the USA.

One common thing I've noticed over the years is APAC is always the most productive timezone from an engineering aspect because they don't overlap with the disruptive/time consuming meetings.

They get the most focus time out of any of the timezones.

The main tag line says "Drop-in replacement for E in the ELK stack" -- but here you say you aren't a drop-in replacement.

Does this mean you've at least implemented every API that Kibana requires?

I don't believe meilisearch or typesense are API compatible with Elasticsearch. I think the best part of this new tool is its a drop-in replacement.

Edit: Nevermind, in another part of this thread the maintainer said:

    We do get compared to Elasticsearch a lot. While we support some of its APIs, Manticore isn't a drop-in replacement

Which conflicts with the README: "Drop-in replacement for E in the ELK stack"

Do you bring a towel to a hotel? There is no difference. People do wash their things, you don't have to bring your own.

Can you give a brief explanation of the benefits of your policy engine over using cloud custodian?