or Debian, and apt-get update. Whatever your distribution of choice is, there is likely an easy way to upgrade. emerge, apt-get, yum, up2date, red-carpet, etc, etc, etc.
They did have LOTR running on some IMAX screens. We saw it twice that way. I don't know if it was the 35mm film projected or something made specifically for the IMAX, but either way it was excellent.
I've been working at the company in question, ditto.com (formerly known as Arriba Soft) for several years, designing and building the technology that lead to this. The judge ruled against Ditto on one point, that being the display of the full-sized image. I'd like to clarify what exactly that means, though.
All thumbnails displayed are served from our own servers, not using the bandwidth of the sites being displayed in our search results. The issue that came into play was what happened when a user clicked on a thumbnail. When that happened, we would pop up two windows (as ugly as that is). One would contain just the full-sized image hosted on that site's server. The second window would be the actual page that the image was found on. Because of the judge's ruling, we no longer pop up the full-sized image, just the page that the image was found on.
I don't think this ruling will have much impact on us and others like Google who are providing the same type of service. The judge ruled upheld the previous ruling about fair use of thumbnails, which is the primary concern of this business.
To be more specific, since I work at the company in question, the issue that the judge ruled against us on was poping up the full-size image *if*, and only *if*, the user clicked on the thumbnail. Not only did we pop up the full-sized image, we popped up the original page that the image was found on, thus driving traffic to that persons site. The thumbnails are stored on our server, so unless the user actually clicked on the image, it would use no bandwidth of his or any other webmasters site.
For the last 5+ years, I've coded in VB, C, C++, Java, perl, php, assembler, and others that I can't remember ( or don't want to ).
Each language has it's strengths and weaknesses, without exception. Yes, VB does have some drawbacks. It is not portable. It doesn't have certain OOP features *yet* ( See VB7 ). It does offer rapid development, native 32-bit _compiled_ code ( VB hasn't been interpreted for a couple years now ) that, when _well-written_, can run just as well as an application written in MSVC++.
** Note ** I'm not making any comment in regards to the stability of the OS, which can play devils advocate for _any_ application.
I'm not claiming that VB is as robust as other languages ( perl, c++, java ) but _in my experience_ I have found that if VB isn't capable of performing a task, it will easily use a component written in to the COM specification. That's a strong features of VB. It can use any COM component, and you can write COM objects in many languages, including Delphi and C++. You can even access CORBA objects!
Applications can be written poorly in _any_ language.
Slashdot Mirror
Knoppix can do that and a whole lot more.
Knoppix Hacks
Virus scanning, emergency router, write to NTFS, even fire up a mythtv box.
or Debian, and apt-get update. Whatever your distribution of choice is, there is likely an easy way to upgrade. emerge, apt-get, yum, up2date, red-carpet, etc, etc, etc.
He did have them on his website, and he refused to put up a robots.txt, even though we told him what it was and what it was used for.
That picture was taken solely for showing the glove in action. 80% of the time I use my laptop I have a seperate keyboard and mouse.
They did have LOTR running on some IMAX screens. We saw it twice that way. I don't know if it was the 35mm film projected or something made specifically for the IMAX, but either way it was excellent.
...to Johnny 5
I've been working at the company in question, ditto.com (formerly known as Arriba Soft) for several years, designing and building the technology that lead to this. The judge ruled against Ditto on one point, that being the display of the full-sized image. I'd like to clarify what exactly that means, though.
All thumbnails displayed are served from our own servers, not using the bandwidth of the sites being displayed in our search results. The issue that came into play was what happened when a user clicked on a thumbnail. When that happened, we would pop up two windows (as ugly as that is). One would contain just the full-sized image hosted on that site's server. The second window would be the actual page that the image was found on. Because of the judge's ruling, we no longer pop up the full-sized image, just the page that the image was found on.
I don't think this ruling will have much impact on us and others like Google who are providing the same type of service. The judge ruled upheld the previous ruling about fair use of thumbnails, which is the primary concern of this business.
To be more specific, since I work at the company in question, the issue that the judge ruled against us on was poping up the full-size image *if*, and only *if*, the user clicked on the thumbnail. Not only did we pop up the full-sized image, we popped up the original page that the image was found on, thus driving traffic to that persons site. The thumbnails are stored on our server, so unless the user actually clicked on the image, it would use no bandwidth of his or any other webmasters site.
I must say it heartens me to see overwhelming favor for the Search Engines in this matter. As long as Search Engines:
a) honor robots.txt
b) provide the user with a mechanism to remove their images
c) Provides the searcher not only with the picture, but the page it was found on as well
Ditto.com's spyder does this (I know, I work there and wrote it) and GoogleBot does the same.
For the last 5+ years, I've coded in VB, C, C++, Java, perl, php, assembler, and others that I can't remember ( or don't want to ).
Each language has it's strengths and weaknesses, without exception. Yes, VB does have some drawbacks. It is not portable. It doesn't have certain OOP features *yet* ( See VB7 ). It does offer rapid development, native 32-bit _compiled_ code ( VB hasn't been interpreted for a couple years now ) that, when _well-written_, can run just as well as an application written in MSVC++.
** Note ** I'm not making any comment in regards to the stability of the OS, which can play devils advocate for _any_ application.
I'm not claiming that VB is as robust as other languages ( perl, c++, java ) but _in my experience_ I have found that if VB isn't capable of performing a task, it will easily use a component written in to the COM specification. That's a strong features of VB. It can use any COM component, and you can write COM objects in many languages, including Delphi and C++. You can even access CORBA objects!
Applications can be written poorly in _any_ language.
IMHO,
http://www.battleaxe.net