On Fri, 6 Oct 2017, Jack Harper wrote:
Interesting Stuff...
One of my heroes - Ray Kurzweil https://en.wikipedia.org/wiki/Ray_Kurzweil -
says that when he builds a new product that he always projects what the
computer horsepower will be like when the product is ready to launch.
Say, an 18-month development cycle, then design the product to run on a
computer with twice the processing power as available at the start of the
project.
Obviously, he is not advocating bloatware - far from it.
Go for products that cannot effectively work today because of the processing
requirements, but will work when released - things like AI/deep
learning/advanced DSP/image understanding etc.
ps - I HATE and LOATHE bloatware - e.g., so much MicroSoft stuff.
It is certainly a very fine line to tread.
On one hand, you wnt to design for what will be around when you release
and the future after that.
But, if don without adequate planning, you end up releasing software that
demands that the user replace their hardware unnecessarily. A computer
six months old should not need to be replaced!
'course there are some who say that it is GREAT for the economy to force
users to buy new hardware at least once a year! (cf. the hopes and
goals in the auto industry, and "planned obsolescence" from half a
century ago)
