News for hackers. Stuff that matters.
Re:React Native made me give up a project today by vsmhn on Tuesday November 15, 2022 @10:31AM (#33610341)
Judging from your fourth row, it seems to be that "Apple made me give up a project today" is the correct headline, since M1 is apparently the issue.
Re:React Native made me give up a project today by antonvs on Tuesday November 15, 2022 @10:51AM (#33610686)
“My desire to do my work on the latest shiny new tech toy made me give up a project today”
Re:React Native made me give up a project today by akmarinov on Tuesday November 15, 2022 @10:58AM (#33610788)
The native toolset works fine on M1, seems like dependencies issues, like always with React Native.
Re:React Native made me give up a project today by vsmhn on Tuesday November 15, 2022 @11:24AM (#33611197)
I was really tempted to buy a new Mac but there are still lots of gotchas my colleagues had to solve, so I decided to wait. Pushing ARM64 to developer machines still seems like a rushed decision imo, and it definitely shifted resources into building and supporting ARM64, resources that Apple doesn't necessarily pay for. At the end of the day, for me it matters how fast I can do a certain task and how much spare time I have left after I finish it.

Docker example: https://docs.docker.com/desktop/troubleshoot/known-issues/ See the "Known issues for Mac with Apple silicon" tab.

Re:React Native made me give up a project today by skydhash on Tuesday November 15, 2022 @11:34AM (#33611358)
I've been on M1 since last year (Switching from a 2015 MBP) and while there have been some issues, the transition has been going fairly swiftly. The main one I had to deal with was some google library embedded inside React Native Firebase. But the fix was fairly easy (setting XCode and Terminal.app to open using Rosetta). My Mac Mini is enough for daily work and my MBA is perfect for personal uses, never getting hot, even with multiple applications opened.