People who aren't cool enough for a Mac. Haven't you seen laptop hunters?

In fact, they're marketing to people who have enormous chips on their shoulders about being so entirely uncool (or poor) for Macs.

I jest. They're talking to themselves. Microsoft's insecurities have been laid utterly bare in all their marketing attempts for a decade.

There was a joint interview with Jobs and Gates not too long ago that I'm too lazy to dig up, and a question was asked "what do you envy about the other" -- Gates' answer came off as snide, yet honest: "I wish I had your taste"

They've been at this since the Zune came out and they started marketing to the Wal-Mart demographic. Because Wal-Mart folks like brown things that work almost sorta as well as an iPod at the same price. Because you're not cool enough for an iPod, and you've got a chip on your shoulder about it.

The weird part is... that demographic's pretty much stuck with MS out of ignorance, and MS is tilting at windmills whenever they go against apple. They inevitably end up looking as insane (and sad) as Don Quixote himself.

They're trying so hard to astroturf these days, build a viral movement. I'm not sure they understand that apart from a handful of lunatics/idiots/middle managers out there, there is nobody on earth who actually likes Microsoft. Maybe they do understand, and they're trying to overcompensate?

Their messaging isn't helping any.

So, as a career advertising guy (15 years & counting) I don't get it either.

Round about Vista/Zune, MS and their various agencies of record starting shooting themselves in the foot. I'm here to tell you Crispin/Porter is a great, kooky agency... but they just can't speak to the Wal-Mart moms that MS thinks they're in danger of losing.

Microsoft's achilles heels are Office (in the near term) and Mobile (in the long term). If they lose control over file formats and Exchange lock-in, Microsoft as we know it gets pushed over their tipping point. Over the long term, so many of our common tasks will be moving to mobiles or embedded devices instead of PCs -- and MS let Mobile languish as a steaming pile for the better part of a decade.

But now they're just shitting out me-too copies of consumer electronics.

Maybe the whole thing is misdirection? I don't think so, but there has to be a few smart folks at that company who can see the forest for the trees.

Actually, Mental Ray satellite (as craptastically buggy as it is) still had a 8-thread limit under Maya 2009 sp1a (patch notes say they removed the restriction, but watch your CPU usage with a dual Nehalem and tell me it's not locked to 8 cores still)....

But it's not so much that... I mean if you've got the budget for Renderman Pro or Mental Ray standalone, you've got the budget to build a farm properly, and yeah an i7 is most definitely worth every penny, Nehalem Xeons are great too if someone else is paying the tab. If you're buying Renderman Pro, you're likely getting Xeons.

I've got 3 identical i7s, a core 2 quad and a core 2 duo for rendering here, and whenever I'm doing hair (shave in particular) or some dynamics plug-in work, I get significantly better render time using the core 2 duo due to the nature of multithreading. If you're only using 1 thread on a hyperthreaded quad, you're only using 12% of the available processing power, and it's more efficient to use a slower processor that you can utilize more of, if that makes sense. Same goes for a few repeat offending after effects plug ins (cinelook and magic bullet come to mind here). I mean you could go a step further and run 8 single core VMs on an i7 to saturate the CPU doing a hair scene (actually works pretty well with linux VMs in a pinch).

I do love the i7s from the very bottom of my heart, though. I'm getting almost a 50% gain in frames rendered between q4400s and i7 920s using Mental Ray in most cases.

I'm a big fan of imaging my boxes, as you mentioned. Particularly with a small shop it can be an absolutely maddening time sink to troubleshoot faulty nodes.

I can't think of the last time I ran into the video card issue... might have been lightwave way back when, but I've seen it. The real point here is "make sure the stuff you're buying is suitable for the work you're doing". If the bulk of your software is single threaded still, an i7 box really might not be the best choice. For most folks doing this professionally, it's an awesome choice though. If you're editing HD or 2k/4k over a network, you need to spend a little extra cash to make sure your disk reads and net throughput are up to snuff.

With that goes: if you're using enormous float textures and displacement maps out the ass, you're going to lose a substantial amount of time on disk & network throughput. Go gigabit ethernet at a minimum (it's cheap) and get a nice, fast raid 5 or 6 for your primary storage (and get another big disk to back it up with, at a minimum). Just because you don't need much storage on those render doesn't mean you can cheap out on the drives (ie 5400 rpm throwaways). Disk and network throughput matter and the matter more as you add more render slaves.

Regarding Vista: it depends on your hardware. Up through SP1, I still had a couple of mainboards with unstable (*cough*nforce*cough) drivers in Vista 64, as well as a few pieces of software that required UAC off (eww). Gave up on Vista then and I've had really good, rock solid stability in XP64. Win 7 seems to be shaping up nicely on my 2 oldish Athlon x2 test sandboxes. I think this really depends on preference and available hardware, personally, but it's going to be a non-issue come October anyhow (and thankfully).

All fair points, but I must say that the Mental Ray workflow that's so prevalent among pro-sumer/small studio CG (now that Autodesk owns most everything and bundles MR) is terribly hard on memory usage, displacement or no, 32-bit float or no, physically accurate shading/lighting or no. Renderman is far far more efficient, however due to the licensing costs, not many of the little shops are using it.

The article suggests buying a crapload of boxes with 4GB RAM mainboards, and my argument is that if you find yourself in need of building a render farm of more than a box or two, you're doing yourself a huge disservice by following that advice.

I can tell you first hand that it's a nightmare best avoided to assemble a bunch of assets into layout only to find that you're throwing memory exceptions right & left on deadline.

I stand by that advice: if you're actually to the point of investing a fair bit of cash for some render boxes, spend just a couple more bucks on the mainboard and RAM so you don't build yourself into a corner. I'm talking about a $50 difference (including ram and mainboard) per machine to safeguard against blowing deadlines.

Sure, there are lots and lots of workarounds for memory/detail/physics/computation issues, but on deadline you don't always have the luxury of using those cheats... and sometimes you've just got to brute-force your way through a sequence. Dynamics and rendering in Maya with Shave & a Haircut come to mind. Incredibly powerful, but single-threaded. You'd be better off rendering hair and contact shadow passes on a single P4 than an i7 unless you're using Renderman in this case.

I think you misunderstood me on the crap GPU issue: there are some apps that literally won't launch at all without a certain level of hardware acceleration under Windows. Most pro-level apps have a CLI-only render interface that's commonly invoked by farm management software -- but not all do. The point I was making is: if you're buying a ton of anything, make sure it's going to do what you want it to do ahead of time. It would suck to get a bunch of motherboards in 1U cases that can't even take an AGP/PCI-E video card, and that was preventing you from using the software that you built the farm for.

The main message was really: these guys give you a low-end, once-size-fits-all recipe for building a 16U farm, basically, and at that level of game, I think their advice is pretty poor hardware-wise. You'd be insane to fork over the cash for that much kit and stick 4GB mainboards in there. Imagine someone who had a need for that kind of horsepower but were limiting themselves to the low end of the capability spectrum on such a major purchase when the price difference in the grand scheme of things to future-proof is so small. Not that there's such a thing as future-proofing, but if you're trying to render anything using mental ray with a 4GB system, I can guarantee you that you'll hit a memory wall after playing with ZBrush or mia* physically accurate materials for a few weeks. Or real global illumination etc etc. Particularly under Win32. Sure there are cheats for everything, but they take time too, and sometimes you just need to hit render and know that 1200 frames will be done by Monday AM without spending a huge amount of time tuning cheats.

If you're a small shop, in the vast majority of cases an Autodesk product (or XSI) with Mental Ray bundled, and it's an engine that is not at all comfortable with a 4GB RAM limit.

The article neatly sums up how to build a render box from about 5 years ago, or for a hobbyist who doesn't really push the hardware.

In the last few years, with the prevalence of displacement mapping and linear workflow, file sizes and memory usage to get renders at the quality folks expect of CG work have skyrocketed.

As someone working as a freelance CG/VFX artist, I can tell you a few practical truths:

1. You may not need XP 64 but you need 64-bit if you hope to do high-resolution, or detailed renders in a single pass. An addendum to this is: don't even consider a motherboard that supports less than 8 gigs of ram, and max the thing out. If you are rendering under Windows, you're shooting yourself in the foot if you're stuck on 32-bit, in particular. You will hit a memory wall with a 4gb RAM system very very quickly. Linux 64 is fine. XP 64 (and even my tests with Win7 64 are good). Avoid Vista 64 like the plague.

2. Depending on your primary rendering usage, a Core i7 may actually be working against you with hyperthreading. Quite a few of the big boys (Renderman, Mental Ray) are still licensed per thread. With hyperthreading enabled on the motherboard, an i7 looks like 8 cores to many rendering apps. Relevant example: A dual quad Xeon Mac pro can only use half of the machine's processing power as a Mental Ray satellite node with Maya, because it's licensed to only use 8 threads total. In addition, a lot of compositing apps -- and LOTS of plug-ins -- are single-threaded (I'm looking at you, random After Effects plug-in, and just about any dynamics plug-in for a 3d app). The short of it: if you're going to be rendering with something that's actually capable of saturating a multi-threaded CPU, go for it. But do some research and tests first.

3. You might be able to get away with a crap mainboard video card -- but make sure of it. A few CG apps don't have command-line rendering available, and it'll suck to learn after the fact that the app you're trying to launch on your pile of new 1U servers won't launch because you don't have a decent video card. Linux & Mac OS (even Hackintoshes) are far superior to Windows in this regard -- you'll rarely find an app that refuses to run due to the card. Crap interactivity is fine as long as you can initiate a render.

4. Standardize your render boxes AND WORKSTATIONS on a single platform (ie Linux 64, Win 64, MacOS X 10.5 intel). Lots of apps require shaders to be recompiled per platform, and small studios generally use share/freeware stuff that might not be available on all platforms -- it's much better to work around this issue when you're creating your assets, versus when you've got a delivery deadline looming and you realize that your fancy layered shader looked great on your Win64 previews, but the code isn't available for Linux 64 to render within your lifetime.

Do I get a medal for reading that thing?

At any rate, railing against FTP is kinda quaint seeing as how there are lots and lots of other ways to intercept the data if you've been pwned.

If you've got a keylogger (or registry scraping malware in the case of Win), it doesn't matter if you're got some outlandish quantum encryption link between machines.

The real story here is:

- Wordpress is insecure, news at 11. Lots of injection attacks happen, interestingly they're disproportionately successful on newer versions of Wordpress.
- Substitute "Wordpress" for your favorite off the shelf blog/forum/cms script.
- If you're on a shared hosting plan and one box/instance/etc at the facility has been pwned, it's likely able to capture data going to other machines/VMs on the same subnet, particularly if you're using a ghetto-tastic shared Win server (there are no other kinds... all shared Win-based hosts suck ass on all fronts due to incompetent administration and terrible cpanels).
- If your workstation has been pwned, your FTP passwords are the least of your concerns. Trust me.

I mean, it's nice that the author decided that the world needs a little bit of edumacation, but the big picture is more important than "FTP bad"

To clarify: I'm not talking about using a single sticker to activate a ton of PCs, which is certainly possible under the current OEM activation structure.

To be sure, I have had no moral issues whatsoever pirating Windows in the past, but I consider paying $129-ish per machine to keep version and config parity on my modest home office render farm a bargain in comparison to any alternative (apart from Linux, but we're talking Windows at the moment). I built the machines, and paid to get XP64 OEM for each of them (legitimately under the license terms). I'll be paying to install a Windows 7 OEM on those same Core i7 boxes later this year, and the day that Microsoft refuses activation of an OEM copy on an honest to God homebuild is the day that their platform gets abandoned entirely. An upgrade from XP64 or Vista 64 is most certainly not worth the price from a SOHO point of view when you're dealing with 5-6 machines.

I guess my primary point was that a full, non-upgrade, OEM copy of Windows is both cheaper and more convenient to own in the long run (and even the short term) than an "upgrade" retail box... and the upgrade boxes are retailing for pennies on the dollar less than a full install. There's no compelling reason whatsoever to pay for an "upgrade" box because it's incredibly inconvenient to have to reinstall from one in the long run.

There is no good reason to ever purchase an upgrade copy from Microsoft given pricing, convenience and licensing terms. If your personal moral code objects to sticking an OEM copy of Windows (or education copy for even cheaper) on a machine that isn't technically brand-spanking-new, then fine... but for God's sake don't buy the upgrade copy. Just spring for the full retail install.

You save about $20 off retail (which costs twice as much or more than OEM) to buy yourself about 3 additional hours on every reinstall, and that's the part that chafes me. Or you can buy the OEM copy that's far cheaper and is the exact same as the retail box, minus superfluous packaging and which serial number it accepts.

Until it's as convenient to be 100% EULA-compliant as it is to fudge a little on the OEM terms I'm gonna continue saving money at upgrade time and not lose any sleep over it.

So, Microsoft: make upgrade boxes less of a pain in the ass over the long term -- or make the price on par with the additional hassle -- and I'll consider doing things your way. I don't trust you, I don't respect you, but I'm stuck with you for certain apps. You'd do well to learn a little about customer loyalty from Apple.

But in reality, I buy an OEM copy of Windows Ultimate Whatever from Newegg for $129. I don't have to deal with the utterly retarded upgrade process every time I have to nuke & pave, and I've got an ugly little sticker to refer to when nuke & pave time rolls around.

You're assuming I give two shits about honoring the finer points of Microsoft's licensing, which I don't. Is MS going to come after me? Are they going to deactivate my Windows randomly? They deactivate retail copies randomly.

To be honest, It's more convenient for me to get a legit serial number that doesn't self-destruct than to deal with suspect WGA patches & cracks that work like an arms race and require constant vigilance.

As long as you don't reinstall more often than quarterly, activation goes through without the need for a dreaded phone call. In the case that it fails, I make the phone call and say (and I quote): "I had to replace the motherboard" and get an activation key in about five minutes. If you do this once a week, the phone drones sound vaguely annoyed with you, but you still end up with the number.

So, really, what's the downside here (apart from paying for it at all)? I'm curious.

In a nod to the global economic downturn, it is interesting to note that upgrade prices are still more expensive than a non-upgrade OEM copy with far more reinstallation hassles.

Oy, I hit submit before I added all the confirmed films:

The Bear and the Bow (2011)

Newt (2012)

Also worth noting is that the last I checked, Andrew Stanton was attached to John Carter of Mars, however it wasn't confirmed that Pixar/Disney would be distributing. There has been conflicting info on the matter, and it's ambiguous at the moment.

Both incorrect itself (or couldn't even be bothered with IMDB) and its assumptions are misquoted blogspam.

So, let's see, confirmed on Pixar's future agenda (as we know now);

Toy Story 3 (2010)

John Carter of Mars (2012)

1906

Plus speculation in Variety from several days ago about Monsters, Inc 2 possibly being Docter's next film that has suffered a little in the blogspam reporting (ie accuracy), resulting in the OMG SEQUALZ?!? meme we're soaking in today...

Also speculation: various rumored Mater spin-off movies from Cars. Yes, Larry the Cable Guy might get his own... vehicle (ouch). God help us all, but it'd be a goldmine.

One more note, Netalyzer sees my upstream at 6.5 megabits and downstream at 15 megabits -- which means that Netalyzer's traffic is being shaped by Comcast to give better appearance than reality (same deal with almost all of the "speed test" sites out there).

I guarantee you in Jacksonville, FL that via FTP, SMTP, AFP, WebDAV or BitTorrent you will never see upstream speeds faster than 45k / second after an initial 3 to 5 second burst, no matter what you might think you're paying for.

They're not redirecting DNS in my area of North Florida, but

Apart from their God-awful downtime (about an hour a day at around 3am EST)... ...and 1-hour almost instant disconnect if you're participating in a torrent they've flagged as unacceptable... ...and terrible upstream speeds (about 45k / sec after the first 3 second burst)... ...and random massive latency... ...and questionable traffic shaping... ...and "not really" unlimited internet...

They're ok-ish. Apart from being FUCKING EVIL. That said, the local cartel apparently hasn't gotten the same memo that caused TFA's seizure.

Ok, they suck compared to, say, Speakeasy in the old days, but AT&T hasn't upgraded infrastructure in my neighborhood to support DSL, so Comcast is quite literally the only game in town. Yeah, I'm 5 miles outside of downtown and I can't get DSL here because up until a few years ago only poor folk lived in these old houses and it wasn't worth the time. Same reason there's no cable underground in Jacksonville's downtown... Cox cable (at the time) decided only poor folks lived there in the 70s when they last dug up the streets.

Anyhow, apart from blocking non-comcast SMTP, here's all Netalyzer anomalies:

RPC (Port 135) blocked
NetBIOS (Port 139) blocked
SMB (Port 445) blocked
DNS resolver (Comcast DNS): 1700ms (!!!)

Nothing I'd flag as unacceptable apart from the DNS latency. I learned to get my own SMTP host on an alternate port years ago as blocking port 25 is standard procedure on most ISPs.

Controversy is a matter of taste.

If you don't want your kids playing GTA or playing pseudo-realistic war sims, don't buy 'em. Don't play 'em. But don't try and protect me from them either.

I never really understood, and I'm not sure I will ever understand, what makes some people take up a crusade expressly to abolish ideas that they find offensive that they could just avoid, in turn exposing themselves to a constant stream of something that they obviously can't stand.

Books, games, metal, hip-hop, homosexuality, religion, porn, weed... hell, even Macs. The list goes on and on. Almost all of of the hot buttons I can think of are often central to a person's identity.

Stop telling me how to live my life and get on with your own. I may not agree with how you choose to live your life, but I'll be damned if you make my moral choices for me.

Have your own kids, shield them if you must, and get back to me in 16 years with how well that turns out.

Think of your own damned children.

With the new regime at MS this last year or so came new advertising/marketing & PR partnerships. Aside from the occasional WTF (Seinfeld?), they've been doing a pretty good job as a whole.

As someone who was in the ad/pr industry for quite a long time I can tell you that:

1. The date has "leaked" reliably pretty much once a week on all the betas to date. Nothing's "leaking". They're disseminating the info virally to build buzz. It works, and that's ok.

2. Win 7 needs as much positive spin as it can get to offset the Vista catastrophe. The february beta was more stable and bug-free than Vista SP1... and to coin a phrase "it's Vista without the suck." They need to get the word out there, to as many folks as possible. For Windows, it's not bad at all, and it's a massive improvement over Vista even if they share 80% of their DNA. Well, aside from the start menu still requiring Vista's 50 clicks to get to the app you want due to the teeny-tiny scrolling programs folder list. I don't like some of the interface Nazi choices that they're making with no user overrides available (start menu, ribbon).

Look, I've tried the public beta back in Feb, and I'm looking forward to putting RC1 on a couple light use 3D workstations. There's nothing inherently wrong with the XP64 that's on 'em, excepting that fewer and fewer 64-bit apps... like say MacDrive... run against XP64 (just Vista.. which is a naggy, broken clusterfuck).

I'm happiest on my primary workstation (which is a Mac) and my laptop (also a Mac), but I've got memory & processor intensive CG apps I run that require Windows 64. Some require Linux 64. Diversity is good. Rendering throughput with Win7 beta (Maya/mental ray) was nearly 10% higher than XP64 and on par with Linux 64's render times... just easier to roll out and configure on a bunch of render slaves with random hardware profiles (ie whatever I've got on hand when I need the horsepower).

Anything that makes Windows suck less is fine by me, and getting a viable 64-bit Win OS in my hands before I'm unable to buy OEM XP64 copies anymore is a priority. Having RC1 not expire until mid 2010 is a bonus. That means I can use it in light production as a render box or secondary workstation now instead of a nuke-every-few-weeks sandbox.