Date: prev next · Thread: first prev next last
2020 Archives by date, by thread · List index


Hello,

I noticed that Apple will sell machines with homemade ARM processors in a
quite near future see
https://www.news1.news/en/2020/06/mac-with-apple-silicon-processors-the-complete-guide.html

I thought it could be interesting to add this subject in ESC, so these
points may be discussed for example:
- do we want to keep on proposing Mac version ?
If no, quite simple, we can purge some code in LO basecode.
If yes:
- are we prepared for this transition? (perhaps it'll need full Cocoa
framework use, I haven't read the impacts yet)
- have we got enough devs for this?
- budget to buy future Mac with ARM ?
- propose during some time (perhaps 3-4 years) 2 LO releases for Mac : Intel
and ARM
- TB and Jenkins machine with Mac ARMs?
- impact on all external libs, old ones like HSQLDB may bring some problems
(since we're stuck with version 1.8)

It seems Cupertino guys will help some projects like SKIA, see:
https://www.macg.co/macos/2020/06/arm-apple-facilite-la-transition-de-plusieurs-projets-open-source-114881
(sorry French source, didn't find English source)

Perhaps it's too early to talk about it, perhaps there's no big deal, ...
I got no expertise here and no opinion here, just wanted to spotlight this
subject.

Any thoughts here?

Julien



--
Sent from: http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.