Planned obsolescence
-
I believe one cannot experience change unless their is a certain degree of planned obsolescence. If that was not the case then we would all still be cave people, if that. In technical terms, we would all still be using punch cards, I believe, if it were not for planned obsolescence.
We would be using abacus, if there were no lazy people. Since there are lazy people, someone came up with a way to stop using punch cards, not because someone planned to make them obsolescent. Planned obsolescence is actually a force that is working against progress. It wastes resources on things, that are cuter and shorter lived, than the ones replaced instead of making them more functional and longer lasting (therefore redirecting efforts and resources from making cheap appliances to making say interplanetary spaceships).
-
I bet you've never said "I won't learn it" about any technology required for any task that's been shoved your way. So let's not hear anything about getting old ...etc. And for that matter - not everything is something that even should be kept up with, rather fashionable chaff blown away by the wind generated by the next perceived cash-in opportunity. And furthermore Get off my lawn :)
In fact I had a course in BASIC in college (business school). You worked on a teletype machine logged in to the University's main computer. I worked in Apple BASIC on an Apple2e clone computer and did an accounting application (Payroll and Inventory control) for the company I worked for. Next, after moving to Charlotte, I wrote a check printing application in Microsoft VB 1.0. I believe you are starting to see the trend here. I've moved through every version of VB since, up to and including VB6 ('84 to current supporting legacy apps for customers) and VB.Net (developing a website). I looked a C once for a monthor so and decided that you had to be a masochist :omg: to use it (way to low level). I rejected it out of hand. I have looked at C# but don't see any advantages over VB.net. On the data side went from flat file, to MS Access, to SQL server. So you see I have rejected all of them.
Stella!
-
Is it just me, or are we caught in some software/hardware planned obsolescence?:confused::confused: With several new languages, frameworks, and hardware coming out every day, it's got me wondering. Have the IT market software and hardware vendors saturated the market, and are trying to increase market share by bringing out minor and unneeded tweaks? I am not talking about the consumers of IT and the increasing demand for developers. On the language/framework front it seems like the "Tower of Babel". I used to be able to keep up by running as hard as I can. But not anymore.
I guess I am just getting old.
Planned obsolescence has been around for a long time now, in modern times, some time in the 1960's it began to pick up again. You see it in almost everything that could be made to last longer, especially things with moving parts. Its all about short term profit. Long range and broad thinking are out, short range and narrow thinking are in.
-
Is it just me, or are we caught in some software/hardware planned obsolescence?:confused::confused: With several new languages, frameworks, and hardware coming out every day, it's got me wondering. Have the IT market software and hardware vendors saturated the market, and are trying to increase market share by bringing out minor and unneeded tweaks? I am not talking about the consumers of IT and the increasing demand for developers. On the language/framework front it seems like the "Tower of Babel". I used to be able to keep up by running as hard as I can. But not anymore.
I guess I am just getting old.
i think everything comes from the fact that a lot of people need to justify their jobs. they make changes all the time, like everybody is working something. they take the up-directory button on windows explorer, then they return it. they take the start button on windows UI, then they will return it... you enter a 3yr project and work in whatever popular language, when the project finishes the language had 6 revisions and you are 'no more competent' in it. "if this frameworks are so great and helpful why do we need another one? why didn't the last 27 frameworks solve the problem? they didn't so you need the 28th framework, right?" Jonathan Blow on Software Quality at the CSUA GM2 it's nothing but chaos