Ulai, you present some interesting thoughts for focused mathematics and scientific computing, but I don't have much (and by "much" I mean "any") experience programming in those areas so I really can't comment on it.
My opinion is that for general-purpose desktop application programming, operator overloading causes more problem then it solves by developers inventing their own metalanguages that someone else has to learn later.
At the end of the day, Objective-C's main priority seems to be general-purpose programming. That said, you can mix Objective-C and C++ if it suits your needs.
I happen to use C# daily at work and overloading has not caused me any confusion at all
Which makes sense since if it did, I doubt you'd be requesting it. :) Of course, the challenge is that Objective-C has a lot of users to take into consideration. Something that you consider a weakness I consider a strength, but that's the whole point of having multiple languages to choose from.
None of this stops you from writing a Mac app, of course. The UI logic and internal calculation logic can be written in different languages.
by Scott Stevenson — Sep 16
My opinion is that for general-purpose desktop application programming, operator overloading causes more problem then it solves by developers inventing their own metalanguages that someone else has to learn later.
At the end of the day, Objective-C's main priority seems to be general-purpose programming. That said, you can mix Objective-C and C++ if it suits your needs.
I happen to use C# daily at work and overloading has not caused me any confusion at all
Which makes sense since if it did, I doubt you'd be requesting it. :) Of course, the challenge is that Objective-C has a lot of users to take into consideration. Something that you consider a weakness I consider a strength, but that's the whole point of having multiple languages to choose from.
None of this stops you from writing a Mac app, of course. The UI logic and internal calculation logic can be written in different languages.