Recent submissions

Comment · 11 years ago
Reader mode was present in the Mobile version for a long time, it's port to the desktop Firefox happened recently AFAIK.
Comment · 11 years ago
Kinda makes sense, as all ads are suspicious at the bare minimum.
Comment · 11 years ago
I believe I saw more IE6 users in the last year than drivers with 50+ year old cars.
Comment · 11 years ago
"Defaulting on all Euro debts, exiting Europe, bankrupting the banks, issuing a new currency is a viable solution. Yes it's a horrible hang over to live through but it means removing the horrendous debt burden for the next 50 years."

If they do not tend the root of the problems, they might as well do this every 50 years. Things like 14th month payments (while it was a thing) or tax evasions that could reach industrial levels on their own will make things hard, even without the IMF or EU interfering.

Comment · 11 years ago
Comment · 11 years ago
Also note the dates: Tomb Raider's TressFX happened in 2013 while Crysis 2 and the 'flat-surface tessellation' happened in 2011 (with Patch 1.8 I believe).

Not something one can call a start.

Comment · 11 years ago
"Solution: AMD optimizes HairWorks."

How do you optimize code you have no access to?

"It's just an extension of the systemic AMD problem: they [very likely] have the best hardware but their Windows drivers are horrific and not only do they not have developer support; they actually play the victim because others take the initiative."

Like how a Project Cars developer or spokesman claimed that AMD did not help for months only to be completely disputed later on? Also, ask Kepler owners about their current driver support in recent titles. They are not happy.

"NVIDIA set out to optimize the game as best as they could for their hardware."

AMD helped optimise several titles that worked just as well on NVidia (excep that one Tomb Raider fiasco, what was solvable doe to the openly available TressFX code. Can we say the same about hairworks?). But somehow many NVidia titles are optimised in a fancy way that always hits hard on AMD cards (Crisis 2 and Batman AA come in as uncovered examples).

"AMD didn't set out to do anything: once again they sabotaged themselves by not getting involved."

I guess you can back up that statement.

Edit: wording, grammar

Comment · 11 years ago
That is true, but I like to believe that if a group can solve a whole class of problems with a new language, that means they can spend more time and effort on other types of security problems.
Comment · 11 years ago
I wonder what would happen if a certain "Poachers' testicles are the best aphrodisiacs." rumour were to spread...
Comment · 11 years ago
Those must be some strong magnets, effecting people even before getting under it's effects!
Comment · 11 years ago
As I know, it went something like this:

-Both wanted x86 for better usability (PS3 Cell was a hard-to-tame beast for many devs, ARM not strong enough)

-Intel was not interested in manufacturing semi-custom chips

-Nvidia simply did not have x86 licenses

-AMD was left as the only option

Of course other things also factored in the big picture, profit margins for example, but those are more known.

Comment · 11 years ago
Well, this was not the first time they adopted something early and left most of the world behind: widespread adaptation of the ogm then the mkv containers, followed by the complete swap to h264 over XviD, and I believe the abandoning of "must fit either onto a CD or DVD exactly" ripping and encoding rule was also a first.
Comment · 11 years ago
Comment · 11 years ago
One of the few reasons why I prefer GOG.com over Steam.
Comment · 11 years ago
This sounds more like "Mantle 1.0 will have a lot in common with DX12 and glNext, but expect even more from the later 1.X versions."

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton