Jump to content

Recommended Posts

Posted

not sure where to ask...but, I checked app package content and saw liblibpersona.dylib with 1GB of size...HUH...

why such a big files for such a simple program ? is it safe to use it ?

Snímek obrazovky 2021-11-24 v 7.42.14.png

Posted

Affinity is not a simple program, a Persona is a whole workspace and Affinity Photo has 5 Persona workspaces: Photo, Liquify, Develop (RAW), Tone Mapping and Export. 

https://affinity.help/photo/English.lproj/pages/Introduction/about_Personas.html

All of the Affinity apps are safe to use, they DO NOT contain any spyware.

iMac 27" 2019 Sequoia 15.0 (24A335), iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9  
B| (Please refrain from licking the screen while using this forum)

Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions

Posted
9 minutes ago, firstdefence said:

All of the Affinity apps are safe to use, they DO NOT contain any spyware.

This applies if you legally obtain the software from Serif, Microsoft or Apple – the organisations which supply official versions of the software.
This may not apply if you illegally obtain the software from somewhere else – i.e. pirated software.

Posted

Add to what @firstdefencesaid above, then also the fact that for certain hardware platforms like MacOS here, the Affinity libs have to be in fat-binary format (thus being multi-architecture libs, containing compiled code for supporting Intel + Apple Silicon M1 CPUs), which in turn leads to huger lib sizes.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Posted
23 minutes ago, LondonSquirrel said:

Do they have to be in fat binary format? Is it not just as easy to build two versions? (My answer: yes it is easy, and hardly any more work).

The advantage of a fat-binary format is, build-/compile once and run on all supported CPU platforms. Of couse you can also build two different compiled versions, one just for Intel, one for M1, but that's then slightly more effort in setting up automated build-processes.

In the past, during NeXTstep times, where the concept of fat-binaries does stem from, since those days 4 different CPU platforms were supported (Motorola, Intel, Sun RISC, HP Risc), there were some lipo tool runs (for stripping out unneeded architexture binary code) included in the NeXTstep/OpenStep system & app installers. - There is still a lipo command-line tool in MacOS, which offers to do so aka stripping out uneeded architecture binary code, but one has to run that manually from a terminal.

37 minutes ago, LondonSquirrel said:

I wonder is Affinity mandated by Apple to provide a fat binary?

Maybe due to the MAS rules and the way Apple want's third parties to handle & build-up their software nowadays. Another reason might be, so Rosetta can be used on M1 hardware even for apps & parts which don't have been natively adapted/converted to M1 etc.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Posted
1 hour ago, LondonSquirrel said:

I went through a migration from Sun Solaris on Sparc to Intel. I don't remember if fat binaries were even possible on Solaris

Can't remember either for Solaris itself, though under NeXTstep on a SPARCstation it was possible to build an NeXTstep/OpenStep related fat binary, since ...

Quote

... The version of the GNU Compiler Collection shipped with the NeXTStep Developer Tools was able to cross-compile source code for the different architectures on which NeXTStep was able to run. For example, it was possible to choose the target architectures with multiple '-arch' options (with the architecture as argument). This was a convenient way to distribute a program for NeXTStep running on different architectures.

It was also possible to create libraries (e.g. using libtool) with different targeted object files. ...

... so if there was some CC cross-compiler on Sun Solaris available then it was at least possible to build code for other CPUs than SPARC. - I've used in the past SPARCstations in Univerity, but mostly via SunOS/Solaris and then for doing some XView programming projects etc. then. But since I had that days at home a NeXTcube and no SPARCstation, I rewrote and adapted Sun's XView system, the "olwm" and "olvwm" and the XView libraries, over to NeXTstep under Cub'X Windows (that took nearly 6 months or so AFAI recall). - Later I gifted that to the NeXT community and the Cub'X Buddies added that stuff into Cub'X Windows too.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.