BudVVeezer

Should have named it "C Tuesdays" since there's basically nothing related to Objective-C in the article...

The fact still remains that wchar_t is still a royal pain to use across platforms. Sure, it defines the size of a single character consistently within the platform. But it doesn't define what encoding that is. USC-2? USC-4? And the fact is: different compilers define it differently, which sucks in practice.

Perl -- the world's premier write-only language.

Inaccurate in what way?

It may be trivial to solve, but it's certainly not an issue anyone should have to solve, if the C++ standards committee would have dictated size and encoding information along with the datatype.

Am I the only one who finds the grammatical mistake in the post title humorous?

I love how there is no actual USAGE of the color in the article. :-P

Or there's people like me who get a MacPro tower from work and promptly install Windows on it because it compiles huge projects significantly faster than XCode...

Seriously, it's about getting a job done -- use what works. Who cares what the name of the OS is? I don't care whether I'm using a Dewalt drill or a Black & Decker. I care whether the drill works. Why is a computer any different?

Pretty light on actual information...

I can agree to that somewhat, but what's interesting about this paper is that it's starting to formalize the fact that some people can "think like a programmer" and some can't. Now, what that says for programming paradigms as a whole...

It seems to me that the complaint is "what used to fail with this error code now fails with a more annoying and scary error code." It's still a regression, but hardly one that's a huge cause for concern.

Failing to call "delete" on a pointer you "new"'ed in C++ is also clearer, and just as incorrect. The ECMAScript spec makes no mention of how memory will be managed for the user. Right or wrong in terms of clarity, it's still a poor practice to assume the browser will behave in a particular way that's not covered by the specification (regardless of how sensible that behavior might be!).

I think developers should always try to avoid poor programming practices instead of relying on implementation details of the browser.