But the whole United States is locked in a situation where hope and optimism is starting to get rare.
The Democrats and Republicans seems to be blocking each other as much as possible causing a deadlock. Today it seems like the creationists are taking over step by step.
That's what the problem is with games and TV shows in the US today. Kids are presented with violence all the time but when a nipple is flashed there's an outrage.
Prices in the US has often been lower than in Europe.
But consider another thing - the sales tax in New Hampshire is non-existent (or very low in some cases), and other states in the US has a higher sales tax, so it may just be a matter of tax evasion.
Buying stuff in New Hampshire is a nice deal when you normally live in a country with 25% VAT.
Just consider the fact that much of the electronics that are placed under an embargo can reach the targets anyway. The embargo is about as effective as shoveling boiling water with a colander. North Korea has been successful in both producing a nuke and a rocket even though they are under embargo. Even if the rocket obviously works like crap it's not really worse than anything the US had in the beginning.
And Cuba is probably one of the countries in the world that would suffer the least from a severe oil shortage.
What really would mess those countries up would be to drop the embargo and instead clutter them with Gameboys and whatnot.
The most likely part is that those phones would go to China. (Guess where they are assembled).
On Cuba they may not even be possible to use, same in North Korea or Burma, and if they are going to Iran - well, the possibility to hack an iPhone to control missiles may be there, but I would say that it would be easier to use an Android device or a laptop, and both can be purchased at a decent price outside the US. Apple on the other hand is doing what they can to keep demand up. And it would probably be more of an import issue at the destination than an export issue from the US.
If the compiler was requiring the handling of all the thrown Exceptions you would be forced to implement them. What if the "ToString()" method is overridden and can throw an Exception that it normally doesn't? Do you always check that in the manual? Most people don't since it should just present a string representation, but suddenly things goes "boom", and if the Exception isn't handled because it's not forced upon the developer it's way too easy to miss.
You forget that not all manuals are good at defining the possible Exceptions thrown and sometimes they aren't even well documented. Even worse is the case when Exceptions are thrown by badly documented third party libraries because the Exception is thrown by something that they call.
One experience I also have is that the Exception handling in C# is horrible because it's slow. And that can cause code that's more complicated than necessary. E.g. when adding data to a Dictionary class you can have two approaches - either first check if the item exists or expect an Exception to be thrown. Going the Exception path is good enough when you have interactive data but when you do batch processing of data it will really slow down things. And you can't entirely exclude the Exception handling anyway because you may still encounter something that gives an exception in your path - like when two different items gives the same hash code and the Dictionary class gives you an Exception anyway. So there you have code duplication and some headache of "how do I test that".
If on the other hand the compiler forces you to handle the Exceptions then you will implement the Exception handling one way or another. So my post was more a kick at the fact that C# isn't properly declaring Exceptions than anything else. Having developed both Java and C# I would say that C# lacks a lot of stuff that should be there and permits a lot of things that allows for sloppy coding. C# is Java for Basic coders and if you have the culture from coding Basic and not the culture from coding a strongly typed language and required Exception handling you end up with ignored Exceptions and stuff like that. People do read the manual to the extent that they do see what the in and out parameters are - or goes for the supported help suggestions in the IDE and are set with that. Do you really refer to the manual for every method you call - like "ToString()"? What if the class you use overrides that method and it suddenly throws an unexpected Exception?
Log4J / Log4Net has done more for software development than many other kinds of error handling. And I agree that capturing general exceptions to begin with and then when the need rises add more specific exceptions but still keep the general as last resort. Over time you can improve the system, but it takes time.
And you can only catch errors if you know that they will appear.
One example is when developing in C# you never know which exceptions to except unless you waste a lot of time reading the documentation for every class that you use or resort to do a general catch of Exception and try to guess what's best to do. In Java the amount of "blind" exceptions thrown are limited to the Runtime exceptions that you can get - which is bad enough, especially if some esoteric third party developer throws their exceptions as extensions of the RuntimeException.
Exceptions are all good and fine but sometimes it's good enough with a return value of zero when an empty string is converted to a number. Even classic Basic had a crude exception handling in the "On Error Goto" statement. But every time you have an error you need to do some cleanup or take an alternate path. Just continuing blindly will give you a bad headache.
Catch and re-throw has it's uses too, but it shall be used with some care. It may be useful when you run a client/server solution where you don't want to expose every exception up to the client since the client may then need to link third party libraries that you don't want the client to carry. Especially if there are two vendors, one on the server side and one on the client side.
The percentage of Aspberger's on Slashdot is probably higher than average.
And it may be a form of Autism, but sometimes it's tough to generalize too much since that will just cause psychiatrists and others to look at the person and consider him/her "normal" compared to the cases they work with instead of handing over you to someone that specializes in cases of the milder forms.
And drop the $5 bill too when you are at it. Compare with many other countries and you see that even that denomination is often represented by coins these days.
You may write whatever you like on the content label. But you will take a risk that it's taken literally.
Like the person that sent his photos in a mail protected by a 1/2 inch aluminum plate and then wrote on the content label "bend this if you can" - it arrived to the recipient neatly bent to 90 degrees...
In that case if you need to provide security you can run by obfuscation and steganography. It will only work for small amounts of carried data, but that may be enough.
Slashdot Mirror
But the whole United States is locked in a situation where hope and optimism is starting to get rare.
The Democrats and Republicans seems to be blocking each other as much as possible causing a deadlock. Today it seems like the creationists are taking over step by step.
Maybe there shall be a separation between physical net and carrier service and make sure that no operator gets exclusive right to a fiber network.
That's what the problem is with games and TV shows in the US today. Kids are presented with violence all the time but when a nipple is flashed there's an outrage.
Just look at the outrage caused by Janet Jackson.
Spanish would be the first non-english language to pick if you are a native English speaker.
But understanding the Metric system is also important.
All completely possible. ...anyone switching to opendns yet?
I did set up my own DNS server instead - free from both OpenDNS and the ISPs filtered version.
You only need a Linux box and Bind.
I was offered that several months ago. But the downside is the monthly cost.
Prices in the US has often been lower than in Europe.
But consider another thing - the sales tax in New Hampshire is non-existent (or very low in some cases), and other states in the US has a higher sales tax, so it may just be a matter of tax evasion.
Buying stuff in New Hampshire is a nice deal when you normally live in a country with 25% VAT.
Just consider the fact that much of the electronics that are placed under an embargo can reach the targets anyway. The embargo is about as effective as shoveling boiling water with a colander. North Korea has been successful in both producing a nuke and a rocket even though they are under embargo. Even if the rocket obviously works like crap it's not really worse than anything the US had in the beginning.
And Cuba is probably one of the countries in the world that would suffer the least from a severe oil shortage.
What really would mess those countries up would be to drop the embargo and instead clutter them with Gameboys and whatnot.
The most likely part is that those phones would go to China. (Guess where they are assembled).
On Cuba they may not even be possible to use, same in North Korea or Burma, and if they are going to Iran - well, the possibility to hack an iPhone to control missiles may be there, but I would say that it would be easier to use an Android device or a laptop, and both can be purchased at a decent price outside the US. Apple on the other hand is doing what they can to keep demand up. And it would probably be more of an import issue at the destination than an export issue from the US.
They were probably just extra pi$$ed because they were called from a nice lunch at Dunkin Donuts or so...
And the reality is that the law is obsolete - cryptography isn't best just because it's built in the US.
What this proves is that Apple is jacking up the price and availability more on some markets than other.
I would vote for 90000.
If the compiler was requiring the handling of all the thrown Exceptions you would be forced to implement them. What if the "ToString()" method is overridden and can throw an Exception that it normally doesn't? Do you always check that in the manual? Most people don't since it should just present a string representation, but suddenly things goes "boom", and if the Exception isn't handled because it's not forced upon the developer it's way too easy to miss.
You forget that not all manuals are good at defining the possible Exceptions thrown and sometimes they aren't even well documented. Even worse is the case when Exceptions are thrown by badly documented third party libraries because the Exception is thrown by something that they call.
One experience I also have is that the Exception handling in C# is horrible because it's slow. And that can cause code that's more complicated than necessary. E.g. when adding data to a Dictionary class you can have two approaches - either first check if the item exists or expect an Exception to be thrown. Going the Exception path is good enough when you have interactive data but when you do batch processing of data it will really slow down things. And you can't entirely exclude the Exception handling anyway because you may still encounter something that gives an exception in your path - like when two different items gives the same hash code and the Dictionary class gives you an Exception anyway. So there you have code duplication and some headache of "how do I test that".
If on the other hand the compiler forces you to handle the Exceptions then you will implement the Exception handling one way or another. So my post was more a kick at the fact that C# isn't properly declaring Exceptions than anything else. Having developed both Java and C# I would say that C# lacks a lot of stuff that should be there and permits a lot of things that allows for sloppy coding. C# is Java for Basic coders and if you have the culture from coding Basic and not the culture from coding a strongly typed language and required Exception handling you end up with ignored Exceptions and stuff like that. People do read the manual to the extent that they do see what the in and out parameters are - or goes for the supported help suggestions in the IDE and are set with that. Do you really refer to the manual for every method you call - like "ToString()"? What if the class you use overrides that method and it suddenly throws an unexpected Exception?
Of course - Java isn't perfect either.
OK, then we have the following:
0 = Go to 200.
=0 = Go to 300.
NaN = Go to 400.
Of course - the NaN was not implemented in classic Basic.
Log4J / Log4Net has done more for software development than many other kinds of error handling. And I agree that capturing general exceptions to begin with and then when the need rises add more specific exceptions but still keep the general as last resort. Over time you can improve the system, but it takes time.
And you can only catch errors if you know that they will appear.
One example is when developing in C# you never know which exceptions to except unless you waste a lot of time reading the documentation for every class that you use or resort to do a general catch of Exception and try to guess what's best to do. In Java the amount of "blind" exceptions thrown are limited to the Runtime exceptions that you can get - which is bad enough, especially if some esoteric third party developer throws their exceptions as extensions of the RuntimeException.
Exceptions are all good and fine but sometimes it's good enough with a return value of zero when an empty string is converted to a number. Even classic Basic had a crude exception handling in the "On Error Goto" statement. But every time you have an error you need to do some cleanup or take an alternate path. Just continuing blindly will give you a bad headache.
Catch and re-throw has it's uses too, but it shall be used with some care. It may be useful when you run a client/server solution where you don't want to expose every exception up to the client since the client may then need to link third party libraries that you don't want the client to carry. Especially if there are two vendors, one on the server side and one on the client side.
CB radio and HAM radio will still use those tools.
And in any case 10Mbps is a lot more than 0Mbps while 100Mbps is just ten times faster than 10Mbps.
The deep-frozen yellow garden hose! :)
And I have an old DELNI stashed away too, but I doubt I will ever need it.
Many companies here uses only mobile phones except for faxes and conference rooms.
Add to it that as soon as you break the seal the mold spores will have access to the bread and it ages no differently from ordinary bread.
But for bread and other items of food that you bring with you on a camping trip this may be great.
The percentage of Aspberger's on Slashdot is probably higher than average.
And it may be a form of Autism, but sometimes it's tough to generalize too much since that will just cause psychiatrists and others to look at the person and consider him/her "normal" compared to the cases they work with instead of handing over you to someone that specializes in cases of the milder forms.
OK, everyone pays in gold instead.
And drop the $5 bill too when you are at it. Compare with many other countries and you see that even that denomination is often represented by coins these days.
You may write whatever you like on the content label. But you will take a risk that it's taken literally.
Like the person that sent his photos in a mail protected by a 1/2 inch aluminum plate and then wrote on the content label "bend this if you can" - it arrived to the recipient neatly bent to 90 degrees...
In that case if you need to provide security you can run by obfuscation and steganography. It will only work for small amounts of carried data, but that may be enough.