One use for computer labs is to try out solutions that can't be tried out on normal computers due to destructive nature or the need for specialized hardware.
Alternate operating system educations are also pushing the need for computer labs.
So there is a need for computer labs, but not for general tasks.
Fingerprinting is always a problem when you use touch screens.
Especially after a snack or a meal.
Aside from that - users also have different movement patterns, which causes every user to be recognized and to let the device learn the behavior of the user.
And don't forget that gestures have different meanings in different cultures.
Combine DRM with an EULA written by a lawyer trying to skin you for your arm and leg for any conceived wrongdoing and when the EULA also states that you use the application/data on your own risk and no responsibility for hardware or anything else and you are toast.
Mind that most EULA:s aren't worth the paper they are written on.
It's just natural selection at work, companies grows bigger and bigger and devour all competition and suddenly they are big enough to collapse and the cycle starts over again.
And I for one can just consider that Visual Studio sucks compared to Eclipse when it comes to how user-friendly the tool is.
The issue shouldn't be with the carriers at all. The issue should be if the customers want the specific phone.
It seems to me that the market in the US when it comes to mobile phones isn't favoring what the customer wants but is instead enforced by the carriers.
Just because it's hard doesn't mean that we shall give up trying.
This field is still a very young field, and the methods used to find planets will be more and more refined over time.
But it's also important to not count out stellar systems that may not look like they are going to contain earth-like planets. Even a negative answer is an answer giving usable data in this case.
Earth is the only speck of dust in the universe where we are certain that there is life. If it's intelligent enough to prosper in the long run remains to be seen. Considering the chemical processes seen in other places in the universe it's likely that life exists elsewhere, but in different forms from what we see here. It would be extremely surprising if we were to find life on an earth-like planet that's similar to us down to the DNA/RNA level.
What humankind need is to continue to find ways of understanding the universe and how to best utilize the possibilities and circumvent the problems.
The step between Java and C# is not that bad, but be aware that a too strict focus on Microsoft platforms can also be a risk in the long run.
Specialize in trying to learn how to be portable between platforms.
Fortran isn't a bad language, but it's used only in specialized applications. It has some advantages in multi-core solutions provided that the compiler supports it.
Erlang is an interesting language to know, and is probably more useful than you first realize.
But what's important to learn is how to break down a problem into components. This regardless of programming language. Writing everything in one humongous block of code makes it hard to follow and maintain.
And make sure to learn tools like splint (for C) and FindBugs (for Java) and to understand the responses they give. This will be a learning experience in how to write code that has a low bug percentage. These tools doesn't protect you from strategic faults and system design faults, but it can catch a lot of those pesky errors that can cause problems at inconvenient moments in the future.
Learning to program is learning a strategy. It takes years of experience before being good, and only a few can be excellent. And even the excellent developers are making mistakes.
What's important is also to avoid getting stuck in a certain sector, make sure that if you have skills like Fortran and Cobol, don't promote them too much or you will be known as a Cobol programmer and be overlooked when trying to find new interesting jobs.
Another perspective in selecting languages to learn is the availability of useful development tools. Java has Eclipse and a lot of other additional tools and plugins to help the programmer. C isn't that well supported, but it's a simpler language from some perspectives and there still exists tools like splint and PurifyPlus.
Forget about which language that has the largest amount of libraries. A huge amount of libraries is like a huge forest, it's easy to get lost. But you shouldn't avoid a language on this criteria. Some languages doesn't need huge libraries as much as other languages do.
This is the problem with new features - the users have problems using them until they fully understands and appreciates the advantages and disadvantages.
And also consider - ext4 is relatively new, so it will improve over time. If you want stability stick to ext3 or ext2. If you want a really stupid filesystem go FAT and prepare for a patent attack.
I have a Nikon D80 and it has a lot less noise than my friends Canon G9 which has more pixels.
What I really want is a wider range of sensitivity. Both higher sensitivity for photo in the dark, but also a lower sensitivity for some cases where I actually would like to have the blur of motion in bright sunlight.
For the latter cases there are of course filters available, so it's possible to work around it. But there is no way to improve the sensitivity the same way.
As for megapixel race - you can buy a 50 megapixel camera today if you like. It's just a question of money!
And then you can build an extreme camera yourself using a flatbed scanner.
If you do shaping - make sure that you do it in a reasonable way. I.e. increase prio for critical/sensitive services like VoIP (SIP and IAX2) instead of slowing down specific services like bittorrent.
Almost every software patent is troll patents one way or another because they just causes trouble for software development.
As it is now one company can claim a software patent and claim thousands of man-hours for it while another can do the same development in an afternoon with the right guy.
And if you have a patent attack on Linux it's subsequently also attacking GPL.
And who in their right mind thinks that a foreign nation doesn't already know the existence, location and layout of various bases around the world?
Some bribes or joint ventures later and information exceeding the information available at Google Earth is widespread.
Blurring a satellite or air photo today is just a giveaway since two different distributions never have the same blurring and that tells others that this is a site of interest.
Slashdot Mirror
fvwm or blackbox are good enough for most cases.
Gnome and KDE are Windows wannabees...
I haven't seen any computer that's able to present Vista with a decent experience yet.
Most of today's computers are still barely able to provide a decent experience with XP.
So to be really Vista capable (with a decent experience) - that's still some years away.
One use for computer labs is to try out solutions that can't be tried out on normal computers due to destructive nature or the need for specialized hardware.
Alternate operating system educations are also pushing the need for computer labs.
So there is a need for computer labs, but not for general tasks.
Fingerprinting is always a problem when you use touch screens.
Especially after a snack or a meal.
Aside from that - users also have different movement patterns, which causes every user to be recognized and to let the device learn the behavior of the user.
And don't forget that gestures have different meanings in different cultures.
To have a study that says that the sky is blue.
If the study was saying that they were unable to feel pain - then it would be news.
Combine DRM with an EULA written by a lawyer trying to skin you for your arm and leg for any conceived wrongdoing and when the EULA also states that you use the application/data on your own risk and no responsibility for hardware or anything else and you are toast.
Mind that most EULA:s aren't worth the paper they are written on.
DRM = Digital Rape Method.
It's just natural selection at work, companies grows bigger and bigger and devour all competition and suddenly they are big enough to collapse and the cycle starts over again.
And I for one can just consider that Visual Studio sucks compared to Eclipse when it comes to how user-friendly the tool is.
Use Linux, recompile the kernel with the necessary drivers only and use fvwm or another light-weight window manager to speed things up even more.
Also optimize the startup scripts to skip any service not needed.
And finally - recompile the kernel specifically for your processor.
If you are lucky it's only that, if not you will get all kind of problems. Murphy's law is the most prominent feature in cases like these.
You never know if there is a secondary software that is depending on the product key and will go and die if it's changed.
Even Option A can cause disruption these days. You have problems regardless of which environment you select.
The issue shouldn't be with the carriers at all. The issue should be if the customers want the specific phone.
It seems to me that the market in the US when it comes to mobile phones isn't favoring what the customer wants but is instead enforced by the carriers.
Just because it's hard doesn't mean that we shall give up trying.
This field is still a very young field, and the methods used to find planets will be more and more refined over time.
But it's also important to not count out stellar systems that may not look like they are going to contain earth-like planets. Even a negative answer is an answer giving usable data in this case.
Earth is the only speck of dust in the universe where we are certain that there is life. If it's intelligent enough to prosper in the long run remains to be seen. Considering the chemical processes seen in other places in the universe it's likely that life exists elsewhere, but in different forms from what we see here. It would be extremely surprising if we were to find life on an earth-like planet that's similar to us down to the DNA/RNA level.
What humankind need is to continue to find ways of understanding the universe and how to best utilize the possibilities and circumvent the problems.
The problem is that the laws and the penalties are too relaxed for crimes like these.
A more severe penalty for involvement in fraud crimes would make many more a lot more vigilant when it comes to strangling that kind of behavior.
C, Java and Erlang.
The step between Java and C# is not that bad, but be aware that a too strict focus on Microsoft platforms can also be a risk in the long run.
Specialize in trying to learn how to be portable between platforms.
Fortran isn't a bad language, but it's used only in specialized applications. It has some advantages in multi-core solutions provided that the compiler supports it.
Erlang is an interesting language to know, and is probably more useful than you first realize.
But what's important to learn is how to break down a problem into components. This regardless of programming language. Writing everything in one humongous block of code makes it hard to follow and maintain.
And make sure to learn tools like splint (for C) and FindBugs (for Java) and to understand the responses they give. This will be a learning experience in how to write code that has a low bug percentage. These tools doesn't protect you from strategic faults and system design faults, but it can catch a lot of those pesky errors that can cause problems at inconvenient moments in the future.
Learning to program is learning a strategy. It takes years of experience before being good, and only a few can be excellent. And even the excellent developers are making mistakes.
What's important is also to avoid getting stuck in a certain sector, make sure that if you have skills like Fortran and Cobol, don't promote them too much or you will be known as a Cobol programmer and be overlooked when trying to find new interesting jobs.
Another perspective in selecting languages to learn is the availability of useful development tools. Java has Eclipse and a lot of other additional tools and plugins to help the programmer. C isn't that well supported, but it's a simpler language from some perspectives and there still exists tools like splint and PurifyPlus.
Forget about which language that has the largest amount of libraries. A huge amount of libraries is like a huge forest, it's easy to get lost. But you shouldn't avoid a language on this criteria. Some languages doesn't need huge libraries as much as other languages do.
This is the problem with new features - the users have problems using them until they fully understands and appreciates the advantages and disadvantages.
And also consider - ext4 is relatively new, so it will improve over time. If you want stability stick to ext3 or ext2. If you want a really stupid filesystem go FAT and prepare for a patent attack.
No problem at all. Use an analog thermostat. The decimal part isn't needed for household use anyway and is just a bling feature.
It maps very well to some useless parameter that can't be handled very well and is just annoying.
100 degrees is where water boils, zero where it freezes.
Or we can do science and run the Kelvin scale in which case 100 degrees is darn cold. Water freezes at 273.15K and boils at 373.15K
Just consider a malware that replaces the PC BIOS with it's own code. Sure it may brick a few, but it may also be a new interesting level of malware.
Write-protect your BIOS:es and you can be a bit safer.
Another interesting thing is that this may be a way around the TPM chip and other copy-protection techniques too.
And beware of special bioses from manufacturers that allows your employer to run keylogging!
I have a Nikon D80 and it has a lot less noise than my friends Canon G9 which has more pixels.
What I really want is a wider range of sensitivity. Both higher sensitivity for photo in the dark, but also a lower sensitivity for some cases where I actually would like to have the blur of motion in bright sunlight.
For the latter cases there are of course filters available, so it's possible to work around it. But there is no way to improve the sensitivity the same way.
As for megapixel race - you can buy a 50 megapixel camera today if you like. It's just a question of money!
And then you can build an extreme camera yourself using a flatbed scanner.
If you do shaping - make sure that you do it in a reasonable way. I.e. increase prio for critical/sensitive services like VoIP (SIP and IAX2) instead of slowing down specific services like bittorrent.
And working with finite resources like coal is a dead end. You will end up with the dirty parts regardless.
And I still call the FAT patent a troll patent.
Almost every software patent is troll patents one way or another because they just causes trouble for software development.
As it is now one company can claim a software patent and claim thousands of man-hours for it while another can do the same development in an afternoon with the right guy.
And if you have a patent attack on Linux it's subsequently also attacking GPL.
I see another problem with this and that is that it shoots a hole in the GPS licensing.
What good is open source if you still have to pay royalties to patent trolls in order to use it?
Have a credibility check page - like checking if someone knows about a local detail that's known by the locals.
"What was the color of the church at Elm Street before 2004?"
And you may want to be careful with IP address filtering since that can result in unexpected disadvantages when a local is out traveling.
And who in their right mind thinks that a foreign nation doesn't already know the existence, location and layout of various bases around the world?
Some bribes or joint ventures later and information exceeding the information available at Google Earth is widespread.
Blurring a satellite or air photo today is just a giveaway since two different distributions never have the same blurring and that tells others that this is a site of interest.