Premature optimization does not refer to hacked sloppy solutions as much as it does illegible and neglible counter intuitive code practices that account for little to no gain. You should only be trying to squeeze out fewer microseconds when the program calls for it. It is a widely known rule of thumb to first right things clearly and perhaps even naively, profile and then optimize when the performance is not within acceptable range.
Spit out plain and simple bribed legislation I don't know what does.
Tape has always been a increasingly attractive solution to my backup needs, and certainly better than bdrs. However until I am in a scenario where I need to perform a full restoration from tape I will wait this one out. Backup zpools and simple rsyncs I have done but dealing with all the potential mechanical and electromagnetic mishaps of tapes I have no experience with. I have read some of the main criticisms of that backup media are the failures during the reads and writes.
Pretty sure this is the debian bug where the relevant packages for whatever reason decided to use a static number for the rng seed. There is an xkcd which pokes fun at this.
as most of OS X's core functionality is open source. It's possible for them to hide something in the quartz engine or something, but backdoors in the open source code would have to make it make it past many more eyeballs. The OpenBSD incident of a supposed "backdoor" (can't remember if it was actually verified or not) wasn't a backdoor but simply a purposeful vulnerability to a side channel attack.
a name of an already popular open source application: http://audacious-media-player.org/
This is almost as bad as the libtorrent and libTorrent fiasco.
As a mac user, I disagree with this. Apple added in a quick search feature into osx not so long ago, and I use it all the time. There's a big difference between typing a precise command into a terminal, and simply typing a few letters from an app name and hitting return as soon as you see the icon pop up. Apple has always been ahead of the game on search. You can search from basically any file browser, including when you're opening a file. Unity has its problems, but I suspect that as time goes on you'll learn to love this feature.
You mean like tab completion?
There is a reason that most people disable compositing for their window manager.
A stripe would be glorious from a performance perspective. It would only take a few to saturate the bus to the CPU.
The data in csi is not obfuscated it's missing. This algorithm reverses motion blur it does not bump up any resolution, these are two completely different things.
Heh slow raid controllers at that
Having lived with the openmoko as my only phone for nearly three years I can safely say the novelty of a community developed ui with barely functioning code for basic tasks wears off quickly. SHR was terrible to live with along with every other distribution
Agreed this article just comes off as ignorant. IO is hardly a bottleneck these days
This seems to rely on the fact that the user would have a working mail transfer agent setup on their system. This is a rarity, however. I happen to have mailx configured with sendmail to use an SMTP smart host, however most people probably do not.
The 3rd version of the kindle natively interprets the PDF format and displays it exactly as it is supposed to be for both raster and vector content. The problem is the PDF as a whole is rendered typically to be 8.5x11 while the kindle is a 6ish inch display. So in order to read any individual part you have to zoom in on that subsection. It's kind of annoying but in my opinion the trade-off for an extremely readable display is worth the occasional annoyance. I currently have bought Brendan Gregg's Dtrace book for the kindle and it's extremely readable. When an author is willing to put the time and effort forth to produce a kindle capable document, it works (and it works for all types of books, including textbooks).
Thus spake the master programmer: "After three days without programming, life becomes meaningless." -- Geoffrey James, "The Tao of Programming"
