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

 



Forgot your password?
typodupeerror
×

Comment Re:Google announced this (Score 1) 233

A key is usually an integer, or a prime integer in some manifold or group. Asymmetric crypto depends on problems being easy one way and "hard" to reverse. elliptic curves are thought to be "harder" than the usual prime factoring. So yeah. It's how you use the bits. It takes a lot smaller number to provide a sufficiently ambiguous (in the reverse) operation.

Comment So don't use gnome. (Score 1) 729

This goofy shit is why I quit using gnome years ago. Even unity is better than this one size fits all usability shit that's handed down. I mean, at least give us a configuration option for it.... Anyway, I thought the gnome shell was even less relevant than unity. Cinimon? I kindof like the tiling window managers. I don't see the big thrill with gnome anyway. It's not a window manager... It's not a window decorator... what is it exactly? desktop what? I tried to live without it completely and used ratpoison for like 2 years. Tiling window managers have their own annoyances, but I really honestly didn't miss gnome. In fact, it was refreshing to not have usability dictated down. I often dictated it up by patching ratpoison -- which is small enough for me to modify easily. Yeah, I suppose I could patch gnome too, but this kind of user hating stuff comes down super regularly from these guys.

Comment Re:see, this is what I'm saying... (Score 1) 211

We're talking specifically about the point that there's a difference between API documentation (which should be an exaustive list of every function and the arguments it takes and why) and a tutorial that talks about how to use the thing. You're likely to find both in The Docs or they're simply not complete. And the point I was making was only that a techy will point out the difference or someone learning to program will quickly find the difference and then look for the tutorial first and the docs later when they're further along. That is the only point that I was making.

Everything else is a silly pointless argument. But this is the main takeaway: The Docs are almost always incomplete because there's nobody that's volunteered to write them and nobody paid to write them. What are you going to do? force the guy that volunteered to write the code to volunteer to write the docs? I doubt it's going to happen, so you'll have to live with reading source, writing your own, or using something else. If you lucked out and the dev wrote little blurbs above the function, great. If someone put some examples in a wiki, even better. If someone just happened to write geniuous docs, well, you've really found a gem and you're going to find a mix of tutorials and API docs and tutorials/examles for the good ones. The API docs are more important thouguh, cuz if all you have is some examples, you're going to go source diving without the API docs or you'll have to find something else.

Slashdot Top Deals

With your bare hands?!?

Working...