But if you do know what you're doing - like myself and many other engineers - you don't need hand holding.
I would not consider SES "shit" because it does not baby-sit you throughout the setup process. The documentation was solid, and I had a lot of freedom to customize a solution specific to my use case. Overall working SES has been an enjoyable experience.
But maybe my mind will change 1 billion emails later haha we'll see.
Can you elaborate on why SES is shit? I've been using it for about 6 months now to run a small newsletter and haven't experienced any issues with deliverability.
> You cannot browse the data structure without an active cluster
That's one of the reason's I'm interested in delta-rs [1], which has delta lake bindings for Python. Would love to read a delta lake table into a native python object without the need for spark.