Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Comment Re:AKA the I HATE AMERICA ACT (Score 0) 358

Newer phones like the Galaxy Note 3 have a USB 3 micro connecter that supports charging with a USB 2 cable. So, make the standard USB3, and smart manufacturers will do it right.
Actually, I won't buy a phone that doesn't have a pretty standard charging port. The market tends to do a better job at sorting these things out in the long run, but codifying a standard like this into law feels too inflexible.

Comment Re:Assumptions... (Score 1) 173

This also assumes that a person wanting to make a purchase on Amazon will not just wait an hour for Amazon to come back up, and will instead make the purchase elsewhere. In some cases that's probably true, but if it were me I'd probably just try again when Amazon came back up. I shop at Amazon out of laziness as much as anything else.

Comment Re:Correction (Score 2) 291

Disagree. Nobody is saying that their piracy "causes" them to pay for more media. However, regardless of the causal relationship, this correlation serves as refutation of the image of a pirate as a freeloading, non-contributing jerk. Statistically, they are buying things. In fact, more than the average person.

Comment Re:As little as practically possible (Score 4, Insightful) 225

"You're assuming that performance -- or, more precisely, CPU usage -- is important; in many cases, reliability (and being able to track down bugs after a crash) are far more important than CPU usage."

I work on a real-time embedded medical device, where both performance and reliability are vital. We've got constrained resources, and the system must be extremely responsive.

Our logging scheme is pretty cool. It's written so that two computers can log to a single hard drive, and each logging statement must define a log level. So, for example, if I'm writing GUI code, I can log to log_level_gui_info, log_level_gui_debug, log_level_gui_error, or any of a number of more specific log levels.

The idea is

  1. Some of these log levels we can turn off before a production release.
  2. We have a special tool for reading these logs (they're encrypted), and in this tool you can check off which log levels you care to see, and which you don't

So, we have two ways to filter out extraneous logging that we don't care about (one actually keeps the logging from happening, and one just filters it out during analysis), and we can log as freely as we like as long as we're smart about which levels we're using.

As much faith as we all have in our own code, nothing's as frustrating as trying to analyze a log that came in from the field where there's just no information about what went wrong.

FORTUNE'S FUN FACTS TO KNOW AND TELL: A firefly is not a fly, but a beetle.