Because "n" is on the right hand side of the keyboard, it requires someone to take their right hand off of the mouse to create a new tab. Ctrl-T can be typed entirely with the left hand.
It is for this reason CTRL-X, CTRL-C, and CTRL-V were chosen for clipboard commands.
I don't understand why you have to puchase a license before developing any of the code. Once you write the code, you own the copyright. You can only license the code you wrote under the GPL. However, once you purchase a commercial Qt license, you can choose to license your code under a commercial license. Since you ultimately own the copyright to the code you developed, you can release it under a different license.
There really isn't any way to make the ctrl-C, ctrl-V method of copy and paste compatible with terminal applications.
I wouldn't paint such a doomed picture. How about making Ctrl-C copy to the clipboard only when text is selected? Presumably this is the only time you'd wish to copy text. And in the reverse direction, I can't see a need to kill an app when you have screen space selected.
Ctrl-V is probably a harder one. I have seen this used in only one form:
stty erase Ctrl-V<Backspace>
For weird unixes this is a must. However, I think we can change this weird sequence to Ctrl-L (for literal) and go ahead and use Ctrl-V for pasting.
A terminal with the above features would be most welcome on my desktop.
If you were particularly inclined you could probably invent a problem that had to be done serially
Or prove that no such problem exists:).
All problems solved by computers are solved by a series of steps or computations (c_x). Each c_x has input and output. Say the input of a given c_x doesn't depend on the output of c_x-1. In this case, we can easily parallize the problem by computing c_x and c_x-1 in parallel.
Lets say that c_x does depend on the output of c_x-1. Let the number of possible outputs of c_x be n. We can run c_x in parallel for each of the possible outputs of c_x-1. All these computations are done at the same time as c_x-1. When they complete, we can use c_x-1's output to choose the solution of c_x without running any extra computation.
open source advocates (myself included) in favor of open source is the simple question: 'Would you buy a car with the hood welded shut?'
Just to push my Karma even further into the depths of sinful badness, I'd like to point out how source code is less like a car's components and more like a car's blueprint.
Car manufacturers are not going to give the instructions on how to create a clone of the motor you purchased. Especially not in a way where you could improve upon their design. In this way, closed software development represents current engineering business practices.
Allowing the hood to be opened is more akin to making the windows registry available or allowing the user to screw around with the locations of installed program files.
In conclusion, use other arguments for open source. I think that since code is notoriously harder to create bug-free than mechanical designs, open source may be viable for code where it isn't for blue prints. Arguments along this line would probably carry more weight.
Fundamentally this test was probably not complete enough to suggest anything in particular.
It's intention seemed not to compare program versions or compilations, but vanilla installations of various distributions. I am led to believe that most Gentoo users set up their system the same way this article outlined. And most, would likely assume it is faster than Debian or Mandrake installations.
This article clearly shows how this is not the case.
An interesting parallel to this is medical "anti-intrusion" systems. Penicillin used to be a miracle antibiotic, and then farmers started including it in cattle and chicken feed. Eventually every bacterium became resistant and penicillin lost most of its usefulness to the super bacteria that became widespread. See this
Practically speaking, if tripwire and daily security emails became part of every linux distribution, then packages like rootkit would quickly adapt to them and render them useless.
For those looking at security from a very high level, we must keep the "more effort implies more security" status. At least this way you have the option to having an extremely secure machine if it is really important to you.
Strong security for everyone will remain a dream until people start proving their code.
Competition for slashdot
on
KDE 3.0 is Out
·
· Score: 1, Insightful
I hate to defend slashdot here, but if they didn't put out the information first, another news service would. If slashdot didn't report this newsworthy information, then I would question the ethics of slashdot. People might even switch to a service that would report this.
As far as I'm concerned, this was a mistake of KDE to put this on their FTP site before announcing it. I'm sure there is a better mirror system than putting the files up before releasing them.
Slashdot Mirror
You can control what you do. You cannot control what you feel.
Also, there are no beta libraries in boost. A library is either in boost (and is production grade) or it isn't.
Check out VoipBuster. It is similar to Skype except calls to regular telephones in most of europe and the US is free.
WHAT?!?
I think you meant s$$$load.
What on earth is wrong with Ctrl-N for "New"?!
Because "n" is on the right hand side of the keyboard, it requires someone to take their right hand off of the mouse to create a new tab. Ctrl-T can be typed entirely with the left hand.
It is for this reason CTRL-X, CTRL-C, and CTRL-V were chosen for clipboard commands.
http://www.microsoft.com/products/expression/en/de mos.aspx
Nope, that's the 5% of development groups that have never delivered a project at any point.
I don't understand why you have to puchase a license before developing any of the code. Once you write the code, you own the copyright. You can only license the code you wrote under the GPL. However, once you purchase a commercial Qt license, you can choose to license your code under a commercial license. Since you ultimately own the copyright to the code you developed, you can release it under a different license.
I wouldn't paint such a doomed picture. How about making Ctrl-C copy to the clipboard only when text is selected? Presumably this is the only time you'd wish to copy text. And in the reverse direction, I can't see a need to kill an app when you have screen space selected.
Ctrl-V is probably a harder one. I have seen this used in only one form:
For weird unixes this is a must. However, I think we can change this weird sequence to Ctrl-L (for literal) and go ahead and use Ctrl-V for pasting.
A terminal with the above features would be most welcome on my desktop.
Uhm, no comment.
It annoys me too. Just put this at the top of your file:
#define for if (true) for
problem solved.
Or prove that no such problem exists :).
All problems solved by computers are solved by a series of steps or computations (c_x). Each c_x has input and output. Say the input of a given c_x doesn't depend on the output of c_x-1. In this case, we can easily parallize the problem by computing c_x and c_x-1 in parallel.
Lets say that c_x does depend on the output of c_x-1. Let the number of possible outputs of c_x be n. We can run c_x in parallel for each of the possible outputs of c_x-1. All these computations are done at the same time as c_x-1. When they complete, we can use c_x-1's output to choose the solution of c_x without running any extra computation.
Well, it's a sketch anyway.
open source advocates (myself included) in favor of open source is the simple question: 'Would you buy a car with the hood welded shut?'
Just to push my Karma even further into the depths of sinful badness, I'd like to point out how source code is less like a car's components and more like a car's blueprint.
Car manufacturers are not going to give the instructions on how to create a clone of the motor you purchased. Especially not in a way where you could improve upon their design. In this way, closed software development represents current engineering business practices.
Allowing the hood to be opened is more akin to making the windows registry available or allowing the user to screw around with the locations of installed program files.
In conclusion, use other arguments for open source. I think that since code is notoriously harder to create bug-free than mechanical designs, open source may be viable for code where it isn't for blue prints. Arguments along this line would probably carry more weight.
+1 Humble
What kinds of new and wonderful things can you come up with?
rm *.xml
You forgot "IANAL".
"A lot" is two words. You wouldn't say "alittle", would you?
You wouldn't say "I had a little of fun", would you? "A lot" is a special case.
Fundamentally this test was probably not complete enough to suggest anything in particular.
It's intention seemed not to compare program versions or compilations, but vanilla installations of various distributions. I am led to believe that most Gentoo users set up their system the same way this article outlined. And most, would likely assume it is faster than Debian or Mandrake installations.
This article clearly shows how this is not the case.
How informative is someone who gets painful shocks the same way twice?
So much for your old high school friends getting in touch with you. Oh yeah, what friends?
What do you think happened to the other moon we used to have?
Remove the e-mail to NOSPAM
Hehe.
An interesting parallel to this is medical "anti-intrusion" systems. Penicillin used to be a miracle antibiotic, and then farmers started including it in cattle and chicken feed. Eventually every bacterium became resistant and penicillin lost most of its usefulness to the super bacteria that became widespread. See this
Practically speaking, if tripwire and daily security emails became part of every linux distribution, then packages like rootkit would quickly adapt to them and render them useless.
For those looking at security from a very high level, we must keep the "more effort implies more security" status. At least this way you have the option to having an extremely secure machine if it is really important to you.
Strong security for everyone will remain a dream until people start proving their code.
I hate to defend slashdot here, but if they didn't put out the information first, another news service would. If slashdot didn't report this newsworthy information, then I would question the ethics of slashdot. People might even switch to a service that would report this.
As far as I'm concerned, this was a mistake of KDE to put this on their FTP site before announcing it. I'm sure there is a better mirror system than putting the files up before releasing them.