Earlier quoted context omitted.
Well, and after years of his project slavishly imitating Windows, its latest iteration is slavishly imitating OS X. So, good work all around. Edit: vvvv I stand corrected. Double Edit: What exactly do you mean, anyway? Things like http://www.linuxtoday.com/developer/2002020601120OPGNMS , dated 2010, seem to indicate he's still active within GNOME.
That seem to be dated to 2002.
How I ended up with Mac
171–180 of 199 posts
Re: How I ended up with Mac
#172My main gripe with Novel and now Xamarin is that they don't provide packages for Debian and Ubuntu, arguably the most popular Linux distributions. For instance if you go to Mono's download page to checkout the options, the only Linux distribution supported by them is OpenSuse: http://www.go-mono.com/mono-downloads/download.html Of course one could argue that Debian (and Ubuntu that relies on Debian's repository) has…
> When you are working day-in day-out with Java, Ruby, Python, Javascript, Mysql, Postgresql, GCC, Casandra, MongoDB, Memcached and dozens of other technologies, installing that stuff and having it work on OS X is amongst the most frustrating experiences I ever had, no matter if you're doing it by hand or with MacPorts or with Homebrew. All available options on OS X suck. I couldn't give a fuck about binaries of comm…
Re: How I ended up with Mac
#173I can't believe all the talk about Finder here.. I bet Miguel is more like me than most of you, that is, living in a unix/linux terminal for the last 15 years or more - AND doing file management in that terminal! I've also gone to the Mac from unix/linux as my primary machine as it just works. What I mean by that is suspend/resume, wifi, and all that stuff that you shouldn't think about anymore. Sure, all I use on it…
Absolutely. I don't use much more than iTerm2, a web browser, emacs + various developer stuff, and Homebrew. The base OS is rock f-ing solid. All my unix stuff works flawlessly. Time spent f'ing around with drivers and random upgrade issues? Zero. It even syncs with my phone (iPhone), which happens to work great! Finder? Who gives a crap? That's what the terminal is for!
As for upgrade issues... I apt-get upgrade weekly because things are getting fixed. OS X is still shipping the same out-of-date copy of BSD tools they've been using for years.
Re: How I ended up with Mac
#174I'm always amused by these posts praising how everything just works on the Mac, and how it's so nice not having to worry about [annoying linux/windows stuff #351]. Am I really the only one blind to this effect ? I've used a mac. It's nice. But it "just works" only until you want to productively use Finder, or you want to connect to a Samba server, or you want to shuffle files with UTF-8 filenames around, or a dozen o…
> or you want to connect to a Samba server I don't have a mac in front of me, but don't you just simply go to Tools -> Connect To Server then type in smb://IPADDRESS ? Why is this difficult, and what would a better alternative be?
open works with loads of protocols, not just files, for example 'open vnc://host' works out of the box.
Re: How I ended up with Mac
#175Re: How I ended up with Mac
#176Earlier quoted context omitted.
* >Incorrect in what parallel universe? >Yes. OS X is just a collection of applications of which iPhoto is NOT one. IIRC, they don't even bundle iLife anymore (you're supposed to get it from the App Store) but that's beside the point.* iPhoto IS one. As I distinctly explained in my previous post, iPhoto comes installed on every every single Mac that Apple sells with the sole exception of the server configuration of t…
> For better or worse, iPhoto is a part of the Mac experience. Sure, it's a non-part-of-the-core-OS, bundled for free, easily replaceable, with 10s of alternatives, peripheral to using a Mac, part of the Mac experience. To return to our duck-ing topic, what does that have to do with OS X being bad or "not just working"? If you had to bring up a bundled, non-essential, app to make your point of OS X not working well,…
I believe you are well aware that you are being disingenuous by treating iPhoto as some sort of unrelated third party application that you have no idea why anyone would bring up out of be blue in a discussion about OS X. Who cares if its "non essential", most of the stuff in OS X is completely non-essential (ahem dashboard, photo booth, even mail considering most people use webmail).
Re: How I ended up with Mac
#177Earlier quoted context omitted.
* >Incorrect in what parallel universe? >Yes. OS X is just a collection of applications of which iPhoto is NOT one. IIRC, they don't even bundle iLife anymore (you're supposed to get it from the App Store) but that's beside the point.* iPhoto IS one. As I distinctly explained in my previous post, iPhoto comes installed on every every single Mac that Apple sells with the sole exception of the server configuration of t…
> . As I distinctly explained in my previous post, iPhoto comes installed on every every single Mac that Apple sells with the sole exception of the server configuration of the Mac Pro. Go to the Apple web page and click on any Mac and look at the "Built-in Apps" section, you will see iPhoto displayed right alongside "system" apps like Mac App Store, Mail, and Messages However, reinstall MacOS, and you will notice it…
Re: How I ended up with Mac
#178Earlier quoted context omitted.
* >Incorrect in what parallel universe? >Yes. OS X is just a collection of applications of which iPhoto is NOT one. IIRC, they don't even bundle iLife anymore (you're supposed to get it from the App Store) but that's beside the point.* iPhoto IS one. As I distinctly explained in my previous post, iPhoto comes installed on every every single Mac that Apple sells with the sole exception of the server configuration of t…
> . As I distinctly explained in my previous post, iPhoto comes installed on every every single Mac that Apple sells with the sole exception of the server configuration of the Mac Pro. Go to the Apple web page and click on any Mac and look at the "Built-in Apps" section, you will see iPhoto displayed right alongside "system" apps like Mac App Store, Mail, and Messages However, reinstall MacOS, and you will notice it…
Re: How I ended up with Mac
#179My main gripe with Novel and now Xamarin is that they don't provide packages for Debian and Ubuntu, arguably the most popular Linux distributions. For instance if you go to Mono's download page to checkout the options, the only Linux distribution supported by them is OpenSuse: http://www.go-mono.com/mono-downloads/download.html Of course one could argue that Debian (and Ubuntu that relies on Debian's repository) has…
I'm surprised to hear this, as I've had the opposite experience with a similar toolchain, especially since the advent of Homebrew. What problems are you running into exactly?
Another thing with OS X is that it just works, until it doesn't. After that you're in Windows-land again, the preferred option being to just reset/reinstall everything.
Again, never had this experience. I would love to hear how you're managing to FUBAR your Mac.
Try building a Hackintosh sometimes and your appreciation for Linux will change.
Have all of these issues been on a Hackintosh? If so, that might explain things ...
Re: How I ended up with Mac
#180Earlier quoted context omitted.
From what I could understand when this bit me, OSX uses a different normalization form from what Linux uses (I'm not even sure of what that means, but hey). OSX uses NFD, while pretty much everyone else uses NFC (by default). So, if you use scp (Finder and the UI seem to convert things on-the-fly) to move files with UTF-8 filenames (mine where of korean origin), you'll end up puzzled because you're supposed to have s…
> OSX uses a different normalization form from what Linux uses (I'm not even sure of what that means, but hey). http://en.wikipedia.org/wiki/Unicode_equivalence#Normal_form... > OSX uses NFD, while pretty much everyone else uses NFC (by default). It depends on the file system. HFS+ uses UTF-8 NFD, as you noted. On Linux, ext4 uses whatever encoding your tools happen to use, as long as it's an 8-bit ASCII superset cap…
It looks like some versions/builds of rsync are encoding-aware (e.g., http://blog.gimpe.com/2009/09/13/tip-use-rsync-to-convert-fi...), although some recent builds may not be (http://cygwin.com/ml/cygwin/2011-05/msg00467.html).