Coding for fruit
-
I couldn't possibly be more ignorant of Apple technologies. Recently, a friend came over with her new Mac laptop, and I couldn't even find the bloody "backspace delete" key. Let alone the right mouse button. I say this as a preface to forestall any excessive laughing at what might be inane assumptions on my part since I've done zero research. I keep seeing the most unlikely people showing up with Macs. Hardcore, longstanding Windows developers and business people who have lived for decades in a Microsoft dominated office. And yet, with the runaway hit of the iPod and then the massively hyped iPhone, people are also starting to realize something. "Say, don't these Apple guys also make computers?" Macs are flying off the shelves these days, and not just to the fluffy bunny, tree hugging crowd (sorry, Paul :)). I spent decades coding for MS environments for the same reason that bank robbers rob banks - because that's where the money is. For every 1 Apple development job advertised (and I'm not talking web browser stuff), there were 1,000,000 MS jobs. Now, with this Apple renaissance and all the neat new gadgets, part of me is thinking, "Hey, a market that hasn't been flooded with developers. Maybe I should write a..." However, while I'm sure there's a standard Mac API equivalent to the Windows API for developers, Apple's attitude towards developers makes me nervous. iPods, iPhones, i.e. the stuff that put them back on the map, are locked down gadgets where only the black hats dare venture since Apple will likely release a new version that turns your modified iPhone into an iBrick. In short, Apple has always been about proprietary hardware (among the many reasons that they had their head handed to them by Microsoft in the business market). Microsoft encouraged the masses to come and code for their platform. All these Apple gizmos look cool and of course Jobs hypes them as bleeding edge, but I just don't see the porch light on beckoning me to code something cool and profitable for their hardware, no matter how tempting it might be. It seems like the only developers that Apple is really interested in are Apple employees. So, let's hear from the fluffy bunny crowd. If you're banned from a web browser, how profitable (or even possible) is it to write cool new apps for Apple's cool new gizmos?
Christopher Duncan Author of The Career Programmer and
-
I couldn't possibly be more ignorant of Apple technologies. Recently, a friend came over with her new Mac laptop, and I couldn't even find the bloody "backspace delete" key. Let alone the right mouse button. I say this as a preface to forestall any excessive laughing at what might be inane assumptions on my part since I've done zero research. I keep seeing the most unlikely people showing up with Macs. Hardcore, longstanding Windows developers and business people who have lived for decades in a Microsoft dominated office. And yet, with the runaway hit of the iPod and then the massively hyped iPhone, people are also starting to realize something. "Say, don't these Apple guys also make computers?" Macs are flying off the shelves these days, and not just to the fluffy bunny, tree hugging crowd (sorry, Paul :)). I spent decades coding for MS environments for the same reason that bank robbers rob banks - because that's where the money is. For every 1 Apple development job advertised (and I'm not talking web browser stuff), there were 1,000,000 MS jobs. Now, with this Apple renaissance and all the neat new gadgets, part of me is thinking, "Hey, a market that hasn't been flooded with developers. Maybe I should write a..." However, while I'm sure there's a standard Mac API equivalent to the Windows API for developers, Apple's attitude towards developers makes me nervous. iPods, iPhones, i.e. the stuff that put them back on the map, are locked down gadgets where only the black hats dare venture since Apple will likely release a new version that turns your modified iPhone into an iBrick. In short, Apple has always been about proprietary hardware (among the many reasons that they had their head handed to them by Microsoft in the business market). Microsoft encouraged the masses to come and code for their platform. All these Apple gizmos look cool and of course Jobs hypes them as bleeding edge, but I just don't see the porch light on beckoning me to code something cool and profitable for their hardware, no matter how tempting it might be. It seems like the only developers that Apple is really interested in are Apple employees. So, let's hear from the fluffy bunny crowd. If you're banned from a web browser, how profitable (or even possible) is it to write cool new apps for Apple's cool new gizmos?
Christopher Duncan Author of The Career Programmer and
Since Mac OS X is based on UNIX, most software packages written for BSD or Linux can be recompiled to run on it.
-
Since Mac OS X is based on UNIX, most software packages written for BSD or Linux can be recompiled to run on it.
jchigg2000 wrote:
Since Mac OS X is based on UNIX
Wrong mooselips - it's based on BSD.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
I couldn't possibly be more ignorant of Apple technologies. Recently, a friend came over with her new Mac laptop, and I couldn't even find the bloody "backspace delete" key. Let alone the right mouse button. I say this as a preface to forestall any excessive laughing at what might be inane assumptions on my part since I've done zero research. I keep seeing the most unlikely people showing up with Macs. Hardcore, longstanding Windows developers and business people who have lived for decades in a Microsoft dominated office. And yet, with the runaway hit of the iPod and then the massively hyped iPhone, people are also starting to realize something. "Say, don't these Apple guys also make computers?" Macs are flying off the shelves these days, and not just to the fluffy bunny, tree hugging crowd (sorry, Paul :)). I spent decades coding for MS environments for the same reason that bank robbers rob banks - because that's where the money is. For every 1 Apple development job advertised (and I'm not talking web browser stuff), there were 1,000,000 MS jobs. Now, with this Apple renaissance and all the neat new gadgets, part of me is thinking, "Hey, a market that hasn't been flooded with developers. Maybe I should write a..." However, while I'm sure there's a standard Mac API equivalent to the Windows API for developers, Apple's attitude towards developers makes me nervous. iPods, iPhones, i.e. the stuff that put them back on the map, are locked down gadgets where only the black hats dare venture since Apple will likely release a new version that turns your modified iPhone into an iBrick. In short, Apple has always been about proprietary hardware (among the many reasons that they had their head handed to them by Microsoft in the business market). Microsoft encouraged the masses to come and code for their platform. All these Apple gizmos look cool and of course Jobs hypes them as bleeding edge, but I just don't see the porch light on beckoning me to code something cool and profitable for their hardware, no matter how tempting it might be. It seems like the only developers that Apple is really interested in are Apple employees. So, let's hear from the fluffy bunny crowd. If you're banned from a web browser, how profitable (or even possible) is it to write cool new apps for Apple's cool new gizmos?
Christopher Duncan Author of The Career Programmer and
Christopher Duncan wrote:
the stuff that put them back on the map, are locked down gadgets where only the black hats dare venture since Apple will likely release a new version that turns your modified iPhone into an iBrick
The iPhone SDK has been out since march, and commercial apps are to be released mid-june. Although they were a bit late with this (almost a year), they seem to be listening to their customers. :)
He who makes a beast out of himself gets rid of the pain of being a man
-
I couldn't possibly be more ignorant of Apple technologies. Recently, a friend came over with her new Mac laptop, and I couldn't even find the bloody "backspace delete" key. Let alone the right mouse button. I say this as a preface to forestall any excessive laughing at what might be inane assumptions on my part since I've done zero research. I keep seeing the most unlikely people showing up with Macs. Hardcore, longstanding Windows developers and business people who have lived for decades in a Microsoft dominated office. And yet, with the runaway hit of the iPod and then the massively hyped iPhone, people are also starting to realize something. "Say, don't these Apple guys also make computers?" Macs are flying off the shelves these days, and not just to the fluffy bunny, tree hugging crowd (sorry, Paul :)). I spent decades coding for MS environments for the same reason that bank robbers rob banks - because that's where the money is. For every 1 Apple development job advertised (and I'm not talking web browser stuff), there were 1,000,000 MS jobs. Now, with this Apple renaissance and all the neat new gadgets, part of me is thinking, "Hey, a market that hasn't been flooded with developers. Maybe I should write a..." However, while I'm sure there's a standard Mac API equivalent to the Windows API for developers, Apple's attitude towards developers makes me nervous. iPods, iPhones, i.e. the stuff that put them back on the map, are locked down gadgets where only the black hats dare venture since Apple will likely release a new version that turns your modified iPhone into an iBrick. In short, Apple has always been about proprietary hardware (among the many reasons that they had their head handed to them by Microsoft in the business market). Microsoft encouraged the masses to come and code for their platform. All these Apple gizmos look cool and of course Jobs hypes them as bleeding edge, but I just don't see the porch light on beckoning me to code something cool and profitable for their hardware, no matter how tempting it might be. It seems like the only developers that Apple is really interested in are Apple employees. So, let's hear from the fluffy bunny crowd. If you're banned from a web browser, how profitable (or even possible) is it to write cool new apps for Apple's cool new gizmos?
Christopher Duncan Author of The Career Programmer and
Personally speaking I'm getting a Mac not to do any development (though I am looking forward to again having vi) but because 1. Macs look good. I'm stunned that PC manufactures are sticking with ugly boxes. 2. Macs run Windows. To me a Mac is just another PC. 3. Macs accept USB devices. I'll use whatever keyboard/mouse I want. My Mac will look like a Mac and smell like a Mac but it's going to be running Visual Studio.
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
jchigg2000 wrote:
Since Mac OS X is based on UNIX
Wrong mooselips - it's based on BSD.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001what the?! "Berkeley Software Distribution (BSD, sometimes called Berkeley Unix) is the Unix operating system derivative developed and distributed by the Computer Systems Research Group of the University of California, Berkeley, from 1977 to 1995." http://en.wikipedia.org/wiki/BSD[^]
-
I couldn't possibly be more ignorant of Apple technologies. Recently, a friend came over with her new Mac laptop, and I couldn't even find the bloody "backspace delete" key. Let alone the right mouse button. I say this as a preface to forestall any excessive laughing at what might be inane assumptions on my part since I've done zero research. I keep seeing the most unlikely people showing up with Macs. Hardcore, longstanding Windows developers and business people who have lived for decades in a Microsoft dominated office. And yet, with the runaway hit of the iPod and then the massively hyped iPhone, people are also starting to realize something. "Say, don't these Apple guys also make computers?" Macs are flying off the shelves these days, and not just to the fluffy bunny, tree hugging crowd (sorry, Paul :)). I spent decades coding for MS environments for the same reason that bank robbers rob banks - because that's where the money is. For every 1 Apple development job advertised (and I'm not talking web browser stuff), there were 1,000,000 MS jobs. Now, with this Apple renaissance and all the neat new gadgets, part of me is thinking, "Hey, a market that hasn't been flooded with developers. Maybe I should write a..." However, while I'm sure there's a standard Mac API equivalent to the Windows API for developers, Apple's attitude towards developers makes me nervous. iPods, iPhones, i.e. the stuff that put them back on the map, are locked down gadgets where only the black hats dare venture since Apple will likely release a new version that turns your modified iPhone into an iBrick. In short, Apple has always been about proprietary hardware (among the many reasons that they had their head handed to them by Microsoft in the business market). Microsoft encouraged the masses to come and code for their platform. All these Apple gizmos look cool and of course Jobs hypes them as bleeding edge, but I just don't see the porch light on beckoning me to code something cool and profitable for their hardware, no matter how tempting it might be. It seems like the only developers that Apple is really interested in are Apple employees. So, let's hear from the fluffy bunny crowd. If you're banned from a web browser, how profitable (or even possible) is it to write cool new apps for Apple's cool new gizmos?
Christopher Duncan Author of The Career Programmer and
Christopher Duncan wrote:
However, while I'm sure there's a standard Mac API equivalent to the Windows API for developers, Apple's attitude towards developers makes me nervous.
The difference is that Microsoft is a software company, and Apple is a hardware company.
-
Personally speaking I'm getting a Mac not to do any development (though I am looking forward to again having vi) but because 1. Macs look good. I'm stunned that PC manufactures are sticking with ugly boxes. 2. Macs run Windows. To me a Mac is just another PC. 3. Macs accept USB devices. I'll use whatever keyboard/mouse I want. My Mac will look like a Mac and smell like a Mac but it's going to be running Visual Studio.
cheers, Chris Maunder
CodeProject.com : C++ MVP
Chris Maunder wrote:
though I am looking forward to again having vi
[reaches for stethascope] I'm terribly sorry Mr. Maunder, but this seems to be signs of a deeper illness. Let me get you the number to a treatment center...
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
jchigg2000 wrote:
Since Mac OS X is based on UNIX
Wrong mooselips - it's based on BSD.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001Mooselips, indeed. How terribly embarrassing for you. What do you think, guys - should John change his sig to "Hey, Rocky..." :-D
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
I couldn't possibly be more ignorant of Apple technologies. Recently, a friend came over with her new Mac laptop, and I couldn't even find the bloody "backspace delete" key. Let alone the right mouse button. I say this as a preface to forestall any excessive laughing at what might be inane assumptions on my part since I've done zero research. I keep seeing the most unlikely people showing up with Macs. Hardcore, longstanding Windows developers and business people who have lived for decades in a Microsoft dominated office. And yet, with the runaway hit of the iPod and then the massively hyped iPhone, people are also starting to realize something. "Say, don't these Apple guys also make computers?" Macs are flying off the shelves these days, and not just to the fluffy bunny, tree hugging crowd (sorry, Paul :)). I spent decades coding for MS environments for the same reason that bank robbers rob banks - because that's where the money is. For every 1 Apple development job advertised (and I'm not talking web browser stuff), there were 1,000,000 MS jobs. Now, with this Apple renaissance and all the neat new gadgets, part of me is thinking, "Hey, a market that hasn't been flooded with developers. Maybe I should write a..." However, while I'm sure there's a standard Mac API equivalent to the Windows API for developers, Apple's attitude towards developers makes me nervous. iPods, iPhones, i.e. the stuff that put them back on the map, are locked down gadgets where only the black hats dare venture since Apple will likely release a new version that turns your modified iPhone into an iBrick. In short, Apple has always been about proprietary hardware (among the many reasons that they had their head handed to them by Microsoft in the business market). Microsoft encouraged the masses to come and code for their platform. All these Apple gizmos look cool and of course Jobs hypes them as bleeding edge, but I just don't see the porch light on beckoning me to code something cool and profitable for their hardware, no matter how tempting it might be. It seems like the only developers that Apple is really interested in are Apple employees. So, let's hear from the fluffy bunny crowd. If you're banned from a web browser, how profitable (or even possible) is it to write cool new apps for Apple's cool new gizmos?
Christopher Duncan Author of The Career Programmer and
Christopher Duncan wrote:
If you're banned from a web browser, how profitable (or even possible) is it to write cool new apps for Apple's cool new gizmos?
This just showed up in my RSS reader. First Venture Capital Funded iPhone Apps: Whrrl, iControl[^]
-
I couldn't possibly be more ignorant of Apple technologies. Recently, a friend came over with her new Mac laptop, and I couldn't even find the bloody "backspace delete" key. Let alone the right mouse button. I say this as a preface to forestall any excessive laughing at what might be inane assumptions on my part since I've done zero research. I keep seeing the most unlikely people showing up with Macs. Hardcore, longstanding Windows developers and business people who have lived for decades in a Microsoft dominated office. And yet, with the runaway hit of the iPod and then the massively hyped iPhone, people are also starting to realize something. "Say, don't these Apple guys also make computers?" Macs are flying off the shelves these days, and not just to the fluffy bunny, tree hugging crowd (sorry, Paul :)). I spent decades coding for MS environments for the same reason that bank robbers rob banks - because that's where the money is. For every 1 Apple development job advertised (and I'm not talking web browser stuff), there were 1,000,000 MS jobs. Now, with this Apple renaissance and all the neat new gadgets, part of me is thinking, "Hey, a market that hasn't been flooded with developers. Maybe I should write a..." However, while I'm sure there's a standard Mac API equivalent to the Windows API for developers, Apple's attitude towards developers makes me nervous. iPods, iPhones, i.e. the stuff that put them back on the map, are locked down gadgets where only the black hats dare venture since Apple will likely release a new version that turns your modified iPhone into an iBrick. In short, Apple has always been about proprietary hardware (among the many reasons that they had their head handed to them by Microsoft in the business market). Microsoft encouraged the masses to come and code for their platform. All these Apple gizmos look cool and of course Jobs hypes them as bleeding edge, but I just don't see the porch light on beckoning me to code something cool and profitable for their hardware, no matter how tempting it might be. It seems like the only developers that Apple is really interested in are Apple employees. So, let's hear from the fluffy bunny crowd. If you're banned from a web browser, how profitable (or even possible) is it to write cool new apps for Apple's cool new gizmos?
Christopher Duncan Author of The Career Programmer and
Macs are so last year - get an OLPC, dig out the innards and put a decent intel based machine in it. ;)
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
-
Macs are so last year - get an OLPC, dig out the innards and put a decent intel based machine in it. ;)
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
Intel, Intel... Sounds familiar. Didn't they used to make computer stuff back in the 80s? :)
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
Personally speaking I'm getting a Mac not to do any development (though I am looking forward to again having vi) but because 1. Macs look good. I'm stunned that PC manufactures are sticking with ugly boxes. 2. Macs run Windows. To me a Mac is just another PC. 3. Macs accept USB devices. I'll use whatever keyboard/mouse I want. My Mac will look like a Mac and smell like a Mac but it's going to be running Visual Studio.
cheers, Chris Maunder
CodeProject.com : C++ MVP
Chris Maunder wrote:
1. Macs look good. I'm stunned that PC manufactures are sticking with ugly boxes.
That reminds me of a couple of female students that were sitting behind me on a train one day - one girl said that she was going to buy a new computer but couldn't decide which one - the Windows PC had a better software bundle, but the iMac matched the decor of her bedroom!
==================================== Transvestites - Roberts in Disguise! ====================================
-
I couldn't possibly be more ignorant of Apple technologies. Recently, a friend came over with her new Mac laptop, and I couldn't even find the bloody "backspace delete" key. Let alone the right mouse button. I say this as a preface to forestall any excessive laughing at what might be inane assumptions on my part since I've done zero research. I keep seeing the most unlikely people showing up with Macs. Hardcore, longstanding Windows developers and business people who have lived for decades in a Microsoft dominated office. And yet, with the runaway hit of the iPod and then the massively hyped iPhone, people are also starting to realize something. "Say, don't these Apple guys also make computers?" Macs are flying off the shelves these days, and not just to the fluffy bunny, tree hugging crowd (sorry, Paul :)). I spent decades coding for MS environments for the same reason that bank robbers rob banks - because that's where the money is. For every 1 Apple development job advertised (and I'm not talking web browser stuff), there were 1,000,000 MS jobs. Now, with this Apple renaissance and all the neat new gadgets, part of me is thinking, "Hey, a market that hasn't been flooded with developers. Maybe I should write a..." However, while I'm sure there's a standard Mac API equivalent to the Windows API for developers, Apple's attitude towards developers makes me nervous. iPods, iPhones, i.e. the stuff that put them back on the map, are locked down gadgets where only the black hats dare venture since Apple will likely release a new version that turns your modified iPhone into an iBrick. In short, Apple has always been about proprietary hardware (among the many reasons that they had their head handed to them by Microsoft in the business market). Microsoft encouraged the masses to come and code for their platform. All these Apple gizmos look cool and of course Jobs hypes them as bleeding edge, but I just don't see the porch light on beckoning me to code something cool and profitable for their hardware, no matter how tempting it might be. It seems like the only developers that Apple is really interested in are Apple employees. So, let's hear from the fluffy bunny crowd. If you're banned from a web browser, how profitable (or even possible) is it to write cool new apps for Apple's cool new gizmos?
Christopher Duncan Author of The Career Programmer and
I don't know about how profitable it is, but I have found their attitude towards devs to be one of indifference. I have been on the carbon and xCode mailing list for about 5 years now, and I have not been that impressed. It can be frustrating to find things out, the tools have been really slow to come to any fruition (the current xCode is much better than before, but it's still got some big issues). Documentation, particularly for Carbon was/is a real PITA to find. A interesting thing has developed with the release of the iPhone SDK and the updated version of xCode (it moved from 3.0 to 3.1). Apple releases it to people for development. But, you have to "sign" a click through NDA to get it. Then they point people at mailing lists, but when newbies rightfully ask questions they are told they won't get answers because the product in question is NDA'd. OK that's fair enough, except there's *no where* else to go! All you can do is send an email as feedback! There's no closed list for NDA devs to ask question or discuss at all. This strikes me as absurd, but it seems generally in keeping with some of the other things I've seen on the platform.
Christopher Duncan wrote:
It seems like the only developers that Apple is really interested in are Apple employees.
That is exactly what I have thought for some time as well. I don't know how fair that is, but from what I've seen ,and heard we're definitely not alone in these sentiments. All this said, I do want to mention that Cocoa is a *really* cool API to use and Objective C is extremely cool. I think it's a crying shame that it's not usable as a general purpose framework on other platforms (and yes I'm aware of GNUStep, but that's not really an option unless you're prepared to accept developing with GCC and a broken Win32 port).
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
-
I don't know about how profitable it is, but I have found their attitude towards devs to be one of indifference. I have been on the carbon and xCode mailing list for about 5 years now, and I have not been that impressed. It can be frustrating to find things out, the tools have been really slow to come to any fruition (the current xCode is much better than before, but it's still got some big issues). Documentation, particularly for Carbon was/is a real PITA to find. A interesting thing has developed with the release of the iPhone SDK and the updated version of xCode (it moved from 3.0 to 3.1). Apple releases it to people for development. But, you have to "sign" a click through NDA to get it. Then they point people at mailing lists, but when newbies rightfully ask questions they are told they won't get answers because the product in question is NDA'd. OK that's fair enough, except there's *no where* else to go! All you can do is send an email as feedback! There's no closed list for NDA devs to ask question or discuss at all. This strikes me as absurd, but it seems generally in keeping with some of the other things I've seen on the platform.
Christopher Duncan wrote:
It seems like the only developers that Apple is really interested in are Apple employees.
That is exactly what I have thought for some time as well. I don't know how fair that is, but from what I've seen ,and heard we're definitely not alone in these sentiments. All this said, I do want to mention that Cocoa is a *really* cool API to use and Objective C is extremely cool. I think it's a crying shame that it's not usable as a general purpose framework on other platforms (and yes I'm aware of GNUStep, but that's not really an option unless you're prepared to accept developing with GCC and a broken Win32 port).
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
It's nice to hear from someone who's been to the front. This reinforces my gut feeling that unlike MS, Apple isn't really interested in building an army of supporting developers for their products. We can joke about Ballmer and "Developers, developers, developers," but it's support from guys like us that made the mammoth success of Microsoft possible, and they were smart enough to court us.
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
I couldn't possibly be more ignorant of Apple technologies. Recently, a friend came over with her new Mac laptop, and I couldn't even find the bloody "backspace delete" key. Let alone the right mouse button. I say this as a preface to forestall any excessive laughing at what might be inane assumptions on my part since I've done zero research. I keep seeing the most unlikely people showing up with Macs. Hardcore, longstanding Windows developers and business people who have lived for decades in a Microsoft dominated office. And yet, with the runaway hit of the iPod and then the massively hyped iPhone, people are also starting to realize something. "Say, don't these Apple guys also make computers?" Macs are flying off the shelves these days, and not just to the fluffy bunny, tree hugging crowd (sorry, Paul :)). I spent decades coding for MS environments for the same reason that bank robbers rob banks - because that's where the money is. For every 1 Apple development job advertised (and I'm not talking web browser stuff), there were 1,000,000 MS jobs. Now, with this Apple renaissance and all the neat new gadgets, part of me is thinking, "Hey, a market that hasn't been flooded with developers. Maybe I should write a..." However, while I'm sure there's a standard Mac API equivalent to the Windows API for developers, Apple's attitude towards developers makes me nervous. iPods, iPhones, i.e. the stuff that put them back on the map, are locked down gadgets where only the black hats dare venture since Apple will likely release a new version that turns your modified iPhone into an iBrick. In short, Apple has always been about proprietary hardware (among the many reasons that they had their head handed to them by Microsoft in the business market). Microsoft encouraged the masses to come and code for their platform. All these Apple gizmos look cool and of course Jobs hypes them as bleeding edge, but I just don't see the porch light on beckoning me to code something cool and profitable for their hardware, no matter how tempting it might be. It seems like the only developers that Apple is really interested in are Apple employees. So, let's hear from the fluffy bunny crowd. If you're banned from a web browser, how profitable (or even possible) is it to write cool new apps for Apple's cool new gizmos?
Christopher Duncan Author of The Career Programmer and
-
Intel, Intel... Sounds familiar. Didn't they used to make computer stuff back in the 80s? :)
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
Christopher Duncan wrote:
Didn't they used to make computer stuff back in the 80s?
Yes - before "electronics as jewelry" :-)
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
-
Since Mac OS X is based on UNIX, most software packages written for BSD or Linux can be recompiled to run on it.
If I'm not mistaken, mac os x is actually based on the mach kernel - a micro kernel. They implement a unix subsystem - a mix between net/freebsd if I'm not mistaken. It's much like the posix or win32 subsystem in windows.
-- Kein Mitleid Für Die Mehrheit
-
Christopher Duncan wrote:
Didn't they used to make computer stuff back in the 80s?
Yes - before "electronics as jewelry" :-)
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
Saaaay... are you making fun of my iNoseRing?
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
I don't know about how profitable it is, but I have found their attitude towards devs to be one of indifference. I have been on the carbon and xCode mailing list for about 5 years now, and I have not been that impressed. It can be frustrating to find things out, the tools have been really slow to come to any fruition (the current xCode is much better than before, but it's still got some big issues). Documentation, particularly for Carbon was/is a real PITA to find. A interesting thing has developed with the release of the iPhone SDK and the updated version of xCode (it moved from 3.0 to 3.1). Apple releases it to people for development. But, you have to "sign" a click through NDA to get it. Then they point people at mailing lists, but when newbies rightfully ask questions they are told they won't get answers because the product in question is NDA'd. OK that's fair enough, except there's *no where* else to go! All you can do is send an email as feedback! There's no closed list for NDA devs to ask question or discuss at all. This strikes me as absurd, but it seems generally in keeping with some of the other things I've seen on the platform.
Christopher Duncan wrote:
It seems like the only developers that Apple is really interested in are Apple employees.
That is exactly what I have thought for some time as well. I don't know how fair that is, but from what I've seen ,and heard we're definitely not alone in these sentiments. All this said, I do want to mention that Cocoa is a *really* cool API to use and Objective C is extremely cool. I think it's a crying shame that it's not usable as a general purpose framework on other platforms (and yes I'm aware of GNUStep, but that's not really an option unless you're prepared to accept developing with GCC and a broken Win32 port).
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
Jim Crafton wrote:
and yes I'm aware of GNUStep, but that's not really an option unless you're prepared to accept developing with GCC
The xcode tools are built on the GCC toolchain, are they not? I remember reading that Apple is the main open source developers on the Obj-C part of GCC.
-- Kein Mitleid Für Die Mehrheit