Pro's use Macs and Nikons.
Really!? Are we going there again this evening?
Pro's use Macs and Nikons.
Does it ever go away!Really!? Are we going there again this evening?
Yeah it goes away! I am the one in denial remember...Does it ever go away!
In all seriousness computers and cameras are just tools.
Just pick what you need and use it.
Really!? Are we going there again this evening?
I've heard that Canons are like Macs and Nikons are like Windows machines. Since I rarely use Windows, and have a Nikon DSLR, not a Canon, I don't really understand the analogy.Pro's use Macs and Nikons.
Lots of good answers here, but for me going Apple was because I use a PC all day and want to come home to something different.
Also my experience with PC's was less than stellar. When you have an issue, the hardware manufacturers blame the software, the software manufacturers blame the hardware.
As Apple made both I figured it would be easier to deal with.
So bought an iMac in 2012, and never had any major issues with it.
In 4 years I'd have probably ended up replacing a PC twice.
I just want to use a computer, not maintain it. I'm sure Windows has come a long way, but I'd rather stick with something that just lets me get on and do stuff.
Back up is easy out of the box too.
I've heard that Canons are like Macs and Nikons are like Windows machines. Since I rarely use Windows, and have a Nikon DSLR, not a Canon, I don't really understand the analogy.
Maybe it has to do with Nikon maintaining lens compatibility back to the dark ages, and Canon using the (slightly) newer EOS mount.
Funny, I'm fluent in Mac, Windows, and Linux, during the day I work as a server admin and by the time I get home I'm so tired of updates that I prefer Mac just because I know that all that was taken care of for me during the day. Less hassel, less headache, no driver issues, just go time.
[doublepost=1462825689][/doublepost]
Yes Nikon's El Capitan support is deplorable, love their cameras, but please Nikon, fix your software please!
Super patch Tuesday and a 10,000 server estate... Yeah talk about purgatory eh?!
Pro's use Macs and Nikons.
No, that's not correct. The two kernels of Linux and OS X aren't even related, the Mach kernel was built as a micro kernel while the Linux kernel is monolithic (the distinction is for the most part obsolete these days). Have a look here: Linux has been created independently of the “proper” unix operating systems. But it is not a branch of the original unix like OS X is.Some guys at Berkeley built a branch off of UNIX creating what was called BSD, the other branch was what we know as the main Linux distros, were based on AT&T SVR4 UNIX.
The history of NT is quite complicated. The underlying OS architecture isn't all that bad actually, especially when it was introduced, it was really a milestone. The problem is everything that is on top of the kernel such as the APIs and the criminally ugly UI. Of course, there were some problematic decisions that were rectified in part later (e. g. the “window server”, GDI, was moved into the NT kernel for a while for performance reasons).I do agree with you that one great advantage of OS X is its core OS. I never had any doubt that Windows at its core was spaghetti. Maybe Windows 10 is getting better.
Ummm I just wonder why photographers prefer Mac or OS X for photography career? Every places I visited have at least iMac or Macbook pro for working. For me, I have a bad experiences with Window 10 that I have to format everything because the system is really unstable.
Personally, I don't see any advantages in performance but why? Any reasons such as color profile or?
In my younger days (Apple ][+), I was an Apple evangelist - I bled 6 colors and put down everything non-Apple. I am still a strong Apple user on a personal level - I use Windows at work because that is what is required.
I owned Canon film cameras, so when they went digital, I had no compelling reason to start over with Nikon, so I stayed and have been quite happy. Could I get the same images with Nikon? Of course!
My bottom line to computer and camera choice? Why reinvent the wheel? Assuming equal performance/cost (NOT a fair assumption - see below regarding stability, security, etc.), a computer and camera are a TOOL for my work. Tools work for me, I don't work for them.
Now that I am a 50 year old guy, I recognize that all the more. I am comfortable with my Apple and Canon ecosystems and see no compelling reason to change them. I don't want to learn how to manage a windows system or new control layouts on a Nikon body. Our house has multiple wired base stations that seamlessly broadcast our wireless network, multiple AppleTV's stream media all over as well, our myriad computers, iPads, iPhones, and MacBooks all JUST WORK and I've grown quite comfortable trouble-shooting. I would dread having to learn all those pearls and tricks if I had to go Windows. But if Apple disappeared tomorrow, that's just what I would do.
So short answer to long answer - stick with what you are comfortable with and can afford. If something new and shiny comes along, ask yourself if it is worth learning over what you already have.
Does it ever go away!
In all seriousness computers and cameras are just tools.
Just pick what you need and use it.
Photographers and artists in general like to use the Mac because they aren't necessarily wireheads. They want to do their thing and get it into the digital lab for some finish work. With the Mac, the computer comes out of the box with an OS from the company that built (or at least designed) the hardware, so, as they say, It Just Works. With Windows, you generally buy hardware from Dell or HP with Windows installed. Since the hardware people can't just leave well enough alone they stuff it full of all this junk that messes up a perfectly good system. I'm ccurrently muddling along with an HP Pavilion laptop since my '08 MBPro bit the dust (video card). I swear the thing hates being hooked up to a Mac keyboard. I've tried to remove the "HP Assistant" (remove istant) but it keeps reinstalling itself. The only way to get an off the shelf PC to run in a straight line is to blank the drive and install a full price copy of Windows.
Kind of like buying a car and throwing out the engine. Wait...I did that...
And that's why photo folks use Macs...
Dale
No, that's not correct. The two kernels of Linux and OS X aren't even related, the Mach kernel was built as a micro kernel while the Linux kernel is monolithic (the distinction is for the most part obsolete these days). Have a look here: Linux has been created independently of the “proper” unix operating systems. But it is not a branch of the original unix like OS X is.
The Linux kernel also doesn't have a relation to the many BSDs that are currently in development (e. g. FreeBSD, OpenBSD, NetBSD and smaller projects such as Dragonfly BSD), it a from-scratch implementation of many of the ideas of Unix. The reason is very simple: at the time, the BSD projects were in legal hot water, and because Linux was implemented from the ground up, it was not involved in the legal skirmishes. There is also a second huge reason why Linux and BSD kernels are not related: the licenses are mutually incompatible.
That's why some old-timers (like myself) write *nix, unixoid or somesuch to be extra precise about the differences. What is nevertheless correct is that all of these OSes implement a common philosophy (with differences in the details, of course), and if you get non-GUI code to run on, say, FreeBSD, it's easy to make it work on OS X and Linux as well. If that's what you meant with your initial comment, I'm with you.
The history of NT is quite complicated. The underlying OS architecture isn't all that bad actually, especially when it was introduced, it was really a milestone. The problem is everything that is on top of the kernel such as the APIs and the criminally ugly UI. Of course, there were some problematic decisions that were rectified in part later (e. g. the “window server”, GDI, was moved into the NT kernel for a while for performance reasons).
Distro ≠ kernel.Are you referring to the SCO Unix legal skirmishes? As they were around use of proprietary code in the SVR4 based Linux distros and AIX, Solaris and HP-UX no?
Fair enough, I agree, and this was indeed one of the reasons why I fell in love with Mac OS X DP2. I can (and have) the command line open pretty much all the time, but at the same time I enjoy plug & play and a beautiful UX and UI. Best of both worlds really.Anyway, this is a photography forum not OS history... so let's stop getting pedantic and move on. My point was, Mac was closer to the systems I worked with at the time so was beneficial to my productivity.
Distro ≠ kernel.
And no, I was referring to the Bell Labs/USL lawsuit from the late 1980s/early 1990s.
Linux vs. SCO was a decade later. This lawsuit not only gave birth to FreeBSD (where the proprietary USL parts of 386BSD were replaced by homegrown code), but also motivated Linus Torvalds to start his own Unix clone project (because neither 386BSD nor the GNU kernel were freely available at the time). So historically, Linux is a Unix clone rather than a proper descendent of Unix.
Regarding SVR4, if memory serves the problem here was not that Linux was using code, but that it could run SVR4 binaries. SCO did allege that Linux was illegally using proprietary source code, but I don't think this was ever affirmed by a court.
Fair enough, I agree, and this was indeed one of the reasons why I fell in love with Mac OS X DP2. I can (and have) the command line open pretty much all the time, but at the same time I enjoy plug & play and a beautiful UX and UI. Best of both worlds really.
You techies. I'm so confused!
Nice trip down memory lane. Nothing like an "ux" system working furiously for a day and a half to generate a fractal on a lower rez screen.
Yep, Unix, Linux, Free BSD, OSX and Microsoft the eunuchs OS.