Linked by Thom Holwerda on Wed 20th Oct 2010 19:02 UTC
Apple So, Apple held its usual autumn press get-together just now, and after a few rather uninspiring ones (to me, at least), they finally managed to blow me away, with the new MacBook Air (especially the 11.6" variant). They also gave a sneak peek at Mac OS X 10.7 Lion, which has... An App Store. An App Store Apple is going to open on Snow Leopard within 90 days.
Thread beginning with comment 446480
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Comment by Kroc
by Morgan on Fri 22nd Oct 2010 02:03 UTC in reply to "RE[6]: Comment by Kroc"
Morgan
Member since:
2005-06-29

Well, *nix systems have the advantage of allowing you flexible access to the lower levels of the system, and in an approachable, programmatic manner.
Free operating systems give a much bigger opportunity for education, as well.


Okay this has been bugging me for a bit now. OS X is closer to true Unix than Linux is, given its pedigree. Yet when you say *nix you seem to refer only to Linux and not the other Unix-like OSes. From Wikipedia:

A Unix-like (sometimes shortened to UN*X or *nix to circumvent trademark issues) operating system is one that behaves in a manner similar to a Unix system, while not necessarily conforming to or being certified to any version of the Single UNIX Specification.

Source: http://en.wikipedia.org/wiki/Unix-like


Emphasis is mine. I know what you mean, and I'm sure everyone else here does too. I don't disagree with your sentiments; I also feel that Free software is the most flexible and approachable from an experienced user's perspective. But don't forget that OS X is a *nix too, and has all that *nix power behind it as well.

That said, I also feel much more comfortable digging around in the Linux terminal than the OS X one. One of the great things about OS X though, is that you don't have to drill down to that level nearly as often; the OS has a lot of hidden power in the GUI that just takes time to get used to.

And just for the sake of full disclosure, I'm typing this in Windows, because it's the computer I happen to be at right now (just got done playing a Windows game).

Reply Parent Score: 2

RE[8]: Comment by Kroc
by TheGZeus on Fri 22nd Oct 2010 02:25 in reply to "RE[7]: Comment by Kroc"
TheGZeus Member since:
2010-05-19

I (grudgingly, look at systemd) include OS X in *nix.

The free OS portion following that is a separate point entirely, and would include non-*nix systems like Syllable and even ReactOS.

I think anything else you would have said would have been the result of misunderstanding again.

Reply Parent Score: 1

RE[8]: Comment by Kroc
by Neolander on Fri 22nd Oct 2010 04:40 in reply to "RE[7]: Comment by Kroc"
Neolander Member since:
2010-03-08

That said, I also feel much more comfortable digging around in the Linux terminal than the OS X one. One of the great things about OS X though, is that you don't have to drill down to that level nearly as often; the OS has a lot of hidden power in the GUI that just takes time to get used to.

Well, in my experience, most modern desktop linux distros either work out of the box without touching a terminal or won't work unless you really want to spend hours wrestling with them.

I never had to open a terminal on linux except for a few uncommon tasks (coding, anything which requires sudoing because most linux distros don't have a "run as root" menu item in the file explorer, anything which requires launching an alien binary from the internet) for some time now.

Reply Parent Score: 2

RE[9]: Comment by Kroc
by Morgan on Fri 22nd Oct 2010 04:57 in reply to "RE[8]: Comment by Kroc"
Morgan Member since:
2005-06-29

Wait, Slackware isn't modern? ;)

I get what you're saying though; the only time I've used the Terminal on my netbook (running Ubuntu Desktop 10.04) is to start the Easytether client for tethering to my phone. It's CLI only, and while I've written a simple script to enumerate the modem, start the service and point dhclient at the device, it's finicky and doesn't always work with a simple double-click. I find it works every time if I open the Terminal and run the script from there.

That more or less defeats the purpose of having the script, as it's only two commands -- easytether enumerate | easytether connect and sudo dhclient easytether0, which if stored in the shell buffer are a couple of keypresses away.

I'm no programmer, but I can see myself one day finding the motivation to make a simple GUI interface to this process, probably using something as straightforward as Tcl/Tk.

Reply Parent Score: 2