If you end up staring at a computer screen late into the night like I do, the light may be disrupting your circadian rhythms. Theres a utility called Flux (http://www.stereopsis.com/flux/) which adjusts the brightness and color of your screen depending on the time of day to make it less disruptive. I've found it to be helpful in getting me feeling sleepy earlier.
With the Radeon 5000 family of GPUs AMD really did well for themselves. Nvidia didn't have an answer for that until they delivered Fermi 6 months later. And what you say about Intel's GPUs is true, they are pretty much useless for any sort of advanced 3d graphics.
* Has a lot of bugs, inconsistencies and crashes. (poor technical design) * Doesn't truly solve the problems it is marketed to. (inadequate research) * Is hard to adapt and extend for custom business processes. * In some cases adds additional work for people with very little benefit. (poor integration)
Some goals for good enterprise software:
* Observe what people are trying to accomplish with their workflows, design the software to save time.
* Use modern software engineering practices, have UX designers, do automated testing, do automated crash reporting and updates, crashes are really frustrating to end-users
* Make it easy for IT to maintain, these people are already busy and you don't want them to get a bad impression of your software because its complex or fragile, again save time
Perhaps because V8's engine translates directly from code to assembly with no intermediate bytecode. It seems like it would make it more difficult to integrate tracing with that system.
Having an intermediate bytecode also makes it easier to support more architectures in a reasonably consistent manner: for architectures where you don't have a bytecode->asm compiler, you can fall back on interpreting the bytecode (as TraceMonkey currently does).
With V8, the direct targeting of architecture-specific asm means you have no support at all on architectures that V8 doesn't yet target--- or you'd have to support them through a different Javascript stack entirely, like falling back to TraceMonkey, which would be harder to keep consistent.
Of course, Mozilla could go the Chrome route and drop support for everything except x86, x86-64, and ARM. But for the moment at least, they appear interested in keeping at least the Linux version available on PowerPC, SPARC, and other architectures.
As they should. Since there is no way to verify the remote server then the connection is vulnerable to man-in-the-middle attacks. In that situation an attacker can simply pretend to be the server and decrypt your traffic.
The human body is not 100% efficient. The efficiency of a human body can change. The amount of Kcal in a food item measured in a lab is not necessarily going to be the same amount a human absorbs.
