For open source systems, the person or persons who inserted the weak code should be identified and kicked off the project. It may just be incompetence, but that's a good reason to keep them out of security-critical areas.
You want to kick off the people who are most likely to never make that mistake ever again? That doesn't seem wise.
Would NO ONE open a file browser, and navigate to that media, and select that file he was interested in? NO ONE AT ALL?
Saying "NO ONE" in capitals so often doesn't really matter, because you're presenting a false dichotomy. It does matter if you go from 90% of people able to install something to only 25% of people. These numbers are totally made up, but I bet they're not totally off-base.
Now, you're right to say that there are other solutions to just making a walled garden. Ubuntu uses another method: installing from CDs is something that's pretty much never done, it has a software centre, so it has little need for autorun. But simply turning off the autorun option across the board is blind and foolish. You need to replace it with something so that the millions of Windows users without a clue can still get things done. Otherwise all they have is a large paperweight.
Android 4.2+ does a key verification thing for USB debugging. Basically you have to confirm a fingerprint when you plug it into a computer it hasn't seen before before ADB will work. Obviously, the confirmation can only happen when the screen is unlocked.
It seems quite smooth on my N4, I'm just not a fan of that way of doing things. Although, android does do it very subtly when you hit the end of a list while scrolling at speed. It's minor enough to not be distracting.
The real spelling can't be written on slashdot. If I write it correctly, it comes out "Mori." Or, in LaTeX: M\-{a}ori (IIRC.) It seems plausible that the editing process swallowed a macron.
Just browse though and see what grabs your eye. I quite like the 163x series (the first one or two are free, and then I was forced to buy the whole damn set.) Also, perhaps grab some of their magazines (Baen's Universe, IIRC - also in ePub) which might be good for getting an overview of what they have.
Be careful, they very much subscribe to the "first hit's free" philosophy, only the subsequent hits are also cheap:)
For open source systems, the person or persons who inserted the weak code should be identified and kicked off the project. It may just be incompetence, but that's a good reason to keep them out of security-critical areas.
You want to kick off the people who are most likely to never make that mistake ever again? That doesn't seem wise.
One of the things that your link quotes Shuttleworth as saying is "Strengthening the LTS point releases".
That would seem to be the opposite of not having them.
Perhaps also have a look at the bit where he says he's not going to have rolling releases.
Would NO ONE open a file browser, and navigate to that media, and select that file he was interested in? NO ONE AT ALL?
Saying "NO ONE" in capitals so often doesn't really matter, because you're presenting a false dichotomy. It does matter if you go from 90% of people able to install something to only 25% of people. These numbers are totally made up, but I bet they're not totally off-base.
Now, you're right to say that there are other solutions to just making a walled garden. Ubuntu uses another method: installing from CDs is something that's pretty much never done, it has a software centre, so it has little need for autorun. But simply turning off the autorun option across the board is blind and foolish. You need to replace it with something so that the millions of Windows users without a clue can still get things done. Otherwise all they have is a large paperweight.
Android 4.2+ does a key verification thing for USB debugging. Basically you have to confirm a fingerprint when you plug it into a computer it hasn't seen before before ADB will work. Obviously, the confirmation can only happen when the screen is unlocked.
I only get any data transference if the screen is unlocked when I plug it in.
Everything he said is correct, however.
It seems quite smooth on my N4, I'm just not a fan of that way of doing things. Although, android does do it very subtly when you hit the end of a list while scrolling at speed. It's minor enough to not be distracting.
Erk, Firefox on Android does the rubber-band thing, it's terrible. The light-up effect is much more preferable to me.
Gee I can't see why you don't find this immediately intuitive and convenient. /sarcasm
There is no such thing as intuitive here. You don't really know if it's convenient until you've tried it.
The source code for the Barcode Scanner app can be found here: http://code.google.com/p/zxing/source/browse/trunk
It is free as in Free, Apache 2.0 license.
Oh yeah, I turned off the unified menu because I use FFM also. The rest of it I quite like.
You could move the windows so that they don't overlap, but instead fit perfectly together and fill the screen in Unity.
Could you get a branded cover manufactured that you could glue to the tablet to make it even less attractive to thieves?
That doesn't make it any more right however. How many of those have direct commit access to the main kernel tree?
Well no, you can't just insert code just because something is open source. Trusted people and other reviewers look it over first.
Well, if the smarter people wouldn't turn off the telemetry, they'd get a more appropriate UI. They really only have themselves to blame.
Since my desktop is completely-clean of any icons,
You are not a standard at all.
We can tell you didn't watch it much at all then. A lot of them have been put out of their misery.
Also, the last update to that codebase was in July. Your developers can't be very busy then.
Heh, like this one that just fixes the naming: https://github.com/liblime/LibLime-Koha/commit/41764c12a22ebfab7f28087a1a82153125894985
The real spelling can't be written on slashdot. If I write it correctly, it comes out "Mori." Or, in LaTeX: M\-{a}ori (IIRC.) It seems plausible that the editing process swallowed a macron.
Just browse though and see what grabs your eye. I quite like the 163x series (the first one or two are free, and then I was forced to buy the whole damn set.) Also, perhaps grab some of their magazines (Baen's Universe, IIRC - also in ePub) which might be good for getting an overview of what they have. Be careful, they very much subscribe to the "first hit's free" philosophy, only the subsequent hits are also cheap :)
Is it really necessary to name-drop the product that you use to google something? :)
It seems to me that having 'enter' and 'return' do different things would cause horrible tech support nightmares. Not that I modded you anything...
Phase-shift? Without having actually tried it, I would have expected FSK to work better in actual audio.