potiuk commented on issue #15635:
URL: https://github.com/apache/airflow/issues/15635#issuecomment-1020051090


   And also copying my comment from 
https://github.com/airflow-helm/charts/issues/488#issuecomment-1020015439
   
   Just to explain where it comes from.
   
   The problem is mainly because many of the dependencies are scrambling to get 
proper "architecture" support. This is a good thing - long term - that Apple 
switched to ARM (more choice is a good thing) and it pretty much forced all the 
developers to pay attention.
   
   The ARM support has to - unfortunately - bubble up - from OS support for ARM 
(already there for linux for quite some time thanks to Android), then low-level 
libraries in C/C++/Rust, then Python low-level libraries (like Numpy) finally 
applications and tools like Airflow (or for example MySQL or MSSQL that have to 
provide clients and images that are also ARM-based). All this is a huge effort 
by all parties involved - not as much to make the change but mainly to make 
sure that it works and that they have the right continuous integration in-place 
to support it, so that they can release the software with confidence after 
passing all the tests.
   
   I think ~ mid 2022 will be the time where all this effort will be nearly 
complete and those who won't be there will have to do it as they will lag 
behind (this is the main reason I deffered buying M1 MacBook as I knew it was 
very far from being ready when M1 was released first and I hated the touchbar, 
and lack of HDMI. MagSafe is great BTW and I am glad it is back).
   
   So crossed_fingers that all our dependencies will be ready soon (or at least 
the crucial ones that will allow Airlfow to reliably and reproducibly build ARM 
image and add CI harness for it).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to