Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Converting nibs (Re: [ANN] Nano 1.4)


On Jun 20, 2007, at 11:30 PM, Dale Jensen wrote:

On Jun 20, 2007, at 12:54 PM, Ken Worley wrote:

It sucks, but language obsolescence is just one of those facts of life of this industry.

C/C++ is not becoming obsolete by any stretch of the imagination...at least nowhere but for Carbon developers being forced down another road.

Sorry, I was referring to Carbon in general and C++ as it relates to that, and for the Mac only, obviously.

8><   8><

Throw in the growing use of languages that are on the periphery of things, like Python, Ruby and web based systems, and I'm not sure that one would call this the Golden Age of C/C++.

Realize that I'm not relating whether I think that's good or not, I'm just observing what I've seen.

Back in 2000, I'd agree with you. But starting when compilers finally got fairly standard compliant (e.g. VC++2003) that started a new wave of library use. I tried to use std::bind1st ten years ago but due to compiler limitations it never worked. Today I use boost::bind and my style has changed dramatically: writing short functions for use with STL loops that finally delivered on their promise. Using boost::bind also provides a foundation for simple multithreading: you can take any function call, bind it down to a function of zero parameters and put it on a worklist.

My feeling is that support for concurrent apps will determine future language success. Today that's sort of a manual operation but if some bright team finds a way to automate that for some language, it'll attract lots of developers. On a dual core machine, users don't care much whether the software is single or multithreaded. On a quad core I think they'll start noticing.

The main Microsoft strategy is to put out new API's at a rate that  no one will be able to follow. My feeling is that since MS lost all control of where C++ is heading, they've sort of moved on. Vista support for OpenGL is another example: CAD vendors had to rewrite their code for Direct3D to maintain performance. With Apple's threading support for OpenGL I was really excited about writing for the Mac until this 64-bit/carbon issue surfaced.

Henrik
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden

This email sent to email@hidden
References: 
 >Re: [ANN] Nano 1.4 (From: "Jan Barnholt" <email@hidden>)
 >Re: [ANN] Nano 1.4 (From: Laurence Harris <email@hidden>)
 >Re: [ANN] Nano 1.4 (From: Bryan Prusha <email@hidden>)
 >Re: Converting nibs (Re: [ANN] Nano 1.4) (From: Laurence Harris <email@hidden>)
 >Re: Converting nibs (Re: [ANN] Nano 1.4) (From: Dale Jensen <email@hidden>)
 >Re: Converting nibs (Re: [ANN] Nano 1.4) (From: Ken Worley <email@hidden>)
 >Re: Converting nibs (Re: [ANN] Nano 1.4) (From: Dale Jensen <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.