Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Comment: Re:So basically we're living in the best timeline? (Score 1) 126

by OverlordQ (#49699417) Attached to: How SpaceX and the Quest For Mars Almost Sunk Tesla Motors

At 7KWh, the battery really wont do anything except for the occassional brown/blackout and really how often does that last. if you dont have solar, there's absolute no point in getting one of these. And if you do have solar it'll just make the payoff slightly better. It'll still take you 3-5 years to pay off the powerwall for little to no gain.

Comment: Re:Assumptions (Score 4, Interesting) 78

by OverlordQ (#49604415) Attached to: Hacking the US Prescription System

> I think it is far more likely that the pharmacy sells this information to insurance, pharmaceutical, and marketing companies.

This. Pretty much every prescription the doctor writes effectively goes straight to the drug reps. If you stop prescribing, they'll know, and come in and bribe^H^H^H^Hinquire as to why you stopped prescribing their drug.

Comment: Re:Check their work or check the summary? (Score 4, Informative) 486

by OverlordQ (#49338341) Attached to: No, It's Not Always Quicker To Do Things In Memory

THATS THE ENTIRE POINT OF THIS PAPER.

It is easy to explain the results: In high-level languages such as Java and Python, a seemingly benign
statement such as concatString += addString may actually involve executing many extra cycles behind
the scenes. To concatenate two strings in a language such as C, if there is not enough space to expand
the concatString to the size it needs to be to hold the additional bytes from addString, then the
developer has to explicitly allocate new space with enough storage for the sum of the sizes of the two
strings and copy concatString to the new location, and then finally perform the concatenation. In Java
and Python strings are immutable, and any assignment will result in the creation of a new object and
possibly copy operations, hence the overhead of the string operations. The disk-only code, although
apparently writing to the disk excessively, is only triggering an actual write when operating system
buffers are full. In other words, the operating system already lessons disk access times. A developer
familiar with the language and system internals readily notices the causes of this observed behaviour,
but this behaviour may be easily missed, as indicated by examining similar cases in production code.

Dead? No excuse for laying off work.

Working...