AMD64 would bring more cache pressure on the CPU, but also a lot more memory for caching the world, plus more registers, a better instruction set… For a game, I expect memory would make a large difference.
You give examples of blobs, not DRM. Unless you are referring to the direct rendering manager, I have not encountered any DRM in years of using Linux on the desktop.
Sensors could manage with some sort of interferometry to rebuild an image from multiple pixels across multiple sensors. The signal processing would be similar to what is used for medical scanners. We could also see a convergence with radar, combining those pixels and algorithms with an active source.
MySQL's warnings are silent, in the sense that the web application will never act on them. Guessing instead of failing early is a poor choice for a relational database, and is only explained by MySQL favouring ease of use and porting over data integrity.
It still implies the Direct3D implementation stayed at 270fps. I wonder how Windows+OpenGL fared before the optimisations; presumably it was lower than 270 or OpenGL would have been the baseline.
The way US politicians are funded, they do not give a shit about this hypothetical lone inventor. This is just a romantic ideal used by the pro-patent lobby to glamorise patents.
PostgreSQL is extensible enough that runtime specialisation would be best, I think. A JIT compiler, or a compiled type-safe multi-stage[1] programming language like MetaOCaml, would give the best performance.
Shouldn't this loophole be closed? Something like: only allow the exclusive owner of a patent to sue potential infringers. That isn't enough to make shell companies a losing proposition, though, because they still contain the risk of losing a suit. I prefer the bond idea, it is a simple and more direct route to making NPEs liable for their actions.
You still need the graph to run the recommender. This algorithm would help new users get up to speed quickly, with better results when the social graph is large; it's just another network effect.
The data was bundled with the domain sale, thankfully. It's a shitty move that they took it offline for an unspecified duration, and that they don't plan to handle existing urls.
Then his stated goals shouldn't prevent people making conversions to other formats. You just have to be careful with not misrepresenting the work, something that is already part of the non-transferable author rights in a few countries.
You asked a very laden question. You have no doubt encountered discussions about full-disclosure to know the arguments against it; giving a one-sided rehash of that topic is a provocative way to invoke an old and tired discussion.
Google and Mozilla will certainly add it to their plugin blacklists. Trojan capabilities remote-controlled through a browser, that's a very serious security risk to their users.
Yeah, but that's proxy, not reverse proxy. It's possible to do something fiddler-like using apache or nginx to mitm oneself and dump everything that goes through.
It's easy enough to generate a snakeoil cert and use its public part as your cert bundle. On Debian/Ubuntu, just install the ssl-cert package, and point to /etc/ssl/certs/ssl-cert-snakeoil.pem as your certificate bundle; the private key is at /etc/ssl/private/ssl-cert-snakeoil.key .
Or just serve your app/API/etc from different urls, plain HTTP for development and HTTPS for preprod and production.
In Python, a sufficiently recent httplib2 will require valid certificates by default; same with the requests library. Both let you use your own cert bundle, as a quick-and-dirty way to do certificate pinning. That's reason enough to discourage the use of Python's standard library for http requests (another reason is that it's quite low-level).
I love it, because it feels streamlined and gets out of the way. I don't really care to participate in flames (the sort that Benjamin linked from his blog post), so I'll just voice some support here.
I'm used to multiple desktops (gnome 3, gnome before that), and multiple panels turn out to be useless to me. I just can't spread my attention across two monitors, whereas I switch desktops without thinking about it.
Indeed, I complained about it as well. It's annoying because I can't download the tracks in order and play them immediately after buying. Plus it's a noob error that most decent trackers will warn you against, and it was in fact faster for me to grab the albums I wanted from one such tracker.
This stuff is used within silos (Watson, bio/medicine research), but expanding it to the web is hard because entities that collect data want to monetise it, and do not see the value in reducing friction.
“don't take too much financing” is a recognition that Digg v4's failure (and you should look at Alexa graphs to see how significant that was) was due to ignoring the community to give investors the site they thought they wanted.