Leaving Apple for FreeBSD

canihazsekooriti said:
… You cannot rely on something you cannot audit for basic security. Period. It's UNSAFE for any end-user, to put it mildly, in pretty real terms. …
Click to expand...

canihazsekooriti said:
Working on it!

Ok, maybe not full but examine network-related things. I'm just starting with FreeBSD (this is not a threat). …
Click to expand...

?

Good luck, and thanks.

I removed a couple of FreeBSD security-related posts. (Months passed, zero public or private interest.)
 

Attachments

  • 2024-03-30 security issue mentioned.png
    2024-03-30 security issue mentioned.png
    49.2 KB · Views: 213
  • 2024-04-13 another security issue mentioned.png
    2024-04-13 another security issue mentioned.png
    26.3 KB · Views: 229
In four days my app store membership will run out. I have apps there since 2009 and learned a lot about lean design in the early app store years. About 5 years ago, I gave swift a try, rather late to the party. My 800k objective-c app bundle of https://mro.name/shaarlios became a 15MB test deployment bundle and a 50MB production bundle to submit to Apple. I have no idea why they differ so wildly. They contain the same code and the same assets for the same devices. If it can run after a direct download, it surely should be good enough to be fed into the app store pipeline.

But what really crushed my expectations that the most valuable company could produce sustainable solutions, was, that uploading those 50MB with the dedicated Apple upload tool for this single purpose caused over 300MB of network traffic on my 12MBit uplink I use to this day.

Hours for one upload (in case of success) for what used to be about a minute if I remember right. For the same payload function-wise. Not my kind of sustainability.
 
You must log in or register to reply here.
Back
Top