Oh, I also forgot to mention that the term audiophile in the article is never used in reference to sound quality that iPod provides.
In one instance, it attributes the stereo line-out output as an audiophile future because this bypasses the end amplifier which is typically much more noisy than an external amplifier that you would want to hook up your iPod to.
I have advice for you, go out there and buy it used from some moron who wants the i470 because Cannon says so. So you buy the i450 from him and you'll even do him a favor.
Re:Put more information on your website!
on
KISS
·
· Score: 1
Well, your argument is sound, but you are wrong on saying "Plus they did it knowing that it would take years to pay off in additional sales.".
Assuming all your other numbers are correct and "several hundred" manuals means 1000 and "several hundred pages" means 1000, you have 1M pages. On 5 scanners like this for $18,000 each, you will receive a theoretical performance of 900 images per minute, which means a total of 18.5 hours for 1M documents, not considering the daily duty cycle.
For money that is worth a salary of 3 people (two-salary equivalent for the above-equipment and some extra money for a man to operate this), you get performance and manpower to scan, categorize, and post all the manuals that you need in less than a one quarter.
And I haven't even started talking about cost if you are outsourcing this type of a job to India...
Bottom line, if it didn't generate revenue, a company wouldn't do it. So even though you call Yamaha a "good" company in a sense that they have values beyond making money, that is misleading. I personally haven't worked at a corporation that is out there for just "being good"...
Plus you forgot to point out that the benefit of.NET is in its interoperability with all Microsoft's "prior art", consequently making.NET a platform suitable and pretty evolved to develop enterprise-level services.
Speaking of prior art, here is an interesting place, you might want to look up whether IBM hasn't by any chance published something that could prevent M$ from this frivolous patent on the basis that prior art exists: http://www.priorartdatabase.com/
Great, so you presented examples of what I mentioned earlier anyway, i.e. specific nonconformities IE has when it comes to CSS.
While I might partially agree that benevolence only enables idiots who can't write proper HTML get their work across as 'looking okay' in IE. However, arguing that this benevolence is a bad thing is like saying that a college kid passes the course either by full score or fails.
All your examples were CSS conformance and nothing else, while in great-grandparent, you claim that IE does not conform to latest standards.
I am contesting your use of plural when saying "standards". I hope you were joking...
I am sorry, but you forgot to mention any facts. I am aware of nonconformities to the latest CSS standards.
However, as a browser, it is one of the browsers that will render even partially received information (or broken HTML) correctly. Apart from efficiency issues (memory footprint when accessing complex documents in several windows and/or instances), which are not necessarily directly related to web developers (GUI designers and (D)HTML kiddies), there are very few Web-developer-unfriendly issues with IE.
You haven't bothered to mention any, so enlighten us.
to say that "[Microsfot] SQL Server [...] has an archetecture that virus and worm writers have been able to exploit" is simply pathetically desprate misleading of the audience. Here is why.
The Slammer worm has used a vulnerability that was NOT an architectural design flaw across the product. It was a simple stack buffer overflow in an implementation of the SQL Resolution Service.
On a seemingly unrelated topic, here is a plethora of buffer overflow vulnerabilities of Oracle from some time ago. How much mass media attention did that receive. Close to none, because it doesn't pay the media in advertising revenue to show an expert talking tech about buffer overflows and authorization headers. But does pay off to create a bombastic news report on a big-time screw-up of the largest software company in the world.
I am sorry to bust your balls, but I do recall several instances of similar problems such as an Apache worm on FreeBSD. I am not arguing that Apache et al. have more flaws, I am just pointing out that everyone who has coding skills prefers to explore IIS's quality rather than some Apache's because of simple "I can pick on the weaker guy easier" predatory concept from kindergarten.
using a technique that I would call Reverse Replicated OCR.
Imagine you created a mechanism that takes those obscure-looking "rand0/^\ w0rd$" and converts them to legible "random words". Easier said than done? Well, if you converted the obscure text to an image, blurred each letter based on what other letter surrounds them (e.g. "^" would be blurred more than "n" because "^" is surrounded by "/" and "\"), you would essentially get, in my opinion, an image that actually looks more legible. "/^\" would collapes into an "M" in the eyes of an OCR engine.
The proposition to make it OCR-based is just an implementation, but the idea is to have a parametric system that realizes that "/^\" can be mapped to "M" for example.
Since this whole proposal probably sounds obvious, one might expect this will be implemented pretty soon.
When it comes to the excerpts from E.A. Poe's works or other continuous sensible text, this will be a much bigger of a problem to tackle. I would even dare to say that this is where we will see spam filter circumvention techniques to be advancing towards.
Slashdot Mirror
Oh, I also forgot to mention that the term audiophile in the article is never used in reference to sound quality that iPod provides.
In one instance, it attributes the stereo line-out output as an audiophile future because this bypasses the end amplifier which is typically much more noisy than an external amplifier that you would want to hook up your iPod to.
You know what those who just repeat what they hear are called...
I have advice for you, go out there and buy it used from some moron who wants the i470 because Cannon says so. So you buy the i450 from him and you'll even do him a favor.
Well, your argument is sound, but you are wrong on saying "Plus they did it knowing that it would take years to pay off in additional sales.".
Assuming all your other numbers are correct and "several hundred" manuals means 1000 and "several hundred pages" means 1000, you have 1M pages. On 5 scanners like this for $18,000 each, you will receive a theoretical performance of 900 images per minute, which means a total of 18.5 hours for 1M documents, not considering the daily duty cycle.
For money that is worth a salary of 3 people (two-salary equivalent for the above-equipment and some extra money for a man to operate this), you get performance and manpower to scan, categorize, and post all the manuals that you need in less than a one quarter.
And I haven't even started talking about cost if you are outsourcing this type of a job to India...
Bottom line, if it didn't generate revenue, a company wouldn't do it. So even though you call Yamaha a "good" company in a sense that they have values beyond making money, that is misleading. I personally haven't worked at a corporation that is out there for just "being good"...
"There is no such thing as free lunch."
Poor little misguided Slashdotter...
Plus you forgot to point out that the benefit of .NET is in its interoperability with all Microsoft's "prior art", consequently making .NET a platform suitable and pretty evolved to develop enterprise-level services.
Speaking of prior art, here is an interesting place, you might want to look up whether IBM hasn't by any chance published something that could prevent M$ from this frivolous patent on the basis that prior art exists: http://www.priorartdatabase.com/
Great, so you presented examples of what I mentioned earlier anyway, i.e. specific nonconformities IE has when it comes to CSS.
While I might partially agree that benevolence only enables idiots who can't write proper HTML get their work across as 'looking okay' in IE. However, arguing that this benevolence is a bad thing is like saying that a college kid passes the course either by full score or fails.
All your examples were CSS conformance and nothing else, while in great-grandparent, you claim that IE does not conform to latest standards.
I am contesting your use of plural when saying "standards". I hope you were joking...
I am sorry, but you forgot to mention any facts. I am aware of nonconformities to the latest CSS standards.
However, as a browser, it is one of the browsers that will render even partially received information (or broken HTML) correctly. Apart from efficiency issues (memory footprint when accessing complex documents in several windows and/or instances), which are not necessarily directly related to web developers (GUI designers and (D)HTML kiddies), there are very few Web-developer-unfriendly issues with IE.
You haven't bothered to mention any, so enlighten us.
to say that "[Microsfot] SQL Server [...] has an archetecture that virus and worm writers have been able to exploit" is simply pathetically desprate misleading of the audience. Here is why.
The Slammer worm has used a vulnerability that was NOT an architectural design flaw across the product. It was a simple stack buffer overflow in an implementation of the SQL Resolution Service.
On a seemingly unrelated topic, here is a plethora of buffer overflow vulnerabilities of Oracle from some time ago. How much mass media attention did that receive. Close to none, because it doesn't pay the media in advertising revenue to show an expert talking tech about buffer overflows and authorization headers. But does pay off to create a bombastic news report on a big-time screw-up of the largest software company in the world.
I am sorry to bust your balls, but I do recall several instances of similar problems such as an Apache worm on FreeBSD. I am not arguing that Apache et al. have more flaws, I am just pointing out that everyone who has coding skills prefers to explore IIS's quality rather than some Apache's because of simple "I can pick on the weaker guy easier" predatory concept from kindergarten.
using a technique that I would call Reverse Replicated OCR.
Imagine you created a mechanism that takes those obscure-looking "rand0/^\ w0rd$" and converts them to legible "random words". Easier said than done? Well, if you converted the obscure text to an image, blurred each letter based on what other letter surrounds them (e.g. "^" would be blurred more than "n" because "^" is surrounded by "/" and "\"), you would essentially get, in my opinion, an image that actually looks more legible. "/^\" would collapes into an "M" in the eyes of an OCR engine.
The proposition to make it OCR-based is just an implementation, but the idea is to have a parametric system that realizes that "/^\" can be mapped to "M" for example.
Since this whole proposal probably sounds obvious, one might expect this will be implemented pretty soon.
When it comes to the excerpts from E.A. Poe's works or other continuous sensible text, this will be a much bigger of a problem to tackle. I would even dare to say that this is where we will see spam filter circumvention techniques to be advancing towards.
http://www.research.ibm.com/resources/news/images
On the left:
Andrew Tomkins, WebFountain Chief Scientist
On the right:
Bob Carlson, VP of WebFountain at the Almaden Research Center