The difference is that if you are put in jail for contempt you will be higher on the ranking scale in the jail than if you are put in jail for child pornography.
The difference is like between cleaning the toilet or being the toilet.
The governments version of waterboarding is to let the IRS do the dirty work and make life miserable for you by digging through your tax filings and rejecting things you filed for being insufficient or whatever.
And neither are the programmers of history really guilty.
The big issue here is that what started out as something small and neat has been growing over time with different programmers involved. This is caused by various input from different areas within a company and after a while the structure that once was consistent is now degraded and there is a lot of dead code. And the evolution of the language has also contributed because what once was the only way to do something can now be done in three different ways.
But this is still nothing that's unique to Perl. Most languages suffers from this problem, and the problem arises from the fact that there is often no compile-time verification of the code to find any inconsistencies between modules.
Languages with strong and static typing are a bit better to cover for problems like these, since they can verify the worst problems at compile time. Additional tools like Findbugs and Splint can also help.
Weak and dynamic typing are fatal problems waiting to happen. You may claim that it's resolved by better testing, but that drives up the cost since the iterations will be longer. And some cases are missed during tests because that code is only executed in rare cases.
So if anything - what should be hated are weakly and dynamically typed programming languages. Regardless of what the language is called. But we can't live completely without them either since they come in handy from time to time. But at least the usage shall be limited to keep things safe.
And back to the issue where code has evolved over time - it is sometimes the best to actually bring together a set of engineers that has to analyze the functionality of an existing system and then rewrite the whole system in a consistent way using a language like Ada, Java or C#. In some cases special languages may be needed because there can be functionality that can be best expressed in Erlang or Fortran. This means that it's important to not be too obstinate about using a single language for development. Select one main language and make it interact with other languages when needed.
Lines of code is of course not a good measurement of the complexity of an application or the task ahead. A programmer may use weeks to code something that's a 1000 lines long, but other parts can be 5000 lines in a day.
Comments in code are useful - but only to a degree, too much comments will just obscure the code instead.
Breaking down code into reasonable modules is also important. Tools like Eclipse have some refactoring capabilities which allows you to actually break out a certain code segment into a new method in Java.
And yet another factor that's easily forgotten is that there are three types of systems;
1. Architect designed systems.
2. Hacks.
3. Evolved systems. Both 1 and 2 can converge into an evolved system, but the evolution depends strongly on the programmers involved and their experience. An experienced programmer can actually restructure a hack into a structured evolved system, but inexperienced programmers can easily cause a designed system to be evolved into an unstructured evolved system. Available tools and methods also bear their share for the quality of an evolved system.
Weed is as addictive as alcohol. And it's sneaky too since heavy users can get an occasional ruse from it on the odd occasions that they haven't had a joint. The catch is that the drug is dissolving into the fat tissues of the body and sometimes it can get released at inconvenient moments.
The question was to verify if and how many alternatives that existed. So far I have only seen Gnash, but if there were others, then it wouldn't have been a waste of time to ask the question.
The point I was trying to make was to attempt to collect if there was any more alternatives, sometimes you can actually strike new information even at Slashdot.
So there is no version of Flash that is open source then?
The disadvantage of not being able to play Flash is mostly on sites like YouTube. But some other sites are also using Flash for the interesting content.
So the big question is - is it possible to implement a Flash player for Linux that's open source?
The problem with going public with this kind of information is also that the nastiest serial killers - they who plan their killings - actually takes notice and makes sure that their pattern is weird enough to mess up any logical conclusions from their pattern.
Of course - sooner or later they are probably making a mistake that leads to their downfall, but by creating a offbeat pattern they can lead investigators down several blind alleys.
This is however not limited to serial killers, but also other kinds of crime. Organized crime are all to aware already of methods used by law enforcement. They know that they are being watched so they run decoys etc.
It's understandable for the point that it was on a very small area, but scaled up to a national area the idea isn't really bad.
But we actually have this today, but by using other kinds of technology - weather satellites and image processing.
I suspect that the real point there wasn't really the sensor network but the ability to actually collect and process the information in a meaningful way. Today we do that on a daily basis, but back then it was to test a concept.
I suspect that they will call off that as being under the noise level.
And even then they will also need to detect not only if they are on, but also the amount of water they are removing. This is a more interesting thing to analyze since the friction between glass and rubber also comes into play.
One factor that may be more of concern is if someone has made a mistake with their lawn watering system, because then every car passing by will turn on their wipers - and you will have a local rain.
But even then I also suspect that they will correlate this with the precipitation radar and see that there is in fact no rain in the area.
We actually have 3G on 450MHz (auto-translated) here in Sweden too. This is a really good solution in rural areas due to the excellent coverage. The 450MHz band was earlier used by the old 1G net NMT.
And having 900/1800 MHz also makes sense compared to the offbeat 850/1900 in USA, since the 900/1800 are pure multiples and allows for better antenna technology.
The advantage with higher frequencies is that you have better bandwidth which in turn means that you can get a higher data transfer rate. But if the reception is bad it doesn't help.
It's probably in the same way you can love a beautiful woman (man) even though that person is stupid as a rock.
Apple is hard working on our feelings and not on the logic part of our minds.
Microsoft is selling the technology on their name and has at least some level of functionality, even though their mobile devices has about the same stability as Windows for Workgroups 3.11. - Which means that they usually work as long as you don't do too strange things with them.
I don't know if this is a joke or not... The general drive to push products at an increasing speed forces the manufacturers to push out sub-standard devices on the market.
And many of the devices are programmed mainly in C/C++ which we all know is a double-edged technology since it gives good performance but it is also prone to weird bugs like wild pointers etc.
And from another source there have been information that the Infineon chipset never had been tested in a production environment.
And if it is the chipset it may be possible that a software upgrade is insufficient.
So I suspect that we haven't heard the last of this story yet.
At least - this is the danger of being the first on new technology, and I'm happy that I didn't buy the iPhone. Even if it is a good design it seems to be more design and less function.
Slashdot Mirror
The difference is that if you are put in jail for contempt you will be higher on the ranking scale in the jail than if you are put in jail for child pornography.
The difference is like between cleaning the toilet or being the toilet.
The governments version of waterboarding is to let the IRS do the dirty work and make life miserable for you by digging through your tax filings and rejecting things you filed for being insufficient or whatever.
Perl is in itself neither good or bad.
And neither are the programmers of history really guilty.
The big issue here is that what started out as something small and neat has been growing over time with different programmers involved. This is caused by various input from different areas within a company and after a while the structure that once was consistent is now degraded and there is a lot of dead code. And the evolution of the language has also contributed because what once was the only way to do something can now be done in three different ways.
But this is still nothing that's unique to Perl. Most languages suffers from this problem, and the problem arises from the fact that there is often no compile-time verification of the code to find any inconsistencies between modules.
Languages with strong and static typing are a bit better to cover for problems like these, since they can verify the worst problems at compile time. Additional tools like Findbugs and Splint can also help.
Weak and dynamic typing are fatal problems waiting to happen. You may claim that it's resolved by better testing, but that drives up the cost since the iterations will be longer. And some cases are missed during tests because that code is only executed in rare cases.
So if anything - what should be hated are weakly and dynamically typed programming languages. Regardless of what the language is called. But we can't live completely without them either since they come in handy from time to time. But at least the usage shall be limited to keep things safe.
And back to the issue where code has evolved over time - it is sometimes the best to actually bring together a set of engineers that has to analyze the functionality of an existing system and then rewrite the whole system in a consistent way using a language like Ada, Java or C#. In some cases special languages may be needed because there can be functionality that can be best expressed in Erlang or Fortran. This means that it's important to not be too obstinate about using a single language for development. Select one main language and make it interact with other languages when needed.
Lines of code is of course not a good measurement of the complexity of an application or the task ahead. A programmer may use weeks to code something that's a 1000 lines long, but other parts can be 5000 lines in a day.
Comments in code are useful - but only to a degree, too much comments will just obscure the code instead.
Breaking down code into reasonable modules is also important. Tools like Eclipse have some refactoring capabilities which allows you to actually break out a certain code segment into a new method in Java.
And yet another factor that's easily forgotten is that there are three types of systems;
1. Architect designed systems.
2. Hacks.
3. Evolved systems.
Both 1 and 2 can converge into an evolved system, but the evolution depends strongly on the programmers involved and their experience. An experienced programmer can actually restructure a hack into a structured evolved system, but inexperienced programmers can easily cause a designed system to be evolved into an unstructured evolved system. Available tools and methods also bear their share for the quality of an evolved system.
But maybe you may charge for light/heat/cooling/privacy?
Door won't close until $1 is inserted.
But the toilet will work, so anybody in need may use it. But not closing the door may constitute indecent exposure.
Just wait until a relative of the mayor gets stuck in the traffic on the way to the hospital and dies.
Well - Hitler and Stalin were effective to some degree, but the cost wasn't acceptable. And by that I mean the cost in lives consumed.
And it didn't end well for Hitler. And Stalin was paranoid, so I suspect that he actually had his penalty too, but not officially.
Don't confuse them with the suicide booths then.
Which makes the drug addictive, just because it's by proxy doesn't matter.
Weed is as addictive as alcohol. And it's sneaky too since heavy users can get an occasional ruse from it on the odd occasions that they haven't had a joint. The catch is that the drug is dissolving into the fat tissues of the body and sometimes it can get released at inconvenient moments.
The insight here was that they were self-cleaning so no need for a janitor.
But maybe an option should have been that if somebody was there for more than 30 minutes then the self cleaning should have started.
The question was to verify if and how many alternatives that existed. So far I have only seen Gnash, but if there were others, then it wouldn't have been a waste of time to ask the question.
It may not be the ordering option that's the problem, it may be accessing today's menu that's the problem.
Like - what shall we have for lunch?
The point I was trying to make was to attempt to collect if there was any more alternatives, sometimes you can actually strike new information even at Slashdot.
Now it's just time to go and invalidate a lot of other too plain trademarks. Just think of one that we use daily...
So there is no version of Flash that is open source then?
The disadvantage of not being able to play Flash is mostly on sites like YouTube. But some other sites are also using Flash for the interesting content.
So the big question is - is it possible to implement a Flash player for Linux that's open source?
The problem with going public with this kind of information is also that the nastiest serial killers - they who plan their killings - actually takes notice and makes sure that their pattern is weird enough to mess up any logical conclusions from their pattern.
Of course - sooner or later they are probably making a mistake that leads to their downfall, but by creating a offbeat pattern they can lead investigators down several blind alleys.
This is however not limited to serial killers, but also other kinds of crime. Organized crime are all to aware already of methods used by law enforcement. They know that they are being watched so they run decoys etc.
It's understandable for the point that it was on a very small area, but scaled up to a national area the idea isn't really bad.
But we actually have this today, but by using other kinds of technology - weather satellites and image processing.
I suspect that the real point there wasn't really the sensor network but the ability to actually collect and process the information in a meaningful way. Today we do that on a daily basis, but back then it was to test a concept.
Just remove the battery and you will be fine. Add a tin foil hat to be sure.
I suspect that they will call off that as being under the noise level.
And even then they will also need to detect not only if they are on, but also the amount of water they are removing. This is a more interesting thing to analyze since the friction between glass and rubber also comes into play.
One factor that may be more of concern is if someone has made a mistake with their lawn watering system, because then every car passing by will turn on their wipers - and you will have a local rain.
But even then I also suspect that they will correlate this with the precipitation radar and see that there is in fact no rain in the area.
We actually have 3G on 450MHz (auto-translated) here in Sweden too. This is a really good solution in rural areas due to the excellent coverage. The 450MHz band was earlier used by the old 1G net NMT.
And having 900/1800 MHz also makes sense compared to the offbeat 850/1900 in USA, since the 900/1800 are pure multiples and allows for better antenna technology.
The advantage with higher frequencies is that you have better bandwidth which in turn means that you can get a higher data transfer rate. But if the reception is bad it doesn't help.
That's interesting, but I'm not very surprised!
And get an answer from HP?
It's probably in the same way you can love a beautiful woman (man) even though that person is stupid as a rock.
Apple is hard working on our feelings and not on the logic part of our minds.
Microsoft is selling the technology on their name and has at least some level of functionality, even though their mobile devices has about the same stability as Windows for Workgroups 3.11. - Which means that they usually work as long as you don't do too strange things with them.
I don't know if this is a joke or not... The general drive to push products at an increasing speed forces the manufacturers to push out sub-standard devices on the market.
And many of the devices are programmed mainly in C/C++ which we all know is a double-edged technology since it gives good performance but it is also prone to weird bugs like wild pointers etc.
And from another source there have been information that the Infineon chipset never had been tested in a production environment.
And if it is the chipset it may be possible that a software upgrade is insufficient.
So I suspect that we haven't heard the last of this story yet.
At least - this is the danger of being the first on new technology, and I'm happy that I didn't buy the iPhone. Even if it is a good design it seems to be more design and less function.