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


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: it's hard to find trustworthy reviewers these days (Score 1) 120

by sshir (#48943651) Attached to: Wi-Fi Issues Continue For OS X Users Despite Updates
I think Apple's unwillingness to admit their bugs, dishonest reviewers and apple's fanboys happily squashing all discontent on message boards etc. combined creating a situation when people simply refuse to upgrade/patch their apple gear.

I mean look, when I first upgraded my perfectly nice iPad Air to iOS 8, it's Wi-Fi become practically unusable (had to reconnect every 5 minutes). Rendering iPad useless for several weeks. And it's not like I didn't check online reviews beforehand... None of them (sellouts!) mentioned this shit. Only _after_ I knew what's wrong with the update I was able to find those huge message board threads full of pissed-off users wenting.

Now, with the new update for iOS 8 I'm sitting this one out. Or at least waiting until other people upgraded and google got the message indexed so I can find it...

Comment: Re:Won't work (Score 1) 426

by sshir (#48796273) Attached to: Chevrolet Unveils 200-Mile Bolt EV At Detroit Auto Show
Interesting. But (I'm not an expert though) it might be that one cannot mothball those things for very long - you pump it or you lose it.

Additionally, even if it does not work for already producing assets, it as sure as hell will clamp down on new investments. And, maybe, that is just good enough of an outcome.

Comment: Re:excellent (Score 1) 226

by sshir (#48722473) Attached to: Red Hat Engineer Improves Math Performance of Glibc
WTF?! We're talking about general recursion, not some stupid, easily avoidable cases. Even in the case of qsort - you need to make 2 (not one) recursive calls one for left and one for right, and you need to keep the midpoint somewhere on the stack... Basically it's easier to roll your own, totally heap based accounting than try to be clever with stack frames. Plus GP explicitly said that there is recursion and your c compiler does not do tail recursion anyway (or you can't count on it)

Comment: Re:excellent (Score 1) 226

by sshir (#48722057) Attached to: Red Hat Engineer Improves Math Performance of Glibc
Recursion makes for elegant code, but in production code should be avoided. At least when you have no control of the input data. The reason is that there is a fairly tight restriction on stack size (you have to explicitly tell your OS that you need large stack). As a result you will coredump if your input is the right kind of nasty.

If this is timesharing, give me my share right now.