Readit NewsInteresting and varied modern story telling in KDramas and fantastic historical story telling in CDramas.
There's also quite a bit of it to consume from over the years on alternative platforms like Viki.
Sadly most of the "best" can't be found on Netflix so most people just don't have any idea about it.
"Good guys follow rules, bad guys don't."
As if getting the infrastructure to privately build your own model is challenging for people that have the capital to spend on such projects.
In this sense it's literally no worse than reading random "news" articles and somehow taking it all as fact at face value.
If you fall into the trap of taking everything ChatGPT tells you as gospel you've already lost.
As for the so called false promise, this is old man yells at clouds stuff.
Make it suitable for all integration authentication possibilities.
Related, we built a developer oriented Zapier clone for event scale automations awhile back for our internal product. We've since pivoted and have been debating on potentially open sourcing the engine as well.
We built ours using Rust with a DSL for all the triggers, actions, and action inputs/outputs. The actions themselves are defined as APIs, which makes it easy to add functionality in any language. Most of our actions have been built in Typescript.
Is there interest from anyone in potentially using it?
It's a lot faster and easier than dealing with containers and the like.
There are a number of ideas in the database space that the industry is adopting across the board:
- Separation of storage and compute (Neon, AlloyDB, Aurora). Every cloud database should built one. It's a big undertaking, but benefits are undeniable.
- Good query processor for analytics (Snowflake, Velox, Singlestore)
- Open source. Especially in OLTP open source == trust
- HTAP. Can run mixed workload (Singlestore, Unistore): both OLTP (apps) and OLAP (reporting). This has always been a dream, but we still live in the world of dedicated systems: E.g. Snowflake and Postgres.
- Shared nothing sharding (Vitess). This is the most controversial as you lose compatibility with the mothership (MySQL for Vitess). So it's unclear this will be the dominant architecture in the future. I think the world may get to "dynamic sharding" where storage stays separate and compute can be multinode and the user can easily and instantly change the number of nodes.
This looks like a good start.