Domain: mamasam.com
Stories and comments across the archive that link to mamasam.com.
Comments · 9
-
Re:Cost analysis
Are you using the server? If so try using adduser.
adduser replacement for Darwin (found after a quick Google)
-
Re:Let's hear more details about your break-in
You have a couple of GUI-less options:
http://www.macosxhints.com/article.php?story=20030 603190314390
http://cocoa.mamasam.com/MACOSXDEV/2002/12/1/51614 .php
But I always use the GUI. I'm less likely to break things that way. -
Good Tutorial
I read through the first edition about a year ago, and found it to be an excellent hands-on tutorial, gradually walking the reader through the construction of increasingly complex apps. I came at the book from a strong C++ background and various Microsoft technologies, and zero experience with Mac software development, and left with a reasonable beginners knowledge of Objective-C and Cocoa. Supplement this tutorial with resources like Apple's reference material and the mindshare at the Cocoa developer list archives, and you'll be well on your way to developing your first Mac app.
I'm glad to see that the second edition added AppleScripting and material on implementing Undo, even if at the expense of the Java chapter. (No surprise, there: in the beginning of the first edition's Java chapter, Hillegass basically says this about programming Cocoa using Java: "DON'T.") -
Definitely a step in the right direction...
The newly release Reference Library is very well organized and makes finding things much easier. Good job, Apple! It's been a long time coming!
There's still a problem, though. Much of the "state of the art" documentation is actually happening on the Mac OS X and Cocoa mailing lists. It's good to have reference materials, but if you're looking for information on the latest & greatest addition to the OS, go search the archives.
You'll find that you can get answers directly from the developers before the reference materials are formalized and made public. As an example, in the months following last year's WWDC, there was a ton of information on the lists about the new Cocoa Bindings. As a developer who wants to stay on the leading edge of Mac OS X product development, this is invaluable.
Also, the guy that is running the mailing list archive, is looking for donations. If you are a developer who uses these archives, PLEASE DONATE.
-ch -
Re:Jagged fonts
There are several settings in the system preferences that allows one to change how anti-aliasing is used on your system.
I'd also be willing to bet that panther is doing some sort of update to the anti-aliasing hence the jagged looking fonts while the bugs are being worked out.
As for you comment about mac people being more artistic I suggest you point your browser to sites such as The O'Reilly Network and The developer mailing list archives to see just how big of an audience the mac really has. Sure there are plenty of artsy folk using the mac, but there is also a slew of terminal junkies as well.
-
He's got it right about developer documentation...
He's right on target about developer training & documentation. It sucks big-time: poorly categorized and there is lots of missing information.
When I'm looking for an answer to a technical problem, I typically find answers at sites like Mamasam or CocoaDev. The Cocoa Dev Central site is a good source of sample code, too. Many more resources are listed here
Historically, Mac developer's have been very picky about this: Inside Macintosh is wonderful. It's an excellent technical reference presented in a consistent and easily readible format. -
He's got it right about developer documentation...
He's right on target about developer training & documentation. It sucks big-time: poorly categorized and there is lots of missing information.
When I'm looking for an answer to a technical problem, I typically find answers at sites like Mamasam or CocoaDev. The Cocoa Dev Central site is a good source of sample code, too. Many more resources are listed here
Historically, Mac developer's have been very picky about this: Inside Macintosh is wonderful. It's an excellent technical reference presented in a consistent and easily readible format. -
Re:Rushed job?
There are some notes in the Cocoa mailing list about the Safari implementation. -
Please learn some logicOf course I know you didn't directly state that I was a Mac Bigot. (Have we even met?) But you did say that Siracusa was a "Mac bigot" because of his belief in Classic MacOS Metadata. By inference, anybody who shares this belief is also a "Mac bigot". Go draw a Venn diagram if you can't figure that out.
Even if that's not what you meant to say, somebody had to shoot down your linkage of metadata technology with Mac true-believers. Look, every theory has its kneejerk, dittohead followers. Has nothing to do with whether the theory is right or wrong.
But in fact, I am not dismissing Siracusa's opinions out of hand with simplistic stereotypes; I've just gotten tired of re-writing an essay on why he's wrong every time I come across a group of Mac users who think he's the cat's meow and think that hes conclusions on metadata are authoritative. If you'd like to read some of them, look on MacSlash, or look at old articles here on Slashdot where Siracusa's "definitive" articles have been posted.
You said "Until Siracusa [figures out how dumb his opinions are] he's just one more Mac bigot". Only with a rude, contemptuous metaphor to express the concept in square brackets. Does anyone else here not see this as dismissal? Don't all raise your hands at once!First you identify Siracusa with his less intelligent followers, then you say, "it's not him, it's his followers." I think we need another Venn diagram.
As for your trauma in being forced to converse with uncritical Siracusa true-believers -- well, that doesn't mean you're not a bigot. You're still rudely dismissing Siracusa, you're just using the actions of other people to justify doing so. In other words you're a self-justifying bigot. Most bigots are.
Looks to me like you have generalized from Windows' poor implementation that file extensions are bad; the same mistake I think Siracusa makes. Believe me, file extensions are imperfect, but right now Mac OS X has the best type system available in a high-volume operating system.
OK, now that's actually a technical argument. And it's even a valid point. I have to confess ignorance of exactly how extensions work in OS X. I gather there are extension-handling feature that are better than those in Windows. But as long as a user can mung the data type of a file just by changing its name, I don't see how you can complete (or even mostly) avoid the problems I describe.