Linked by Thom Holwerda on Fri 3rd Feb 2012 23:43 UTC
Thread beginning with comment 505846
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: You're wrong. It's bad iOS developers.
by warhawk on Sat 4th Feb 2012 00:12
in reply to "RE: You're wrong. It's bad iOS developers."
You know, it's funny... if somebody makes a comment about how many desktop Java apps run like ass, people are quick to blame programmers as well. Surely, it CAN'T be the languages that suck
Have you considered upgrading your Pentium with 1 GB of RAM? As for languages that suck, well, they really don't get much worse than Objective C.
Edited 2012-02-04 00:20 UTC
RE[3]: You're wrong. It's bad iOS developers.
by Bill Shooter of Bul on Sat 4th Feb 2012 01:16
in reply to "RE[2]: You're wrong. It's bad iOS developers."
RE[3]: You're wrong. It's bad iOS developers.
by krreagan on Sat 4th Feb 2012 06:28
in reply to "RE[2]: You're wrong. It's bad iOS developers."
RE[3]: You're wrong. It's bad iOS developers.
by darknexus on Sat 4th Feb 2012 10:57
in reply to "RE[2]: You're wrong. It's bad iOS developers."
As for languages that suck, well, they really don't get much worse than Objective C.
Couldn't agree more. A bastardized mix of C and SmallTalk, and neither bit bares even the slightest syntactic resemblance to the other. Even C++ is cleaner, and that's saying something. Why anyone thought the design of obj-c was a good thing I couldn't guess, and why Next (and as a consequence Apple) went with it is one of those mysteries we'll probably be wondering about forever.
RE[2]: You're wrong. It's bad iOS developers.
by JAlexoid on Sat 4th Feb 2012 00:40
in reply to "RE: You're wrong. It's bad iOS developers."
RE[3]: You're wrong. It's bad iOS developers.
by warhawk on Sat 4th Feb 2012 00:58
in reply to "RE[2]: You're wrong. It's bad iOS developers."
Are you implying that Java sucks?
That said, Java's Swing tool-kit was always a slow ram hog when used without proper knowledge.
That said, Java's Swing tool-kit was always a slow ram hog when used without proper knowledge.
I'm implying that the gold rush on mobile apps has attracted sub par developers that write crash prone iOS apps because they don't understand memory management.
RE[2]: You're wrong. It's bad iOS developers.
by sithlord2 on Sat 4th Feb 2012 13:04
in reply to "RE: You're wrong. It's bad iOS developers."
"The majority of these iOS apps crashes can probably be attributed to bad programmers that can't manage their memory properly.
You know, it's funny... if somebody makes a comment about how many desktop Java apps run like ass, people are quick to blame programmers as well. Surely, it CAN'T be the languages that suck
" No, it's the programmers. You can perform bad memory management in every programming language (including java).
Ex:
In C/C++ if you don't release memory, you'll get memory leaks
In Java or .NET: If you don't dispose objects the GC will not re-use their memory, and will keep requesting new memory blocks from the OS with every new().
Memory management is the responsability of the programmer, not the language (despite what some Java or .NET folks say).





Member since:
2005-11-13
You know, it's funny... if somebody makes a comment about how many desktop Java apps run like ass, people are quick to blame programmers as well. Surely, it CAN'T be the languages that suck