Re: [MacPerl] Installing on Users' Macs

["Shin Yamamoto" <shinyam@earthlink.net>]

Well, I see those of you sys-admin's headaches. I understand this. I'm
sorry.

However, from a user's point of view, allowing a user to install
applications like MacPerl or CodeWarrior or whatever  on Macs is asking for
a disaster. Because Macs are basically not to be designed for that kind of
programs in general public. What kind of administrators install developing
tools on library Macs? I think that's a part of system administrator's job
as to where to install what kind of programs. If you have users who can
barely run a installer, the users don't need MacPerl. If they still think
they need it, that's also a part of system administrator's job to educate
users BEFORE installing anything. Or a system administrator can always ask
users why they want MacPerl. Maybe they only want to learn the language. In
that case, the admin can refer him/her to Unix environment where everybody
can safely, comparing to Mac, run Perl and everybody can be happy.

I have to object an idea regarding invisible files. A locked attribute is OK
as far as they can be seen their presence. But invisible and locked files,
no. Again, as a user, it's a kind of invasion of privacy. Maybe a bit
exaggerated, but isn't it a unix administrator's ethics that just because a
root user can see/do anything doesn't mean s/he is allowed to do anything
without notifying users. Same thing here. Besides, invisible files on a Mac
need special tools to be found, as oppose to a leading dot on a unix system
that can be easily seen if a user knows how to use ls. Please don't even
think about this. Macs are supposed to be user friendly, so are the
administrators, aren't they?

Just my $.02

Shin Yamamoto

***** Want to unsubscribe from this list?
***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch