#Os x mail run rules driver#
#Os x mail run rules software#
#Os x mail run rules code#
#Os x mail run rules series#
#Os x mail run rules mac#

There's also a lot of software I like to use that aren't available on OSX yet. Anjuta, Geany, Eclipse, KDevelop vs XCode, Eclipse). While I love the Cocoa API and what it allows apps to do, Linux is catching on fast, and I find that good GNOME or KDE apps perform most, if not all, the functionality I care about in OSX, while being beer free, and offering me more choices (i.e.

However, Linux offers me a great deal more choice, and that choice tends to be much more configurable to my needs. While both systems are good, I perceive the Linux market as responding more credibly to security issues. 10.5 is supposed to have MAC, but I can't find any info on it. Also Linux offers some features that OSX doesn't currently offer, such as MAC.

#Os x mail run rules driver#

OSX is pretty good, but I'm a little worried at Apple's highly negative response to security concerns (anyone remember the wireless driver exploit fiasco?).

I can enable, disable, theme, customize, and otherwise hack my environment to suit my needs much more easily than in OS X. While this is pointless for 90% of users, for me, it is very nice to be able to custom compile a kernel with the options I need, recompile any given app for the characteristics I need, and so on. Linux gives me a lot more control over my OS. With Linux, I have a much wider choice of hardware vendors.

#Os x mail run rules series#

It can be hacked, sure, to run on some non-Apple systems, but widescale hardware compatibility is lacking (just look at the difficulties in getting a GeForce 8x00 series card running). For me, my move from OS X to Linux is motivated by several reasons. Neither Linux nor FreeBSD had this problem.ДЄt any rate, how is the codeweavers support for playing iTunes videos? That's really the only thing I use iTunes for is video. I also hate that my 4 USBserial connectors are flaky, and have to be re-plugged before they'll all show up on boot. Specifically, the external editor plugin for Thunderbird so that I can edit messages in xemacs, and the noscript and adbplockplus extensions for Thunderbird. I started out using Mail and Safari, but I moved back to Thunderbird and Firefox for the plugins. I also find that the only MacOSX application I ever use is iTunes. However, X locks solid every few weeks (usually when I scroll too much or too fast in some window). To get around some of this, I run most of my shells via xterm. I hate the menu bar at the top, I hate not being able to define *MY* hotkeys for resize, move, and iconify, I miss the easy X11 1-click cut and 1-click paste, etc. I've found that after more than a decade and a half of being able to customize my desktop behavior, I just can't adjust to the MacOSX gui. I've been running 10.4.x on my Core 2 Duo iMac since last October. Last year, after we had a baby and I had essentially no time, I finally got tired of maintaining my system, and thought the 'just works' aspect of MacOSX might be a nice change. I've run *nix on the desktop for roughly 17 years. I'd love to be able to confine MacOSX to a window. For 99% of what I do, MacOSX is a flaky pain in the neck. For the few apps that would be worth supporting, it is probably easier to re-write them from scratch than it is to write a general purpose compatibility layer.

#Os x mail run rules mac#

There are far fewer essential applications for the Mac (90%+ of computer users don't use any OS X apps, after all), and so no one has bothered.

WINE has had a lot of time and effort put into it because there are a huge number of proprietary Windows-only applications that would be useful on other platforms already deployed. You would also not be able to run anything that depends on WebKit (unless you use GNUstep's SimpleWebKit as a stop-gap), QuickTime, or any of a number of other frameworks that have not yet been added to GNUstep. There is no open source version of Carbon, although a few people have written GNUstep wrappers for the parts of Carbon which are toll-free bridged with Cocoa. Unfortunately, a lot of OS X applications also use Carbon. If you did this, you could run applications that just used Cocoa.

#Os x mail run rules code#

This is pretty easy (the code is ASPL), but currently GNUstep has problems running with the NeXT libobjc (it uses the GNU one by default). Next you would need to compile the Apple (NeXT) Objective-C runtime library on Linux. Linux uses ELF as the format for binaries, and so the loader can not start and link OS X applications. In order to run OS X pure-Cocoa applications you would also need a Mach-O binary loader. GNUstep gives source compatibility and is now fairly good at reading nib files. There are a few more things required than just GNUstep. Producing a Cocoa compatibility layer should be much easier than producing a Windows compatibility layer.