Comment Re:Hibernation (Score 1) 77
Perhaps it is!
"and sent a radio confirmation that it had successfully turned itself back on one and a half hours later"
Now we know where that gap in time came from.
Perhaps it is!
"and sent a radio confirmation that it had successfully turned itself back on one and a half hours later"
Now we know where that gap in time came from.
In other news: construction workers building and maintaining city streets and highways are now held responsible for high speed chases.
If we're to believe Betteridge's law this time around... we're to believe that both Chernobyl is safe AND 60 Minutes didn't push propaganda!? NNNNOOOOO, I'M SO CONFUSED! I DON'T KNOW WHAT TO DO!
And IOS is the operating system powering Cisco routers.
"It's bulky. It can be forgotten, or lost"
My wallet is on a chain which links to my belt loop on my pants. My wallet will not be lost. However, my phone doesn't have this same protection.
And seriously, how is a phone any less likely to be lost than a wallet? One of the two is out and about of the pocket a hell of a lot more often than the other.
Get a less noisy system. How hard is that to figure out?
Get a case that has one or two 120mm or larger fans for airflow. They generate much MUCH less noise than 80mm fans and still push enough air to keep the thing chilled.
Switch CPU/GPU fans to ones that only turn on when needed, and are off while the system is at a cool idle temp.
Switch your HDD out for an SSD, and use network storage for your bulk storage. Gigabit Ethernet is ~100MB/sec and so is a rotational disk, so you're not gonna see much different in performance here (assuming your network doesn't suck)
And to go beyond my computing age, let's have something a little older: http://en.wikipedia.org/wiki/B...
"Heartbleed set the trend early this year"
Wait, this is NEW!? http://en.wikipedia.org/wiki/B...
Compiled JavaScript, you say? http://en.wikipedia.org/wiki/V...
No matter how much effort goes into securing the transport layer, it means absolutely nothing if the end nodes themselves are insecure. Something as simple as a SQL injection or remote code execution could easily deanonymize an end node. With how quickly many of those sites sprung up, one of the current theories is lack of security on the end-points themselves is what was attacked, not the Tor network itself.
Since I was able to get off a wise ass crack joke for a first post, let me follow it up with something actually insightful for you other readers out there.
What makes a "good" or "bad" boss anyways? Well, this article is one that I've always lived by, and it explains things quite well for both us techies and for those who are not of the tech mindset and skill set.
NO SHIT. We needed a paper to tell us what we already knew? Damn, why didn't I write that paper... Here goes.
"INCOMPETENT BOSSES ARE THE LEADING CAUSE OF CAPSLOCK RAGE ON THE INTERNET"
While I'm sitting here reading about other people bitching about abstraction libraries such as jQuery, my first thought was actually about testing processes.
Pretty much everywhere I look online, projects are FLOODED with automated testing tools to ensure their code works. And sure enough, every bug that I submit has an "automated test" that didn't test that particular condition. Developers are relying more upon these testing tools and less upon actually USING their own services they're developing to ensure they work properly.
A great example: a recent bug I had to file was brain dead simple. File opening ignored current working directory, so if you changed directories, the file open command would still assume you're in the base directory. Why wasn't this caught? All of their file handling automated testing routines ONLY checked absolute paths, none checked relative paths. On top of that, when they finally did add relative path testing after my bug report, they only added it as relative to the base path, and not testing against current working directory.
Now, let's think about this for a second. How long has the concept of changing directories been around? While most of us will go "oh, DUH!" to the bug mentioned above, newer developers may simply not be in that same mindset, because they're not actively traversing their filesystems themselves. The automated toolkits are doing all that work for them, leaving the developers less experienced in this area, and thus less forethought when building the next generation of tools to test these exact sorts of issues. It is a downward spiral.
Yes, because this is SUCH a problem on sites like Twitter... where if a user feels a particular account is flooding their feed too much, they are just a click or two away from an "unfollow" button.
I don't need a computer telling me that I've had too much information and to restrict how often new content can appear on my feed, I'm quite capable of doing this myself!
Progressive technological evolution, adding a new finger every year!
Kleeneness is next to Godelness.
