The idea of Google is to provide users with linking information to other content providers rather than to produce anything themselves. They are more doing the "glue" or "pimp" work on the net than providing the end service.
And then - what's the real difference between Google and Pirate Bay? Both are search engines but with the distinction that Google is big and diversified while Pirate Bay is specialized. And Google do have a filter against material that can be seen as "offensive".
You don't need to trust Google all the way. Take your pick from the competition and you see that the main alternatives are either Microsoft Bing (Not Bing Carburetors) and Yahoo. There are others too, listed at This Wikipedia page. OK, Wikipedia can in it's own way be considered a search service. And then there are specialized search engines, but many of those provides only "special interest" result.
In any case - Google has been able to make money from their services one way or another and is for a large company relatively decent. If they are cutting something then it's probably more since they are worried about lawsuits than anything else.
Don't forget the problems you run into when the server decides to spring a leak. Old servers and old cars would have the same level of sludge and oil puddles below them.
Regardless - the existence of DNA doesn't necessarily prove guilt, just that you have a connection of some sort.
Remember that DNA evidence can also prove that you aren't guilty. At least not of that crime.
However since criminals today are aware of DNA they are sometimes trying to contaminate the scene as much as possible just to throw in a few false leads.
I would call in Pascal since it's a language that's fairly easy to understand and learn and it is a lot less prone to strange bugs than C/C++.
Since it's a compiling language you will also find out inconsistencies before you execute. Scripting languages are sometimes filled with time-delayed bombs waiting to go off in inconvenient moments due to undeclared or misdeclared entities.
What you get with Pascal is also a structured way of doing things. The code is easy to read and understand even if you don't know Pascal before. Experience in structure earned from Pascal can easily be translated to C, Java or C#.
Visual Basic is a big NO in my book. Too much problems have been caused by VB already.
And if you are counting CPU cycles - any language with a virtual machine has already lost.
In exceptional conditions I would certainly include what the driver is wearing.
Synthetic material causing ESD sparks is something that can't be ignored.
And be aware that the trigger may be in a box that resides on the CAN bus, but is for something completely different. Like power windows or central locking. Cars are so complex these days that you can never be sure what's wrong - and the workshops have been degraded to code readers and component replacers.
And even more important - the bug may be a combination of software and hardware. Just ask what may happen if the code suddenly jumps to the wrong address. Do they use ECC memories in the electronics? What about a voltage spike? Driver has wrong socks/pants causing a spark that jumps to the OBD-II connector and messes up the CAN bus?
If anything can go wrong - it will. Think outside the box of how bad it can be, then multiply with PI to get a value closer to reality.
So to avoid cross-education in criminality store them in solitary cells without contact and you will get nice drooling types that you can then form to zombies of your liking. Maybe both a bad and a good thing at the same time. The advantage is that they will lose contact with their "friends" and they can't make new "friends" but the downside is that you may end up with permanently drooling fools instead.
It's not necessarily a bad thing to have done things in BASIC, but bad habits can be formed by that language. However the other side of it is that if you first see the bad sides of BASIC then you can recognize the good sides of other languages.
Unfortunately you are still limited to comparing variations of the same apple, so if you want to see if it's a Xeon, Sempron or i7 you want/need many hardware reviews are just too limited.
Obscurity seems to be the life-line for the manufacturers these days and there is no simple way to compare the devices.
Of course it is, but there are a lot of crappy programming done with dropping boxes in Visual Studio and then adding a few event handlers. After a while and a kiloton of changes/programmers involved you will end up with a lot of dead code and items that you don't dare to touch in case something breaks.
Unfortunately the majority of the ad providers do provide all kind of annoying ads - and the ads are often overloading the client computers. Many ads written in Flash or similar technology are frequently taking 100% CPU out of the client computer.
And then - many computers used aren't state of the art or latest model at all. Some are still using old Pentium III laptops just because they still can be used to surf with. And with AdBlock installed they can survive that, but with ads - no way.
Also - don't forget that some people are using dial-up. They may even need to disable the display of images in order to be able to browse the web to the sites they want to see.
The need for adblockers is created by the ad makers themselves and even since not all ads are bad every ad is swept away and collateral damage occurs.
The day the ad makers figure out how to create non-intrusive ads that don't disturb people and still catches the interest we won't need adblockers anymore.
I agree to the fact that it's important to know software libraries to use. That is an essential part of programming today.
And most of the software libraries are bread and butter functionality that is what you as a programmer probably know how to do and can do if necessary but when you get down to earth it's just stupid to redo that work over and over again.
A good programmer shall be able to use a decent set of tools (libraries) and also be able to see the whole of a solution. It doesn't matter if what you do is perfect if it doesn't fit the need of the system.
Don't forget the GUI design approach where the programmers never see a single line of code at all but only throws around objects in a GUI and thinks that they do some programming.
Also set up iptables to only allow for a certain frequency of connection attempts and then block the source address for further connections.
You may of course bypass this in iptables for known addresses, so you will allow known users to log in and still have connections available if they are roaming, but when they are roaming they may get occasionally blocked by the frequency block.
Don't forget that in the case of code there is a large amount of code that's just bread and butter. That code isn't really important in itself - it's just there, used and is probably reusable or recreatable with little effort. What is interesting is how that code is joined together.
Then there is code that is customer specific - it's mission critical for that customer but worthless in any other situation except as a study object for educational purposes.
A third part that sometimes appears is code that does contain some parts of general interest that also is innovative. But this code does not always occur. It is also a fraction, and may contain critical values. The big issue is to identify this little piece of code.
Now - if you as a customer pays for an item you will get the composition of all the components involved. This is what you get. If fragments of that code is reused in another solution - so be it. It's like saying that if a few specific sequence of notes in a work like a piece of music is reappearing in another piece of music you own that other piece too. But there are only so many ways to do things so solutions will reappear and reusing or rewriting is a moot point in reality.
Even if the bottleneck moves from disk to controller the overall performance will improve. So it's not that SSD:s are bad, it's just that the controllers needs to keep up with them.
On the other hand - raid controllers are used for reliability and not just for performance. And in many cases it's a tradeoff - large reliable storage is one thing while high performance is another. Sometimes you want both and then it gets expensive, but if you can live with just one of the alternatives you will get off relatively easy.
And if you really want performance enhancement you may want to look into a mix of SSD:s and ordinary disks. It depends on the actual solution how you can tune it for best performance.
Slashdot Mirror
Porn, cute kittens, weird youtube videos and Slashdot are also contributing.
The idea of Google is to provide users with linking information to other content providers rather than to produce anything themselves. They are more doing the "glue" or "pimp" work on the net than providing the end service.
And then - what's the real difference between Google and Pirate Bay? Both are search engines but with the distinction that Google is big and diversified while Pirate Bay is specialized. And Google do have a filter against material that can be seen as "offensive".
You don't need to trust Google all the way. Take your pick from the competition and you see that the main alternatives are either Microsoft Bing (Not Bing Carburetors) and Yahoo. There are others too, listed at This Wikipedia page. OK, Wikipedia can in it's own way be considered a search service. And then there are specialized search engines, but many of those provides only "special interest" result.
In any case - Google has been able to make money from their services one way or another and is for a large company relatively decent. If they are cutting something then it's probably more since they are worried about lawsuits than anything else.
Don't forget the problems you run into when the server decides to spring a leak. Old servers and old cars would have the same level of sludge and oil puddles below them.
And the weight of the servers will be higher too.
Regardless - the existence of DNA doesn't necessarily prove guilt, just that you have a connection of some sort.
Remember that DNA evidence can also prove that you aren't guilty. At least not of that crime.
However since criminals today are aware of DNA they are sometimes trying to contaminate the scene as much as possible just to throw in a few false leads.
I would call in Pascal since it's a language that's fairly easy to understand and learn and it is a lot less prone to strange bugs than C/C++.
Since it's a compiling language you will also find out inconsistencies before you execute. Scripting languages are sometimes filled with time-delayed bombs waiting to go off in inconvenient moments due to undeclared or misdeclared entities.
What you get with Pascal is also a structured way of doing things. The code is easy to read and understand even if you don't know Pascal before. Experience in structure earned from Pascal can easily be translated to C, Java or C#.
Visual Basic is a big NO in my book. Too much problems have been caused by VB already.
And if you are counting CPU cycles - any language with a virtual machine has already lost.
Year-Month-Day as in the ISO standard it's 2010-03-14.
And the rate - keep it same per hour/distance driven regardless of where the cab goes.
In exceptional conditions I would certainly include what the driver is wearing.
Synthetic material causing ESD sparks is something that can't be ignored.
And be aware that the trigger may be in a box that resides on the CAN bus, but is for something completely different. Like power windows or central locking. Cars are so complex these days that you can never be sure what's wrong - and the workshops have been degraded to code readers and component replacers.
There will always be another bug.
And even more important - the bug may be a combination of software and hardware. Just ask what may happen if the code suddenly jumps to the wrong address. Do they use ECC memories in the electronics? What about a voltage spike? Driver has wrong socks/pants causing a spark that jumps to the OBD-II connector and messes up the CAN bus?
If anything can go wrong - it will. Think outside the box of how bad it can be, then multiply with PI to get a value closer to reality.
And more examples of how wrong things can get can be found here: http://thedailywtf.com/
Compared to most big companies Google isn't that bad.
Compared to governments Google is a saint.
But that doesn't mean that they are right every time. In some way I expect that if they have to leave they do leave behind as little as possible.
What China should fear is instead the risk of having their connection to the rest of the internet cut off or at least limited.
I must go back to use OS8MT or something even more obnoxious then.
So to avoid cross-education in criminality store them in solitary cells without contact and you will get nice drooling types that you can then form to zombies of your liking. Maybe both a bad and a good thing at the same time. The advantage is that they will lose contact with their "friends" and they can't make new "friends" but the downside is that you may end up with permanently drooling fools instead.
This is just another evidence that weapons must be stored unloaded and locked up when not in use.
So I'll say - prosecute the parents till your ears bleed. The right to bear arms is just an excuse for weapon fetishists.
Relate the number of accidental kills with the number of validated kills. Do you want 10 dead for every legal kill?
That's a severe invasion of privacy - have you discussed it with your union representative?
It's baffling how much control that some people seems to want to have over their peers.
Compared to vbScript JavaScript is a blessing, but compared to a fully compiling language with strong typing like Java it sucks.
It's not necessarily a bad thing to have done things in BASIC, but bad habits can be formed by that language. However the other side of it is that if you first see the bad sides of BASIC then you can recognize the good sides of other languages.
And BASIC of today is Python.
Unfortunately you are still limited to comparing variations of the same apple, so if you want to see if it's a Xeon, Sempron or i7 you want/need many hardware reviews are just too limited.
Obscurity seems to be the life-line for the manufacturers these days and there is no simple way to compare the devices.
Of course it is, but there are a lot of crappy programming done with dropping boxes in Visual Studio and then adding a few event handlers. After a while and a kiloton of changes/programmers involved you will end up with a lot of dead code and items that you don't dare to touch in case something breaks.
Unfortunately the majority of the ad providers do provide all kind of annoying ads - and the ads are often overloading the client computers. Many ads written in Flash or similar technology are frequently taking 100% CPU out of the client computer.
And then - many computers used aren't state of the art or latest model at all. Some are still using old Pentium III laptops just because they still can be used to surf with. And with AdBlock installed they can survive that, but with ads - no way.
Also - don't forget that some people are using dial-up. They may even need to disable the display of images in order to be able to browse the web to the sites they want to see.
The need for adblockers is created by the ad makers themselves and even since not all ads are bad every ad is swept away and collateral damage occurs.
The day the ad makers figure out how to create non-intrusive ads that don't disturb people and still catches the interest we won't need adblockers anymore.
I agree to the fact that it's important to know software libraries to use. That is an essential part of programming today.
And most of the software libraries are bread and butter functionality that is what you as a programmer probably know how to do and can do if necessary but when you get down to earth it's just stupid to redo that work over and over again.
A good programmer shall be able to use a decent set of tools (libraries) and also be able to see the whole of a solution. It doesn't matter if what you do is perfect if it doesn't fit the need of the system.
Don't forget the GUI design approach where the programmers never see a single line of code at all but only throws around objects in a GUI and thinks that they do some programming.
Also set up iptables to only allow for a certain frequency of connection attempts and then block the source address for further connections.
You may of course bypass this in iptables for known addresses, so you will allow known users to log in and still have connections available if they are roaming, but when they are roaming they may get occasionally blocked by the frequency block.
Don't forget that in the case of code there is a large amount of code that's just bread and butter. That code isn't really important in itself - it's just there, used and is probably reusable or recreatable with little effort. What is interesting is how that code is joined together.
Then there is code that is customer specific - it's mission critical for that customer but worthless in any other situation except as a study object for educational purposes.
A third part that sometimes appears is code that does contain some parts of general interest that also is innovative. But this code does not always occur. It is also a fraction, and may contain critical values. The big issue is to identify this little piece of code.
Now - if you as a customer pays for an item you will get the composition of all the components involved. This is what you get. If fragments of that code is reused in another solution - so be it. It's like saying that if a few specific sequence of notes in a work like a piece of music is reappearing in another piece of music you own that other piece too. But there are only so many ways to do things so solutions will reappear and reusing or rewriting is a moot point in reality.
Even if the bottleneck moves from disk to controller the overall performance will improve. So it's not that SSD:s are bad, it's just that the controllers needs to keep up with them.
On the other hand - raid controllers are used for reliability and not just for performance. And in many cases it's a tradeoff - large reliable storage is one thing while high performance is another. Sometimes you want both and then it gets expensive, but if you can live with just one of the alternatives you will get off relatively easy.
And if you really want performance enhancement you may want to look into a mix of SSD:s and ordinary disks. It depends on the actual solution how you can tune it for best performance.
Ah - that would mean that the patent office is located in a building filled with asbestos.
Seems like it would be a potential health hazard to work there then. So time for a relocation!