Fans running at 100% all the time? Call Applecare.
Superdrive making a motorboat sound? Call Applecare.
Batman AA crashes? Call Applecare.
Keyframe animation borked in Finalcut? Call Applecare
Font have a kerning issue? Call Applecare
I find the majority of Mac-whine-blogs out there are customers that have recently migrated from the PC world, and do not yet have an understanding of how the Apple support model works. This is not to say that their issues don't exist or are invalid, but that that are choosing to whine rather than accept the assistance that they paid for.
Direct link special for you.
First post:Latest post:Quote:
I have problem with wake up from sleep.
when i just use my mac, it works normaly
but after wake from sleep, graphic performance
down to about half.
for example i got 70 fps around. in WOW.
after wake, it drops to 20 fps around.
Cinebench 11.5 shows 16fps after wake.
but 30 fps from first reboot condition.
Mac is 2008 2.8 octacore with Radeon 5770
lion looks heavy than SL. more heavy feeling to
click something. it reacting bit slowly than SL
and this made feel heavy. please fix this problems.
No, Apple support is doesn't work as you think.Quote:
A year later, 10.7.4, and this is still an issue. Seriously Apple?
Put bluntly, Nvidia makes semi-decent hardware. The performance per watt ratio is generally awful, and the feature per die space ratio also leaves something to be desired when compared to competitor products from XGI, ATi, ATi/AMD, Via/S3, SiS, Matrox, PowerVR, Trident, Intel, and even going back to 3DFX.
Pub bluntly, Nvidia makes awful drivers and software development kits.
Nvidia loves to leverage proprietary OpenGL calls, the most famous possibly being UltraShadow as used in the IDTech3 engine. Nvidia's love of non-standard graphics calls were one of the reasons City of Heroes never ran right on AMD/ATi graphics cards. People on the CoH forums loved to complain that the problem was the ATi/AMD drivers... but ATi/AMD was not the culprit. Nvidia's deliberate code level sabotage was the culprit.
Nvidia loves proprietary / non-free development. We've already heard about the business contracts lost because Nvidia has no open-source strategy. Yes, let us be clear here, Nvidia-GLX is not an open-source strategy. Nvidia has already been called out by the /Linux kernel developers and the Linux Foundation... and managed to get itself branded as the worst company the Linux Foundation had ever worked with; including a very explicit "Fuck You" from Linus T. himself.
* * *
What Nvidia does have... is marketshare: http://store.steampowered.com/hwsurvey/
As of June 2102 Nvidia based cards make up over 47% of the graphics cards used by those participating in the Steam Survey.
Nvidia tends to wield this marketshare like a club, using it to force developers to use Nvidia SDK's and Nvidia products when developing commercial games. The result is the code-level sabotage in recent games like Batman: Arkham Asylum and Arkham City.
The result is a Microsoft-like cycle. People buy Nvidia cards because Nvidia has marketshare and that marketshare results in software that is written to perform better on Nvidia hardware: Which fuels the marketshare.
By the same token. People who use Nvidia cards on /Linux do not do so because they support /Linux development or open-source ideals... and if you say do ... you do not. End of Story. Can it Deary.
To be blunt, if you support /Linux development or open-source ideals, you would not be using Nvidia cards at all. You would be using either Intel or AMD cards on x86-platforms.
Developers who implement software applications that make calls to Nvidia API's generally do so because, again, Marketshare.
* * *
Admittedly both Microsoft and Khronos have taken steps to reign in Nvidia's shenanigans. DirectX 11, OpenGL 3.x, and OpenGL 4.x have stricter definitions for supported calls, as well as supporting more functions in the core specification. Standards like OpenGL ES 2.0 and ES 3.0 truncate the list of API supported calls even further, giving less room for proprietary problems.
Admittedly Nvidia has also been quicker to adopt new protocols or functions compared to Intel or AMD. VDPAU is a very good example of this. Nvidia had their API out and ready for usage... and leveraged marketshare like a club. So, instead of having a universal standard for Video Acceleration API's... we have a proprietary standard being resold as an open-standard.
Admittedly AMD and Intel have been slow to react to other advances in the open-source market. Case in point would be Kwin+OpenGL on AMD hardware: http://blog.martin-graesslin.com/blo...gacy-hardware/
* * *
However, these last two situations are slowly being addressed. AMD and Intel have an open-source strategy and are carrying their strategies out by fixing problems, getting appropriate specifications released under Open-Licenses, and generally being good Open-Source citizens.
Oh, and just BTW, the first link on google is this: http://www.filestube.com/p/planet+ea...80p+sample+mkv <- like I said, I'm not gonna trawl through cyberlocker indexers, just because *you* are afraid that I'll *again* prove you wrong.
You funny guy indeed. Good luck in your fighting with fear of links and trollphobia.
Why should you care about correct drivers? Specifications are there for a reason: to allow any company to bring their goods to the table and let customers sort things out. Clean competition is a Good Thing (tm).