Current x86-64 Build very buggy in rosetta, needs a native compile for ARM64
But other reports say it runs just fine.. Either way the idea to make a desktop ARM build has been thrown around a long time (check closed issues) but its in none's plans as far as I know and doesnt really depend on Popcorn Time, more on nwjs on which Popcorn Time runs on, so.. closing this too for now.
(also imho better ask apple to fix rosetta than asking all the x86 apps to become native)
But other reports say it runs just fine.. Either way the idea to make a desktop ARM build has been thrown around a long time (check closed issues) but its in none's plans as far as I know and doesnt really depend on Popcorn Time, more on nwjs on which Popcorn Time runs on, so.. closing this too for now.
(also imho better ask apple to fix rosetta than asking all the x86 apps to become native)
x86 apps need to become native. It is a future requirement. There is nothing wrong with Rosetta, it’s common sense there will be hiccups translating x86 to ARM. Apple isn’t going to continue making a translation platform work better for every single app they get a bug report about, it’s the developers responsibility to update their apps not apples.
I suggest the developers research into Apple’s easy universal compiling program to make the App Universal (native binaries for both architectures).
Like I said Popcorn Time runs on nwjs, which at the moment of writing this has no official M1 or (the long discussed) ARM support.
NW.js is absolutely working on M1 already. There are already OSX ARM64 builds.
As evident by the open issue you just linked (and ofc their releases/downloads pages and documentation) they dont. Those are just test builds with a lot of errors at the moment. There is still a long way until they iron them out and release official, not test, beta or bugged arm versions and even longer until Popcorn Time that still uses a custom compiled 0.44.5 version can update to it.
That being said, you can try and build it for yourself with those builds if you are feeling confident they wont be even worse than the translation, but breaking the app for everyone with them just to immediately natively support a small minority of M1 users is not a very realistic option at the moment.
@tehfalcon-vw you are a bit too fast.
First as @kiriles90 explained we will need a stable silicon build of nwjs and then we will need to make a custom build of nwjs to include the extra codecs and test things. Not sure how much time it will take for all that, but not all contributors have a macbook M1. Else we aren't against, but contributions from M1 owners will be more than welcome.