3 ms·
What you're missing is that for much of enterprise software before Airflow, everything was steaming rubbish. Airflow is... not amazing. But by the standards o
by urthor 5y ago
What you're missing is that for much of enterprise software before Airflow, everything was steaming rubbish.
Airflow is... not amazing. But by the standards of horrible enterprise software we've all been subjected to, it's not that bad.
If you're complaining about Airflow, wait for the day you're forced to use an internally built database client.
That's Afghanistan.
Our proprietary AWS wrapper takes 45 damn minutes on a good day to allocate a VM. The AMI is built in two minutes. TWO.
I'm sure in 5 years Dagster and Prefect will have improved gradually in lots of incremental ways. For now Airflow is pretty solid.
- sparsely 5y agoI have memories of pasting 10 line powershell scripts into one of those tiny windows XP text entry boxes, and being happy I could do so!
- the_af 5y ago> If you're complaining about Airflow Wait, maybe I explained myself badly: while I am complaining about some things I dislike about Airflow, at the same time I'm saying it's better than the random assortment of cron jobs we had before, and pushing back against the idea of "unbundling" it and going back to disparate tools by separate vendors. I like writing Python code, I feel in control.