It is obvious to me that hour hands were evolved to pick up rocks and sticks and then either wield them as weapons or throw them. Making a fist is something we do as a last resort when we are unarmed.
I have found the following advantages to command lines:
+ For the most part, commands in command lines remain backward compatible.
+ Scripting. Have you ever tried to script to a GUI? That is part of why apple-script was such a failure! It's a nightmare! Full of stuff like poke at the "download" item in the "file" menu
+ With a good history editor repeating prior commands (maybe with slight modification) is easy.
I personally type much faster than I mouse, so I also prefer command lines for productivity reasons.
Hardware was expensive and slow. Most PCs (The MAC didn't exist yet) were running on floppys, modems were 1200 baud at best and they weren't built in, they were an extra cost and they tied up your phone line. In order to set up a computer that had a modem you were in for $1000-$2000 at least.
The necessary software didn't exist yet. There was no web browser. There weren't any decent GUI OS shells in common usage. The URL didn't even exist yet.
The infrastructure wasn't there! DNS Wasn't out yet, so you didn't have Domain Names. No DNS, and no WEB, so of course there were no search engines!
I just use tar archives! I put the archive on a FAT32 file system and then I keep my permissions and I don't have to be root to extract it. You also get compression for free.
I think the spammers check the SPF records, and if there is one they don't forge your address. I had lots of problems with my e-mail address being forged by spammers. When I put in an SPF record, it stopped immediatly.
Some women seem to be incapable of looking before they sit. Have you ever had a guy sit on something in the passenger seat of your car before you could move it? I haven't, but I have had several women do it. They just can't or at least don't look before they sit. This is why the need to have seat down all the time.
It is the ultimate defense. I have learned that if you change the rule to "Everyone should close the lid." then women are as bad if not worse about it. In the end they can't complain about that one.
You are never going to get money back from security investments, you are limiting losses. That puts you into Risk Management analays, not Return on investment. Think of it like going without insurance, worker injury prevention, or other loss prevention/mitigation.
I have had problems with spammers using one of the domains I owned. I added an SPF record and within two months they quit using my domain. I suspect spammers avoid domains with SPF records, for now.
I know there will be lots of consumer appliences such as VCRs and Clock radios that currently know when daylight savings time is and will either be wrong for some weeks in the spring and fall or have to be changed 4 times a year.
Unix/Linux should be fine as long as you update your timezone files appropriately.
And there may be some apps and/or websites that may have problems, but I expect the consumer appliences will have the most problems exactly because they won't get updated even if they could be.
I believe you should keep the certificates secure and make sure that, in the case of SSL certificates, the certificate holder is the owner of the domain and that is it. If you want information about a domain, Black List, White List, or more involved reputation, that should be a separate service. The certificate policies should only involve enough rules to make sure the private key is not compromised. There are already several reputation services as it is; the browsers should support displaying info from reputation services about domains that are authenticated via the existing SSL process.
Let's just stick to capitalism. It is worth whatever someone is willing to pay for it. So if the game currency can be traded in the real world for $$$ or other hard currency, that is what it is worth. If, however, the game currency does not trade for real world hard currency, then it is hard to say there was a real world loss.
In my experience, hardware encryption doesn't keep up with speed either. If you are using software encryption, it gets faster along with everything else as you upgrade to faster machines. Hardware encryption just does not keep pace with the increasing speed of general purpose processors.
The only remaining reason to keep hardware encryption around is to protect your private keys. Even in this way hardware can be problematic. If you have important private keys locked away in hardware, you need to have some backup plan if the hardware fails, or is not fast enough to meet future demand. So even in this case, you are probably better off with general purpose hardware that will protect/destroy its contents if physically attacked. Of course you can keep the hardware with the private keys on a secure subnet as well.
Prior to about 1995, encryption technology was classified by the State Department as
ammunition.
It only seems fair that we should now encrypt ammunition.
The two are already tied together in many people's eyes.
If they are going to do this, I would certainly hope that both the encrypted signal, and some mechanical action (e. g. A striking firing pin) are required to fire the bullet.
This approach would prevent a bullet from accidentally firing just because it received a signal.
Options are worthless if they never vest. You should insist on something that gets you actual stock as you go. Monthly vesting, up-front stock grants, maybe with the stock in escrow. Then they can not sell off the assets without notifying you as a shareholder.
All of the fancy notes, options, future grants, and other instruments are not very meaningful until they actually turn into stock. You will also find that you often have more rights as a shareholder than as an employee.
The only down side to this approach is that you will be paying for stock (either in cash or tax liabilities) in advance when the stock may end up being worthless.
Everyone seems to ignore the Space Race and how instrumental it was in early development of the transistor, the integrated circuit, and the micro-processor. All of the things were developed with NASA money because they needed electronics that consumed less power and generated less heat. Less power because it is expensive to carry power in space, and less heat because cooling is expensive when you can not just jettison the heat.
Additionally there were many other technologies from micro-wave to lasers, that were developed here. Again these were largely funded by NASA in the quest for the moon race. Additionally, many aerospace companies brought many engineers and collected them here because of the race to the moon.
I firmly believe that the Silicon Valley could not even be recreated here without another space race!
One is that there is a HUGE difference between Linux and Unix and the original poster said Unix. The design of networking and Unix was an iterative process, and the first versions of Unix had only a part of what is currently called Unix. So what people currently called Unix was designed around networking.
As far as network operating systems, it was Sun that first had the motto "The Network is the Computer." And this was for their Unix system, long before Mosaic, and the first HTTP RFC.
There were several Unix implementations that achieved Orange book B2 compliance long before anything Microsoft produced did. Furthermore, Micro$oft is likely to take the OS in any direction that will make them money. They seem to like the idea that people have to pay for a network service on a time/subscription basis, whereas they usually buy an OS for a given piece of hardware once.
Use indent for C and C++ And Jalopy for Java. Formatters are available for most languages. Decide on what all of the options are for each formatter and make a script available that runs the formatter with the appropriate options.
Require that automated formatters be run before code is checked in.
It is easier to read consistant formatting than your favorite formatting.
The second half of the move plays much more on an emotional level. The result for a lot of people, especially those that have children, is to shock them into action.
Slashdot Mirror
It is obvious to me that hour hands were evolved to pick up rocks and sticks and then either wield them as weapons or throw them.
Making a fist is something we do as a last resort when we are unarmed.
Vote Early and Vote Often!
poke at the "download" item in the "file" menu
I personally type much faster than I mouse, so I also prefer command lines for productivity reasons.
Not even close. The guy that threw the shoes at Bush got 3 years. Bush never lifted a finger for him.
http://articles.cnn.com/2009-03-12/world/iraq.shoe.thrower_1_zaidi-al-maliki-and-bush-shoes?_s=PM:WORLD
Which is better?
Area = (pi) r^2
or
Area = (tau/2) r^2
It all depends on what problem you are trying to solve.
Just live with pi.
Hardware was expensive and slow. Most PCs (The MAC didn't exist yet) were running on floppys, modems were 1200 baud at best and they weren't built in, they were an extra cost and they tied up your phone line. In order to set up a computer that had a modem you were in for $1000-$2000 at least.
The necessary software didn't exist yet. There was no web browser. There weren't any decent GUI OS shells in common usage. The URL didn't even exist yet.
The infrastructure wasn't there! DNS Wasn't out yet, so you didn't have Domain Names. No DNS, and no WEB, so of course there were no search engines!
You can upload the doc file to google docs and then read it.
I just use tar archives! I put the archive on a FAT32 file system and then I keep my permissions and I don't have to be root to extract it. You also get compression for free.
I think the spammers check the SPF records, and if there is one they don't forge your address.
I had lots of problems with my e-mail address being forged by spammers.
When I put in an SPF record, it stopped immediatly.
Some women seem to be incapable of looking before they sit.
Have you ever had a guy sit on something in the passenger seat of your car before you could move it?
I haven't, but I have had several women do it.
They just can't or at least don't look before they sit.
This is why the need to have seat down all the time.
It is the ultimate defense. I have learned that if you change the rule to "Everyone should close the lid." then women are as bad if not worse about it. In the end they can't complain about that one.
I had the same problem some years ago, but as soon as I added SPF records to my domains, the spammers quit using addresses from my domain.
You are never going to get money back from security investments, you are limiting losses.
That puts you into Risk Management analays, not Return on investment.
Think of it like going without insurance, worker injury prevention, or other loss prevention/mitigation.
I have had problems with spammers using one of the domains I owned.
I added an SPF record and within two months they quit using my domain.
I suspect spammers avoid domains with SPF records, for now.
I know there will be lots of consumer appliences such as VCRs and Clock radios that currently know when daylight savings time is and will either be wrong for some weeks in the spring and fall or have to be changed 4 times a year.
Unix/Linux should be fine as long as you update your timezone files appropriately.
And there may be some apps and/or websites that may have problems, but I expect the consumer appliences will have the most problems exactly because they won't get updated even if they could be.
I believe you should keep the certificates secure and make sure that, in the case of SSL certificates, the certificate holder is the owner of the domain and that is it. If you want information about a domain, Black List, White List, or more involved reputation, that should be a separate service. The certificate policies should only involve enough rules to make sure the private key is not compromised. There are already several reputation services as it is; the browsers should support displaying info from reputation services about domains that are authenticated via the existing SSL process.
Let's just stick to capitalism. It is worth whatever someone is willing to pay for it. So if the game currency can be traded in the real world for $$$ or other hard currency, that is what it is worth. If, however, the game currency does not trade for real world hard currency, then it is hard to say there was a real world loss.
In my experience, hardware encryption doesn't keep up with speed either. If you are using software encryption, it gets faster along with everything else as you upgrade to faster machines. Hardware encryption just does not keep pace with the increasing speed of general purpose processors.
The only remaining reason to keep hardware encryption around is to protect your private keys. Even in this way hardware can be problematic. If you have important private keys locked away in hardware, you need to have some backup plan if the hardware fails, or is not fast enough to meet future demand. So even in this case, you are probably better off with general purpose hardware that will protect/destroy its contents if physically attacked. Of course you can keep the hardware with the private keys on a secure subnet as well.
It only seems fair that we should now encrypt ammunition.
The two are already tied together in many people's eyes.
If they are going to do this, I would certainly hope that both the encrypted signal, and some mechanical action (e. g. A striking firing pin) are required to fire the bullet.
This approach would prevent a bullet from accidentally firing just because it received a signal.
Options are worthless if they never vest. You should insist on something that gets you actual stock as you go. Monthly vesting, up-front stock grants, maybe with the stock in escrow. Then they can not sell off the assets without notifying you as a shareholder.
All of the fancy notes, options, future grants, and other instruments are not very meaningful until they actually turn into stock. You will also find that you often have more rights as a shareholder than as an employee.
The only down side to this approach is that you will be paying for stock (either in cash or tax liabilities) in advance when the stock may end up being worthless.
Everyone seems to ignore the Space Race and how instrumental it was in early development of the transistor, the integrated circuit, and the micro-processor. All of the things were developed with NASA money because they needed electronics that consumed less power and generated less heat. Less power because it is expensive to carry power in space, and less heat because cooling is expensive when you can not just jettison the heat.
Additionally there were many other technologies from micro-wave to lasers, that were developed here. Again these were largely funded by NASA in the quest for the moon race. Additionally, many aerospace companies brought many engineers and collected them here because of the race to the moon.
I firmly believe that the Silicon Valley could not even be recreated here without another space race!
A few issues with your mostly correct posting.
One is that there is a HUGE difference between Linux and Unix and the original poster said Unix. The design of networking and Unix was an iterative process, and the first versions of Unix had only a part of what is currently called Unix. So what people currently called Unix was designed around networking.
As far as network operating systems, it was Sun that first had the motto "The Network is the Computer." And this was for their Unix system, long before Mosaic, and the first HTTP RFC.
There were several Unix implementations that achieved Orange book B2 compliance long before anything Microsoft produced did. Furthermore, Micro$oft is likely to take the OS in any direction that will make them money. They seem to like the idea that people have to pay for a network service on a time/subscription basis, whereas they usually buy an OS for a given piece of hardware once.
Use indent for C and C++
And Jalopy for Java.
Formatters are available for most languages.
Decide on what all of the options are for each formatter and make
a script available that runs the formatter with the appropriate options.
Require that automated formatters be run before code is checked in.
It is easier to read consistant formatting than your favorite formatting.
The usual technique is for the signer to append
some unguessable, preferably random, stuff to the message before signing such as:
1. "Joe will send Dr. Blue $10. Confirmation number 1234567. Joe agrees FDXasd-lvaudfljw"
This way you can avoid the birthday attacks and the attacker must take on the hash at full strength.
The second half of the move plays much more on an emotional level. The result for a lot of people, especially those that have children, is to shock them into action.