Re:Memory access on the Apple M1 processor
by coldtea on Wednesday January 06, 2021 @06:25PM
(#25664204)
>Well, and on the Mac, it's not the only method. The walled garden here has big open gates.
Gates are not incompatible with walled gardens. Most walled gardens have those.
Plus, I mentioned the walled garden as a good thing. It's part of the Apple proposition (even if not alll get it), and part of what it enables it to move at the speed it does (whether in the right or wrong direction).
But one can susbstitute "walled garden" with "tight control of the OS, hardware and imposed requirements on most of third party software, and willingness to enforce hard schedules (e.g. regarding removing 32-bit, OpenGL, etc) to all (or tons) of its developers at once.
Re:Memory access on the Apple M1 processor
by astrange on Wednesday January 06, 2021 @09:18PM
(#25666460)
32-bit Windows software is actually supported through WINE and works in Rosetta.
Re:Memory access on the Apple M1 processor
by coldtea on Wednesday January 06, 2021 @11:01PM
(#25667149)
This is about 32-bit OS X software/libs.
Re:Memory access on the Apple M1 processor
by ogre_codes on Wednesday January 06, 2021 @06:29PM
(#25664254)
They are little tiny 6" tall walls that you can step over. Like micro-walls. Except for the bits where you have no walls at all. Like if you install literally any programming language, HomeBrew, or MacPorts.
The walls in the walled garden only exist in the heads of people who never use a Mac.
That said, all software on the Mac, post-Catalina, has to be 64-bit, whether it's distributed through the Mac App Store or not, because the 32-bit system libraries are no longer included at all.