Linked by Thom Holwerda on Wed 29th Aug 2012 22:52 UTC
Linux Miguel de Icaza: "To sum up: (a) First dimension: things change too quickly, breaking both open source and proprietary software alike; (b) incompatibility across Linux distributions. This killed the ecosystem for third party developers trying to target Linux on the desktop. You would try once, do your best effort to support the 'top' distro or if you were feeling generous 'the top three' distros. Only to find out that your software no longer worked six months later. Supporting Linux on the desktop became a burden for independent developers." Mac OS X came along to scoop up the Linux defectors.
Thread beginning with comment 533266
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Comment by miscz
by akrosdbay on Thu 30th Aug 2012 15:28 UTC in reply to "RE: Comment by miscz"
akrosdbay
Member since:
2008-06-09


As for OSX being simple and easy to use, how many of the OSX users here run any of the following:
OpenVPN
Samba
SSHFS
NFSv4


My clients have asked around and so have I and I've yet to get an answer to the basic question: what does OSX have for workable file and print services? It sure isn't SAMBA/CIFS (horrendous performance) and isn't NFSv4 and it's not appletalk so what do you use?



NFSv4 is supported and I use it every day.
Smb support:
http://support.apple.com/kb/HT1568

OS X uses CUPS for print services.

If you can be more specific with what your problem is it will be helpful.

Reply Parent Score: 1

RE[3]: Comment by miscz
by trev on Thu 30th Aug 2012 20:19 in reply to "RE[2]: Comment by miscz"
trev Member since:
2006-11-22

I should have just said File services. You are correct in pointing out we had no printing issues. I'm just a bit used to saying "file and printer sharing".

As I said in my original post SMB is supported just unusably slow in our testing (about 10% of linux or windows clients). We tested this about 1.5-2 years ago and on both 10.5 and 10.6 on several machines. At the time the client and I both asked around and there were very few suggestions offered to improve the abysmal performance. A quick google of the issue shows it has been around and felt by many with only recent suggestions (mid-2011) being offered. Maybe they've resolved some of the issues now but not so long ago it was brutal.

As for NFSv4 from what I recall we had the following problems:
1. No user ID mapping support (we had to go to global user IDs if we wanted it to work, a major pain even in a small company)
2. Kerberos authentication integration was problematic
3. DNS updating and host file issues were difficult to make it work with a VPN
4. User side install nightmares. Getting NFSv4 setup was a bear (NFS w/ kerberos over a VPN). In the end this is the issue that killed it. Scripting it was not possible because many things needed to be done through a GUI (no CLI tools for it) so it make the process unreliable when done by average users.

We rolled this same thing out to Linux desktops and Windows (NFS software was expensive for the windows clients) in testing with a small fraction of the difficulties. When problems were encountered on OSX there was a lack of documentation, knowledge base answers from forums and other sources and a void in finding anyone who was even using OSX in a business environment.

Maybe some of that is being fixed now but to say that OSX is much easier than Linux on the desktop really makes me wonder. My client still is predominantly an OSX shop. They just had to move to SSH as the filesharing method because nothing else worked. It works pretty well but is not a true filesharing technology so they have to be careful (no file locking, etc). All in all it works for them now but it was a rough transition mostly because of difficulties on the OSX side.

Reply Parent Score: 3