vortitribal.blogg.se

Cocoa frameworks in appcode
Cocoa frameworks in appcode









cocoa frameworks in appcode
  1. #Cocoa frameworks in appcode how to
  2. #Cocoa frameworks in appcode 64 Bit
  3. #Cocoa frameworks in appcode code

Remember that? This layer existed even in Classic, yet another compatibility layer that allowed OS 9 applications to run on OS X… but I digress.

cocoa frameworks in appcode

The earliest example is the “Mac 68k Emulator Layer,” bundled with Power Macs back in the 90’s, so that old Mac applications compiled for the Motorola 68000 CPUs could run. The history of Apple is quite interesting in this respect. Transitional TechnologiesĪnother thing that has not changed is that Apple always provided us with what I call “Transitional Technologies.” That is, emulators, compatibility layers and binary formats that have allowed us to move our applications from one architecture or language to the next, and often to run it without changes in the new platform. So, in a sense, we can say that “plus ça change, plus c’est la même chose.” Clearly, Jean-Baptiste and Heraclitus never agreed on the subject of change. Of course, every time the marketing department said the same thing about those languages that they are the best, the fastest, the blah blah blah. This leads me to another clear evolutionary path, if you look at this slide closely: we have gone from a procedural world, the one of BASIC and Pascal, to an object-oriented one, with C++ and Objective-C, and Swift is opening the way for a more functional way of doing things.

#Cocoa frameworks in appcode 64 Bit

Look at their CPUs Apple has gone from a humble MOS 6502 to Gigaherz-fast ARM chips, eating very little power and providing enough calculation power to put a man on the moon, or, you know, to publish a selfie in Instagram.Īt the same time, we have evolved from 8 bit to 64 bit architectures, forcing us to rewrite lots of low-level pointer-arithmetic code, because you know, that’s where the fun is.Īnd finally, the most important part of the evolution for us, software developers, is the constant change of “official” programming languages from Wozniak’s Integer BASIC in 77 to Swift, Apple has constantly required us to migrate our skills to newer, safer, and buggier programming languages. Soon, watches are going to appear in the horizon to complete this lineup, too. We’ve gone from very humble machines to state-of-the-art computers, some of them handheld and operating a social and technological revolution. In the meantime I will buy as much Apple stock as I can. And to begin my talk I will go quickly back in time to 1976, to 1984, to 1995, to the two thousands, and back to now.

#Cocoa frameworks in appcode how to

IntroductionĪ wise man called Heraclitus said 2500 years ago that “Change is the only constant.” He said it in greek, obviously, so actually he said these words: “πάντα χωρεῖ καὶ οὐδὲν μένει.” But I just do not know how to pronounce this, so I’ll leave it there.

#Cocoa frameworks in appcode code

Some code examples will help him defend a point that nobody outside of Cupertino can sustain for sure. In this talk, Adrian will provide lots of speculation and highly arguable unverified gossip, about how the design of Swift will lead Apple to redesign Cocoa into new directions, and maybe replacing it altogether.











Cocoa frameworks in appcode