SiguzaIf watching the [arm64] tag on Stack Overflow has taught me anything, it's that interpreted languages basically only work on x86_64. Most C source tarballs can just be recompiled for arm64, but lmao good luck if your python or npm dependencies are "not available" for arm64.
I guess it has also taught me that Linux users have no idea that `uname -m` is only the kernel arch and userland can be whatever, and that you have to make a conscious effort to find the version of Raspberry Pi OS that actually has a 64bit userland. 🙄
évelyne@siguza is the kernel 32 bit still? hasn’t it been many years that they’re using arm64
@evelyne the kernel is 64bit, but userland is 32bit (on the default OS image, that is - there is one with 64bit userland but you have to dig for it). So every other week there's someone on Stack Overflow, confused why this arm64 binary they downloaded doesn't run even though `uname -m` says arm64.
Saagar Jha
Emma (IPG)
Cryptic@siguza Can confirm. Professor made us force aarch32 userland on the pi to fit the course.
wetfeet2000@siguza I agree with the general principle. But in practice I've had a great time on my work Mac M1 with mambaforge and python! Once in a while I have to install a dependency with brew, but I don't think I've ever had to abandon a python library because of the inability to build for ARM yet. 🤞