Security is the antagonist to comfort. [etc. etc. etc.]
Your entire rant is based on a false premise. In most cases, security actually increases "comfort" or "convenience." It's damn inconvenient to use a system which crashes, misbehaves, and needs to be frequently rebuilt due to security problems. Removing buffer overflow vulnerabilities from your software in no way inconveniences your users.
Authentication is perhaps the only piece that sometimes is inconvenient. Just typing your username to log in is more convenient than having to type a password. But that's the exception to the rule. And systems which time you out while you're using them, and don't integrate with SSO, are actually not "more secure," they're just badly-implemented. So that's not a trade-off either.
On the contrary, I think the CPU will go the way of the coprocessor. The humble Atom may be enough CPU power for most people these days, but you can never have enough GPU power... at least not until your po-- I mean, games, are photorealistic in real time.
C# was developed as a reaction to Java. They were trying to make a language with Java's features but without its warts. I'm sure it is easier than Java for many things.
Ruby and Python were both developed as reactions to Perl (again: all the features, sans the warts). Python tried to be easy for beginner programmers (and was successful; it's taught in many intro classes). Ruby tried to be easy to experienced programmers. If you're trying to to real OOP, you will find no easier syntax than Ruby's.
So, at least in some ways, both those languages are "easier."
Bank chairmen: "Mr. Obama and Congress, give us billions of dollars of the Public's money, no strings attached."
Politicians: "If we don't do this, your banks will close, the FDIC will go bankrupt, and we will have a terrible deflationary depression, is that right?"
Bank chairmen: "You are correct. Billions of dollars, please. Hand 'em over."
Politicians: "Well we must prevent a depression, but you don't exactly deserve billions of the Public's money. So here's the cash, but there will be strings attached..."
Bank chairmen: "Whatever; thanks for the cash! PS: buy these defaulting mortgages from us too, please. At twice their real value. Good! Bye!"... one year later...
Politicians: "Here are the strings we told you about..."
Bank chairmen: "What? Regulation? Penalties? You radicals! We thought you were balanced centrists, not commies! After all our payouts, we still have a few billion of the Public's money left. If you try to force any penalties on us, that money will be used to make sure you never get elected again. Checkmate."
No, this is all just justification for more spending. IT security spending counts as "economic infrastructure" in my book, so it probably isn't the worst possible way to use public money.
Among the appengine hard limits which aren't documented are: simultaneous URLFetch limits and "excessive latency" limits.
Even "hello world" servlets in java are randomly killed for "excessive latency" in appengine.
They call it a "preview release" and that's a good name for their Java support. Java performance is absolutely terrible on appengine, even for "hello world." Yes, it works ok most of the time. It the rest of the time, fails to work randomly with "excessive latency" errors. Appengine java is not ready for production use.
Energy prices can go up or down. If you want to bet on the cost of energy going up, there are much easier and less-risky financial instruments you could buy with a click of the mouse--no million dollar mystery box required.
AppEngine does not scale. There are countless hard limits in appengine, many of which are not documented.
Furthermore, only two languages are supported in appengine: Python and Java. And Java performance is really terrible. Java web apps are killed at random times for "excessive latency" by appengine. It also loads and unloads your apps aggressively, so your users will see very long delays when accessing Java-based web apps.
If you're using Python and you think you can fit within the many API limits and scalability limits of appengine, give it a try. Otherwise, look elsewhere.
I know slashdot loves bad analogies, but this you the cake. IT security is most certainly not an illusion. It is very real. With no IT security, an kid halfway around the world could steal your data and sabotage your business on a whim. With well-funded, well-implemented, and fully-staffed IT security programs, it would take a dedicated, big-budget espionage operation to ruin you. And even then, such things would likely be detected and contained.
If you call that difference illusionary, you've got vision problems.
What would be reasonable would be to dedicate more screen space to certificate information. Make sure the users see exactly who signed a cert, and exactly which site the certificate is assigned to.
It is my personal experience that "flicker" glasses do, in fact, result in less brightness when viewing a display. I don't doubt what you are saying bout LED brightness, but I'm also not sure that it applies here.
The problem with all of these is that of brightness. If you're sending data to one eye at a time, the other eye sees darkness. It's like wearing 50% tint sunglasses.
If you are looking for a display to do flicker 3D, make sure you get one with a really really bright backlight.
In my experience, there is lots of ageism, but in the other direction.
How many job postings are there for Junior IT or developer positions? Almost none. And for "Senior" positions? Almost all of them require many years of experience.
Left 4 Dead and Team Fortress 2 both have options to use multiple cores. I believe that, when enabled, the other cores to "physics processing." My understanding is that "physics processing" is geek-speak for "making the bodies of your slain foes collapse into realistic piles of death as they hit the ground."
The fact that some local education board wants school books to promote their misleading and unscientific ideology is a small problem, but it's a problem the rest of the country doesn't have too much influence over.
The fact that this affects the nation as a whole is a big problem. Solution? Stop letting Texas influence national text books.
Slashdot Mirror
Your entire rant is based on a false premise. In most cases, security actually increases "comfort" or "convenience." It's damn inconvenient to use a system which crashes, misbehaves, and needs to be frequently rebuilt due to security problems. Removing buffer overflow vulnerabilities from your software in no way inconveniences your users.
Authentication is perhaps the only piece that sometimes is inconvenient. Just typing your username to log in is more convenient than having to type a password. But that's the exception to the rule. And systems which time you out while you're using them, and don't integrate with SSO, are actually not "more secure," they're just badly-implemented. So that's not a trade-off either.
On the contrary, I think the CPU will go the way of the coprocessor. The humble Atom may be enough CPU power for most people these days, but you can never have enough GPU power... at least not until your po-- I mean, games, are photorealistic in real time.
C# was developed as a reaction to Java. They were trying to make a language with Java's features but without its warts. I'm sure it is easier than Java for many things.
Ruby and Python were both developed as reactions to Perl (again: all the features, sans the warts). Python tried to be easy for beginner programmers (and was successful; it's taught in many intro classes). Ruby tried to be easy to experienced programmers. If you're trying to to real OOP, you will find no easier syntax than Ruby's.
So, at least in some ways, both those languages are "easier."
When HTML5 video overtakes Flash video on the Internet, Apple will make sure only Quicktime video works with their iP** products.
I can see those conversations:
Bank chairmen: "Mr. Obama and Congress, give us billions of dollars of the Public's money, no strings attached."
Politicians: "If we don't do this, your banks will close, the FDIC will go bankrupt, and we will have a terrible deflationary depression, is that right?"
Bank chairmen: "You are correct. Billions of dollars, please. Hand 'em over."
Politicians: "Well we must prevent a depression, but you don't exactly deserve billions of the Public's money. So here's the cash, but there will be strings attached..."
Bank chairmen: "Whatever; thanks for the cash! PS: buy these defaulting mortgages from us too, please. At twice their real value. Good! Bye!" ... one year later ...
Politicians: "Here are the strings we told you about..."
Bank chairmen: "What? Regulation? Penalties? You radicals! We thought you were balanced centrists, not commies! After all our payouts, we still have a few billion of the Public's money left. If you try to force any penalties on us, that money will be used to make sure you never get elected again. Checkmate."
Politicians: "Oh fuck--pwned."
No, this is all just justification for more spending. IT security spending counts as "economic infrastructure" in my book, so it probably isn't the worst possible way to use public money.
Among the appengine hard limits which aren't documented are: simultaneous URLFetch limits and "excessive latency" limits.
Even "hello world" servlets in java are randomly killed for "excessive latency" in appengine.
They call it a "preview release" and that's a good name for their Java support. Java performance is absolutely terrible on appengine, even for "hello world." Yes, it works ok most of the time. It the rest of the time, fails to work randomly with "excessive latency" errors. Appengine java is not ready for production use.
Energy prices can go up or down. If you want to bet on the cost of energy going up, there are much easier and less-risky financial instruments you could buy with a click of the mouse--no million dollar mystery box required.
So when you're generating your keys, all I have to do is blast your wifi and I can pick your keys for you? Cool!
AppEngine does not scale. There are countless hard limits in appengine, many of which are not documented.
Furthermore, only two languages are supported in appengine: Python and Java. And Java performance is really terrible. Java web apps are killed at random times for "excessive latency" by appengine. It also loads and unloads your apps aggressively, so your users will see very long delays when accessing Java-based web apps.
If you're using Python and you think you can fit within the many API limits and scalability limits of appengine, give it a try. Otherwise, look elsewhere.
You can afford a huge house, but you can't come up with $100 for a tranceiver? That's absolutely daft.
Civ IV does have the option to disable animations. Apparently, you never looked...
Prove? No. But reducing the risk by 99.9% is practically the same, though.
Holy bad analogies, batman!
I know slashdot loves bad analogies, but this you the cake. IT security is most certainly not an illusion. It is very real. With no IT security, an kid halfway around the world could steal your data and sabotage your business on a whim. With well-funded, well-implemented, and fully-staffed IT security programs, it would take a dedicated, big-budget espionage operation to ruin you. And even then, such things would likely be detected and contained.
If you call that difference illusionary, you've got vision problems.
Politics is the reason. It's hard to get funding (for something like increased IT spending) without politics.
That's not a practical option.
What would be reasonable would be to dedicate more screen space to certificate information. Make sure the users see exactly who signed a cert, and exactly which site the certificate is assigned to.
It is my personal experience that "flicker" glasses do, in fact, result in less brightness when viewing a display. I don't doubt what you are saying bout LED brightness, but I'm also not sure that it applies here.
The problem with all of these is that of brightness. If you're sending data to one eye at a time, the other eye sees darkness. It's like wearing 50% tint sunglasses.
If you are looking for a display to do flicker 3D, make sure you get one with a really really bright backlight.
In my experience, there is lots of ageism, but in the other direction.
How many job postings are there for Junior IT or developer positions? Almost none. And for "Senior" positions? Almost all of them require many years of experience.
That's discrimination against the young.
Never had freezes on my Intel quad-core system, either in L4D or L4D2.
The collider would shut down for two years due to some component overheating.
Left 4 Dead and Team Fortress 2 both have options to use multiple cores. I believe that, when enabled, the other cores to "physics processing." My understanding is that "physics processing" is geek-speak for "making the bodies of your slain foes collapse into realistic piles of death as they hit the ground."
Software developers are artists now? What???
How do you propose it detects that a person is 500 meters away? This is a laser; it's long range.
The fact that some local education board wants school books to promote their misleading and unscientific ideology is a small problem, but it's a problem the rest of the country doesn't have too much influence over.
The fact that this affects the nation as a whole is a big problem. Solution? Stop letting Texas influence national text books.