Rami Awar
@iamrami.bsky.social
Open source developer and content creator
✨ Simplifying data analysis and visualization
🚀 Try it out: http://dataline.app 🚀
✨ Simplifying data analysis and visualization
🚀 Try it out: http://dataline.app 🚀
Have to say, I'm really happy for them with how much their Github contributors have grown.
Now that Airflow v3 is language agnostic, they can also get contributions for different SDKs which will get SO MANY more contributions. This wasn't just an architectural unlock!
Now that Airflow v3 is language agnostic, they can also get contributions for different SDKs which will get SO MANY more contributions. This wasn't just an architectural unlock!
March 21, 2025 at 7:56 AM
Have to say, I'm really happy for them with how much their Github contributors have grown.
Now that Airflow v3 is language agnostic, they can also get contributions for different SDKs which will get SO MANY more contributions. This wasn't just an architectural unlock!
Now that Airflow v3 is language agnostic, they can also get contributions for different SDKs which will get SO MANY more contributions. This wasn't just an architectural unlock!
✨ DAG Versioning
Straightforward: Now possible to view historical versions of DAGs along with their run information. Much better visibility, prevents loss of information for debugging/auditing
✨ Modernized UI
Not just a facelift, now uses React, Typescript, Chakra UI, Neutrino, React Query.
⬇️
Straightforward: Now possible to view historical versions of DAGs along with their run information. Much better visibility, prevents loss of information for debugging/auditing
✨ Modernized UI
Not just a facelift, now uses React, Typescript, Chakra UI, Neutrino, React Query.
⬇️
March 21, 2025 at 7:56 AM
✨ DAG Versioning
Straightforward: Now possible to view historical versions of DAGs along with their run information. Much better visibility, prevents loss of information for debugging/auditing
✨ Modernized UI
Not just a facelift, now uses React, Typescript, Chakra UI, Neutrino, React Query.
⬇️
Straightforward: Now possible to view historical versions of DAGs along with their run information. Much better visibility, prevents loss of information for debugging/auditing
✨ Modernized UI
Not just a facelift, now uses React, Typescript, Chakra UI, Neutrino, React Query.
⬇️
✨ Run workers "in any language":
- Airflow 3 is language agnostic
- Current language SDKs available: Python
- Upcoming support: Probably Golang
- This is now possible thanks to the new Task Execution Interface!
⬇️
- Airflow 3 is language agnostic
- Current language SDKs available: Python
- Upcoming support: Probably Golang
- This is now possible thanks to the new Task Execution Interface!
⬇️
March 21, 2025 at 7:56 AM
✨ Run workers "in any language":
- Airflow 3 is language agnostic
- Current language SDKs available: Python
- Upcoming support: Probably Golang
- This is now possible thanks to the new Task Execution Interface!
⬇️
- Airflow 3 is language agnostic
- Current language SDKs available: Python
- Upcoming support: Probably Golang
- This is now possible thanks to the new Task Execution Interface!
⬇️
✨ Run workers "anytime" means:
- Event based triggers were already kinda there, but now can also trigger automatically based on external resource changes, no user setup needed
- Ad-hoc executions
- Process data in partitions, independently (ex. time or segment partitions) ⬇️
- Event based triggers were already kinda there, but now can also trigger automatically based on external resource changes, no user setup needed
- Ad-hoc executions
- Process data in partitions, independently (ex. time or segment partitions) ⬇️
March 21, 2025 at 7:56 AM
✨ Run workers "anytime" means:
- Event based triggers were already kinda there, but now can also trigger automatically based on external resource changes, no user setup needed
- Ad-hoc executions
- Process data in partitions, independently (ex. time or segment partitions) ⬇️
- Event based triggers were already kinda there, but now can also trigger automatically based on external resource changes, no user setup needed
- Ad-hoc executions
- Process data in partitions, independently (ex. time or segment partitions) ⬇️
✨ Run workers "anywhere" means:
- Workers can be upgraded independently! (this is such a pain point in all task exec frameworks)
- Flexible deployment (public, hybric, private cloud, on-prem, ...)
- Better task isolation == security (Task exec interface architecture) ⬇️
- Workers can be upgraded independently! (this is such a pain point in all task exec frameworks)
- Flexible deployment (public, hybric, private cloud, on-prem, ...)
- Better task isolation == security (Task exec interface architecture) ⬇️
March 21, 2025 at 7:56 AM
✨ Run workers "anywhere" means:
- Workers can be upgraded independently! (this is such a pain point in all task exec frameworks)
- Flexible deployment (public, hybric, private cloud, on-prem, ...)
- Better task isolation == security (Task exec interface architecture) ⬇️
- Workers can be upgraded independently! (this is such a pain point in all task exec frameworks)
- Flexible deployment (public, hybric, private cloud, on-prem, ...)
- Better task isolation == security (Task exec interface architecture) ⬇️
Only works if your standing desk is low enough and then your monitor arm is high enough.
Then your elbows are above the wrist, and the arm can go up and down while the wrists stay stable.
It's a pretty delicate balance I'd say.
Then your elbows are above the wrist, and the arm can go up and down while the wrists stay stable.
It's a pretty delicate balance I'd say.
January 16, 2025 at 12:13 PM
Only works if your standing desk is low enough and then your monitor arm is high enough.
Then your elbows are above the wrist, and the arm can go up and down while the wrists stay stable.
It's a pretty delicate balance I'd say.
Then your elbows are above the wrist, and the arm can go up and down while the wrists stay stable.
It's a pretty delicate balance I'd say.
Cause it was never marketed😅 but I intend to change that!
I was lucky to have found it a long time ago randomly tbh, never would've thought I'd be the maintainer one day 😄
I was lucky to have found it a long time ago randomly tbh, never would've thought I'd be the maintainer one day 😄
November 28, 2024 at 8:14 PM
Cause it was never marketed😅 but I intend to change that!
I was lucky to have found it a long time ago randomly tbh, never would've thought I'd be the maintainer one day 😄
I was lucky to have found it a long time ago randomly tbh, never would've thought I'd be the maintainer one day 😄
Very interesting infra too. I want to dive into this whole 'data ownership' / 1 SQLite file per person design.
Imagine every software out there gave people control of their data like this.
I want any software I build in the future to offer that.
Imagine every software out there gave people control of their data like this.
I want any software I build in the future to offer that.
November 25, 2024 at 10:43 AM
Very interesting infra too. I want to dive into this whole 'data ownership' / 1 SQLite file per person design.
Imagine every software out there gave people control of their data like this.
I want any software I build in the future to offer that.
Imagine every software out there gave people control of their data like this.
I want any software I build in the future to offer that.
Every time I rant about this to friends they'd be like "aaah but bluetooth!"
Still not over it... My old QC headphones still far exceed any of the expensive wireless crap out there
Still not over it... My old QC headphones still far exceed any of the expensive wireless crap out there
September 8, 2024 at 7:49 AM
Every time I rant about this to friends they'd be like "aaah but bluetooth!"
Still not over it... My old QC headphones still far exceed any of the expensive wireless crap out there
Still not over it... My old QC headphones still far exceed any of the expensive wireless crap out there