Having to optimise for three very different microarchitectures with the G3 (short narrow pipeline, no AltiVec, small caches), G4 (short wide pipeline, focus on in-order AltiVec, useful OoO otherwise, large L2 yet memory bandwidth starved), and G5 (long and wide pipeline, focus on super-scalar OoO, AltiVec just glued on, more memory bandwidth) must have been "fun".
How many variants of the codecs did you have to implement to make it work?
And Intel! We shipped QuickTime for windows, and then later launched intel-based macs. That was a lot of work to optimize for too! Lots of nights and weekends porting and optimizing for little-endian byte order and a completely different simd instruction set. Porting QT from OS9 to OS X was another major transition. It was fun though :)
"You've reached your quota. Please hold your credit card or mobile phone on the card reader within the next 10 seconds or you'll be liable for the resulting crash."
Best of luck getting a good deal for new hardware right now from anyone right now. All hardware pricing negotiations these days start with give us your company credit card, drop your pants and bend over the table.
They also fucked up their parity RAID repair so that the next disk failure on a different disk will destroy the data, argued that the pathological B-tree performance reported by a user couldn't be real, because they didn't understood the tree depth would only be logarithmic to the base of the fanout if the entries are the same size. insert shocked pikachu face
No reasonable person has ever argued that a consumer buying a (digital) copy of a game obtains the exclusive rights to the game. This is such a cheap embarrassingly stupid attempt to come up with a straw man.
I'll listen to Sony management and lawyers whining about copyright after they paid the damages and fines and get out of jail for every rootkit they deployed. Should be any century now.
A CDN *cache* server is a special case. Netflix cache appliances can accept the risk of running FreeBSD -CURRENT and upgrading half their fleet to the latest snapshot every ~2 weeks and we thank them for battle testing FreeBSD's active development branch in production. It really helps to reveal regressions (both correctness and performance) early in the subsystems and drivers that matter to their usecase.
Most users will neither be willing nor able to accept the trade-offs that Netflix chose.
You're just wrong. FreeBSD stable branches are the development branches from which new minor releases (with a stable ABI) are forked. If you want to be pedantic you want to follow the releng branches for most production deployments (release + security and non-security errata patches). Unless you build from source yourself you the tools (pkgbase, freebsd-update) don't make that distinction visible to the user.
How many variants of the codecs did you have to implement to make it work?
reply