atomic_cheese
Re:Learning from Tay’s introduction
on Friday March 25, 2016 @08:29PM (#11363785)
I was more impressed that it lasted an entire 24 hours. They're exposing it to the festering cesspool of Twitter, and it holds out for an entire day? That speaks to the quality of their anti-abuse measures more than anything else.
Re:$99 Mineserver: The Devil Is in the Details
on Friday March 18, 2016 @08:53PM (#11316579)
Based on the rest of the post, I think that hope might be unrealistic.
Re:Why Messaging Startup Slack Keeps Raising Money It Doesn’t Need
on Wednesday March 16, 2016 @07:59PM (#11301647)
C++ to JS is a pretty huge jump. C++ -> Java -> JS might work better.
Re:Man moves individual fingers on prosthetic arm using only his thoughts
on Wednesday March 02, 2016 @07:39PM (#11214262)
Absolutely. I can't speak for anyone else, but I'd happily switch to a GiTS-style full-body prosthetic if they were available.
Re:The Unbearable Asymmetry of Bullshit
on Monday February 29, 2016 @02:09PM (#11197434)
If you can't blind them with brilliance, baffle them with bullshit.
Re:Leading Android scientific calculator now requires Caller ID
on Tuesday February 16, 2016 @01:56PM (#11112218)
RealCalc is my favorite. It supports RPN and doesn't require any permissions other than storage.
Re:Google is banning Flash from its display ads
on Wednesday February 10, 2016 @08:36PM (#11077671)
If you use Livestreamer and an IRC client, you can run Twitch streams outside your browser. That's what I've been doing - I haven't had flash installed since that cross-platform RCE bug late last year.
Re:Ignition: An Informal History of Liquid Rocket Propellants (1972) [...
on Sunday December 06, 2015 @12:25AM (#10684480)
I managed to find a PDF copy a while back, and if I can ever find a physical copy that's not incredibly expensive I'd certainly buy it.
Re:You Can Do Any Kind of Atomic Read-Modify-Write Operation
on Thursday October 08, 2015 @02:39PM (#10355011)
I'm pretty sure that example is actually fine - if there's a concurrent writer, the modified value will be loaded into oldValue. Repeating shared.load is unnecessary since that operation occurs as part of compare_exchange_weak.