Does it make sense to upgrade to a 64-bit version for a "typical" Mac OS X application?

I understand the main advantages of creating a 64-bit application on Mac OS X: more available memory, better performance, etc.

But what if I have an application with modest memory needs and no performance issues. Suppose porting it to 64-bit is just a matter of changing build settings. Will accessing a 64-bit executable provide real benefits to my users on Leopard or Snow Leopard?

I know that the reaction of many programmers on the knee is “Of course you must support 64-bit!”, And some experienced users will mock and complain if they see that your application is not 64-bit, but I’m interested in the real benefits / costs .

Some related issues:

  • I could provide a combined universal 32-bit and 64-bit application, but will the benefits (if any) justify the larger download size?
  • I could provide separate 32-bit and 64-bit downloads, but would that just confuse users?
+3
source share
8 answers

, 64- . , , , , , 64 , . , . , . - : , . 64- , .

OTOH, SQLServer/Oracle, , , : -)

+3
  • 64- ( - 64- . , " ", ...)

  • , 32- 64- . , . , , , .

    - 56k ( ). 32- " [Mac]" "" 32/64 ( , Mac ).

+4

32- 64- . - 10.6.

64- :

  • x86_64
  • Objective-C
  • 32- Snow Leopard

, Snow Leopard 64-, Apple 64- . , . , , 32- ( !). , 64- .

Objective-C 32- ABI. 64- ABI, . , Cocoa.

A 32/64 Universal Binary - . . , .

, . 10.6 , ​​ 32- . 64- .

64- ​​ 64- . Snow Leopard 64-, 64-, .

Apple ( , ):

+2

. , 64- , .

+1

Mac OS X 10.6 - 64- , 32- , 32- .

, 64- , , 32- .

+1

, - .

64- , . 32-, .

, , , 64- , , , . -, , , . , .

0

: . 64- 64- 32- , 32- .

0

64- , , . 64- , , 4 , , , 64- (4 4 , , , OS-X. Linux 1 ).

, ( ) , , 64 - SIMD , .

- C , 64- , 64 . , , , .

: , , , . , 64 , OS-X 32- , .

: " " , 64- 32- 64 > 32, , , , - . , , 64-, .

-2

Source: https://habr.com/ru/post/1716778/


All Articles