Are Unfinished Products Now the Norm?
Paul asks: "Long ago when digital synthesizers first became commonly available, I recall a reviewer lamenting how he was getting more and more products to test whose software was unfinished and buggy and would require updates and fixes (this, before the internet allowed easy downloads, would have meant a journey to a specialist repair center). The review also commented how this common problem with computer software was spreading (this was before Windows 95 was out), and asked if it was going to become the norm. These days it seems ubiquitous, with PDAs, digital cameras, PVRs and all manner of complex goods needing after-market firmware fixes often simply to make them have the features promised in the adverts, let alone add enhancements. Are we seeing this spread beyond computers and computer-based products; jokes apart, will we be booting our cars up and installing flash updates every week to prevent computer viruses getting into the control systems? Can anyone comment on any recent purchases where they've been badly let down by missing features, or are still waiting for promised updates even whilst a new model is now on the shelves? How can we make the manufacturers take better responsibility? Apart from reading every review possible before making a purchase, what strategy do you have, or propose, for not being caught out?"
There is no such thing as an "unfinished" product. They're defective out-the-door.
Bill Clinton: Pimp we can believe in. - The Shirt!!!
It's amazing how much effort you can save when you don't take the time to do the job properly. As long as people still buy your product, there's no incentive to actually fix it before it launches.
Software is approaching the complexity of organic life. You know what it means for an organic being to be "finished"?
So what if our software is constantly changing, and is thus "unfinished"? To be finished means it won't improve. Heck, the whole reason for the existence of open source is the "if it's broken, I can fix it" idea.
So, why do we need software to be "finished," anyway?
Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
What truth?
There is no dupe
My answer to buggy/unfinished products has always been to take a pair of nunchucks to them. I think of it as an alternative way of 'finishing' them.
"As long as people still buy your product, there's no incentive to actually fix it before it launches."
Thankfully we've fixed that problem.
The DVD recorder has some "issues" with recording to DVD. It's very fancy, otherwise, complete with 6 possible recording inputs and can do slide-shows off USB keys with photos. Nifty specs. It seems that the primary solution is to update the firmware. You would think someone at the factory might have attempted to record video prior to shipping it, alas, they apparently did not. (It is an intermittant bug that causes the audio to progressively lag the video). Hey - it compiles, ship it!. Since the process for updating the firmware seems non-trivial, is riddled with warnings, involves a USB key and I'm lazy - I haven't done it.
Combine this disturbing trend with product reviews that are little more than a regurgitation of the back of the box. (Along with some weird DMCA rules about what can and can't be reviewed on a product esp. vis-a-vis security.) Now you have a situation where you can't even get real reviews of products, and no review is ever "not positive." It's just that some are more positive than others. So, here you are, trying to buy a $500 video camera so you can tape the birth of your fist child and you aren't even really sure that any of them work. On top of that you can't even trust the reviews you read on various sites. I agree with you, this is not a good thing.
Leave the gun, take the cannoli -- Clemenza, The Godfather
I wholeheartedly agree w/r/t complex software. Further, if you look at organic artifacts, even something as simple as a knife, the tool is always changing. The knife gets duller, and you sharpen it (removing molecules), and so it is constantly changing.
I think a lot of people say "uh oh, when are cars going to start getting the BSOD?", but what they don't realize is that, as complicated mechanical entities, cars DO give the equivalent of a BSOD. The word "crash" has a real-life meaning, too, after all :) Tires blow, mufflers fall off, things are changing all the time.
At least software is not subject to the laws of entropy (or is it?!)....
That depends entirely on perspective. If entropy is seen as a relative process, software that is not being developed is going to suffer entropy as the world around that software is changing. So, in relative terms, there is software entropy.
Hypothetically, if your current 'perfect OS' software no longer has any development being done, when new storage devices or networking devices become available, that 'perfect OS' is no longer perfect. For this reason, all software will always be 'incomplete' in as much as the world around it changes at an ever increasing pace. Some software is outdated by the time that it is ready for launch as a beta product. For more on that, see the big software projects that some groups around the world have attempted, only to find that on launch it is not capable of dealing with recent changes in the world.
All software will always be no better than beta given that the above is true. This means that for businesses, good enough is as good as perfect as that is as close to perfect as it is likely to ever get.
Sure, there are cases where good enough really isn't; medical equipment, space travel equipment etc. but for the vast majority of software for consumers, beta grade is good enough and thus worth releasing.
Fortunately, some companies release beta software/apps and treat them as such by continuing to improve them before pronouncing the software is out of beta stage. When software is released as final product rather than beta, consumers get upset when they find out it's really only beta that they paid for.
But the point is, yes, software suffers from entropy and atrophy is relative terms.
Support NYCountryLawyer RIAA vs People
How can we make the manufacturers take better responsibility?
If it doesn't work right take it back. If a manufacturer continues to put out a shoddy product, don't buy their products in future.
This is incompatible with the idea that you must have the latest game, the latest gadget, the latest console, etc. How many people on Slashdot know about Sony's abusive behaviour and yet bought a PS3 anyway? How many people here know about Blizzard shutting down Free Software competition with phony copyright claims and yet carry on using WoW? How many geeks despise Microsoft's abusive lawbreaking and went out and bought an XBox? The RIAA and MPAA are evil corporations, right? The DeCSS lawsuits are completely unjust, right? So how come you have hundreds of CDs and DVDs?
The fickle, greedy nature of Western consumerism causes this problem, and by giving in to your irresponsible impulse buying and fanboyism, you are part of the problem.
A nice example of this is the Canon Powershot S1. When I bought it, it did what the specs told me it would do. Then there was an upgrade that fixed some bugs. And after that there was another upgrade, and suddenly it had a macro function! It would now make sharp pictures at distances as close as 5 cm instead of 10 or whatever the specs were. Suddenly it turned rom a nice camere to a very nice camera.
-- Cheers!
I will always have two paper punches (hand perforator) at home. One is over 40 years old, and was used by my father. The other will be replaced every 3-7 years, depending on how long it will last.
The old thing is virtually indestructable, while modern equivalents are of lower quality, even though they come with those little bars to align your A5 or A4 paper size (Or US Letter).
Ours already broke off, so I just crease the paper in the middle and align on sight.
Henk
Note: That little compartment in a paper punch is actually a supply of holes. Don't forget to refill it.
change is inevitable
Would you like a 0$ refund?
Yup -- a program is never done. Always one more feature to add :)
However, we routinely produce complicated systems that have excellant reliability. For example, glass displays on aircraft - which are quite common in commercial jets. They have to undergo a much more rigorous level of testing before they can be shipped because the liability to the manufacturer is huge. What's the liability if your Sony cam-corder stops working in the middle of your once-in-a-lifetime round-the-world vacaction, all because of a software glitch? The problem is not with the software, the problem rests partially with the people that make and test the systems, but mostly with the people who hire/fire developers, designers and engineers. They do silly things like higher cheaper, but less qualified engineers. They make marketings's brain-fart of the day the top priority. (I realize we're using the world's cheapest 16 bit micro-controller - but could you write the software in Java with a Gui so we can demo at Java One?) And they do things like sacrifice testing to make schedule. And they're also the ones that do things like set budgets and deadlines.
Leave the gun, take the cannoli -- Clemenza, The Godfather
This has been going on for as long as CE have been sold with "commercially developed" firmware. If it's simple, it can be bug-free. When it gets complicated, if you're using the "write and debug" model, you will get bugs. And you'll get usage bugs: ones that affect practically all users, but don't show up until expensive real-world testing is done.
Shameless self-plug aside, this is happenng even with firmware we'd thought was following a different development model, like that in modern fighter jets. And there, they compounded problems by not having at hand the hardware necessary to upload firmware. That's why when you buy a cellphone today, you factor in the cost of a USB connector.
God what a devastatingly witty repartee.
I can only assume you consider OSS to be in the what you pay for is what you get category, a zero sum gane of zero. And interestingly after paying and getting nothing, a lot of people would rather willingly commit a criminal act and pirate the supposedly useless commercial offerings than continue to use OSS because it fits their needs better.
Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
What truth?
There is no dupe
When I first bought my TiVO, it said that it could connect to my home network. It didn't really mention that it required an external network card to do that. So I went to TiVO's website and found a Linksys network card that TiVO said would work, and I bought it. I connected it and it did not work, because the TiVO I bought had an old version of the TiVO software on it that didn't work with that network card. The only way to get my TiVO to work with that network card that TiVO had approved was to have a phone line. So much for working with my network out of the box.
Posting anonymously, because I review consumer electronic devices for a major web site. It gets depressing. I think I'm one of the few "reviewers" that don't reguritate press releases and/or the specs on the box. I work through each advertised feature and really try it out. I almost always find bugy user-interfaces, features that don't work, and features that are not documented. I used to start these reviews enthusiatically, but over time, I'm gotten more cynical. Today I'm working on a new review and finding the usual problems: Pop-up error messages that are blank except for an "OK" button, security holes big enough to drive a truck through and documented features that plain don't work. And this is with an expensive device that won a major award at an industry trade show. I look at the shiny box with the happy models and I read the glowing quotes from other reviewers and I wonder if they are using the same product I am.
Sigh...
How much does the glass display for an aircraft cost compared to your camera? How much of that cost is testing?
T Money
World Domination with a plastic spoon since 1984
Really, who cares? It's not as if everyone has the time to
If moderation could change anything, it would be illegal.
Apart from reading every review possible before making a purchase, what strategy do you have, or propose, for not being caught out?"
Don't buy new products. Seriously, if it is worth buying it will still be on the shelf in six months. Even then I wouldn't buy it until I had read a few *user* reviews, immediately disregarding the top 10%. Check out some forums. Unofficial forums that is, publishers are notorious for nuking negative comments. I do not trust professional reviews. Ever. Even for existing software things can be pretty sketchy for a while. Consider how often Apple manages to botch iTunes, and that's their billion dollar baby. I know it's not what you wanted to hear, but you have to do your due diligence and be patient.
Frankly I don't see this problem going away until it is legislated away. If the bills concerning paid advertisements (i.e. the Sony PSP blog et.al.) have any teeth and clear consumer friendly rules, then reviews might have some value again. Not a lot, but some. Beyond that, liability is the only thing that's going to reign publishers in.
Platform advocacy is like choosing a favorite severely developmentally disabled child.
I think you might be missing the point slightly about open-source.
You release unfinished products not out of laziness or incompetence, but because that way others can work on them too.
You're seeing the development process, which is normally hidden from you, in action. Is it any surprise that the unfinished software isn't all that you'd hoped for?
"Release" means a different thing in the commercial world than in the open-source world.
If moderation could change anything, it would be illegal.
I won't disagree with you on that. A Garmin GPS unit is a couple of hundred bucks. A garmin navigational unit for an airplane is several thousand - all because it has to be certified for use in aircraft. You make a valid point that it's expensive. I was trying to make the point that we can make quality stuff. My gripe is that even "high-end" stuff suffers this phenomena. Even more so in some cases.
Leave the gun, take the cannoli -- Clemenza, The Godfather
Any product that does not make it out the door is "finished", that equates to 60-80% of all software products depending on who you listen to. Personal experience says to me it's more like 10-20%, but I'm not regularly involved in pre-sales or spreadsheet scripting.
Another category of "finished" software products are those tagged with the euphemisim "functionally stable" or "legacy", wich roughly translated means "go away and RTFM".
And did you exchange a walk on part in the war for a lead role in a cage? - Pink Floyd.
Even Slashdot posts are sometimes left unfinis
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
If it don't work like it should, return it. It's much easier to review a product myself, anyway. If enough people returned shoddy (aka unfinished) products, manufactuerers wouldn't make shoddy products.
> The problem is not with the software, the problem rests partially with the
> people that make and test the systems, but mostly with the people who
> hire/fire developers, designers and engineers.
No. It rests entirely with customers who buy cheap, heavily advertised crap, complain bitterly about how it doesn't work right, and then go right back and buy more cheap, heavily advertised crap from the same vendors.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
"There's no finished software.
Finished software is outdated.
Windows 2000 - from the guys who brought us edlin
I'm approaching 100 years old, but I've still got a very long way to go before I get there.
Because as a consumer, if I blow 300 bucks to buy a funky new PVR, I'd like it to at least record the programmes I ask it to, the way my VHS VCR did 20 years ago?
Because the time lost in business due to poor software products being inefficient costs a staggering amount of money compared to what we could do if we made the effort to get the top 10 most used applications designed and built properly, and these costs are ultimately passed on to society one way or another?
Because when I'm driving in my car (or the US Navy is sailing in their warship, take your pick) I don't want a stupid software bug to leave me stranded?
You get the idea, I'm sure. Software is typically sold as a product (or in connection with a physical product) to perform a specific task. I don't want to learn a new meaning of pain and suffering as the software slowly evolves to actually working over a period of 1,000 years. I just want it to perform the task for which it was developed safely, efficiently and reliably. This should not be difficult, but the commercial software world consistently produces crap because the market has demonstrated a willingness to pay for it.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
I bought myself a p990i (with orange, uk). Its a very nice phone - the specs are great - 2mp camera, ieee802.11b, pop3,smtp,3g, etc. Anyway, the phone crashes regularly, the interface is slow, when pull the num keys down to reveal the qwerty keyboard, the screen goes white for about a second.
There's a firmware fix for it from sony ericsson, but orange have installed branded firmware so I cant upgrade to fix the bugs. Any suggestions?
See the problem is that a program is only as good as it's programmer. Unfortunately, software test engineers are worse. I think also there is a lack of good programming technique. I've seen people take advanced C classes whos code couldn't even handle the simplest exceptions. I had an instructor who would take off 10 points for not catching extra tokens in a command line. As a result my code is tight.
What I see is in this world who ever gets their product out first is the winner. Thats why public betas are more important. Microsoft and vista is an example of that. At least they patched some of the security holes before they launched.
What I think is programming is an art form. I know people who play metal on guitar. When you ask them what key they're playing in they stare at you blankly as if they don't have a deep understanding of the notes they are playing. I think programming is plagued with the same problems. Programmers no longer have a deep understanding of whats going on in a system. Part of that I think is due to the educational system. Many Universities start teaching Java as a first language. You learn what a class is before you learn what a class REALLY is.
It takes a good understanding of the ENTIRE system to find bugs. Often programmers are completely focused on their little piece of code and aren't held up to standards as long as it works when they test it.
You keep using that word, are you sure it means what you think it means?
Obviously value and quality also have different meanings, as well.
I like that one about people would rather commit a criminal act and pirate commercial software than use open source.
It's really gotten out of hand. I just bought a new 2007 Jeep Wrangler. This is a major redesign of the old Wrangler line, and, for the first time, includes not only ordinary ABS, but active stability control in both yaw and roll, with rate gyros and computers.
Yesterday, I received a recall notice:
DamlierChrysler Safety Recall F50 - Reprogram ABS Control Module
"The software programmed into the ABS control module on your vehicle may cause the rear brakes to lock up during certain braking conditions. This could result in a loss of vehicle control and cause a crash without warning".
So it has to go in for a firmware upgrade. Over 60,000 vehicles are affected.
You're seeing the development process
No, you are seeing the development process never end. Just try and count the number of projects, even highly popular projects, that are still stuck in pre-1.0 state because the developers can not be bothered to set a specific goal and work to polish the product up for release, but instead just want to do the fun work of adding new things forever.
Do not buy a new product as soon as it is made available. There is hardly any device or feature that you need so desperately that you can't wait several months. Use that time to research the different products and you'll most likely find a different one (or that same one, but now complete) that works fine and you'll probably save money too.
The ones my company produces cost several times my yearly salary a piece, and I am not exactly living poor.
Best Slashdot comment ever
Leave the gun, take the cannoli -- Clemenza, The Godfather
There isn't much choice when the maker of the cheap, heavily advertised crap was so heavily subsidized with government funds and stock market favoritism that no competitor had a running chance in the market.
I don't think many people fully recognize what an impact government had on the software industry and the internet through the 90s. It was taxpayer money that provided a significant percentage of the capital for the companies which went big (or went broke). It was taxpayer money that provided a significant percentage of the capital to build the infrastructure. It was taxpayer money that provided a significant percentage of the research funding. On the other side of the counter it was taxpayer money which bought the products.
But it was only the directors, CxOs, VPs, and major stock holders who were allowed to walk away with the profits. Where is the taxpayer's cut?
the NPG electrode was replaced with carbon blac
I don't think the contention is that software should be perfect, and should never be changed. However, it would be nice if the software at least worked well when it was released. More and more software is being released in an almost perpetual "beta" state, even though users are paying for it. It seems to be more acceptable to release software with bugs in it, that hasn't been through a proper testing regime.
So, why do we need software to be "finished," anyway?In this context, I would say it would mean that it isn't full of bugs. I think that's important. Am I somehow being selfish by wanting to run non-buggy software that works? Maybe you don't need that, but I certainly do. I haven't got time to waste on bugs, I have work to do.
... and then they built the supercollider.
Remember the NES? The ZIF connector was poorly designed and was prone to geting dirty and breaking at random intervals. It's the only console that comes to mind in which you can fix by blowing into it (despite only furthering the damage done.) It took a rather long time until Nintendo did much to fix the situation hardware-wise, with the release of the NES2. It was released in 1985. The concept of implementing half-baked concepts into retail products isn't exactly new, although it is becoming more prevalent every day. (Think Windows 3.0)
Around 1970 the quality of the bikes was so piss poor that factory new machines would often simply not work without extensive work by their new proud owner. So did the japanese with their fastly superior quality bury HD as it deserved too?
Hell no.
But bikes are an odd product. They are bought by 'fans' not just fans of a brand but fans of a the idea of bikes themselves. Having to spend hours working on your brand new bike to get it work is not actually a minus to a HD owner. A nephew of mine is a HD nut and once he finished a bike he loves riding it, on the look out for a new wreck, sorry, rare find to work on.
Most tech goes through this face. Long before polaroid made photographs a snap you had a large group of photographers making photos despite the hassle involved. It wasn't always that cars were black boxes that just start always when you turn the ignition and you never ever look under the hood. Early car drivers had to be their own mechanics. No, that is not right, that sounds like they objected to it. For early car drivers, it was part of the fun.
It ain't just tech, ever had a sister who LOVED horses? They actually enjoy taking care of them, shoveling shit and hauling hay.
Computers are just the same, early adaptors don't mind the nitty gritty, for them it is part of it. As my nephew likes scraping rush, my sister loves shoveling shit, I love messing with obscure setting and compiling my own kernels. Take those "messy" bits away and you ruin the whole experience.
The problem is when the "normal" people get involved. When a tech moves from the early adoptors to the mainstream. When it is no longer a "hobby" but becomes a necessity.
There is a reason we no longer use horses for transportation. There is a reason why no courier service uses HD bikes and there is a reason why MS tries to hide all the settings from the user.
The problem is that in a very real sense some tech moves into the mainstream before it is ready and/or the mainstream audience has the wrong idea about the tech.
If you owned a horse back when it was a mainstream form of transportation you had better accept that the horse had to be properly maintained, the movie idea of driving it hard across the desert into the town, jumping off and heading into the saloon just ain't "real". It requirs rubbing down, watering, feeding. They don't show that on tv.
They don't show you having to exchange the oil of your car, check its tires, replace the lights either.
The computers on tv? They have voice commands, can log onto any service automatically and always have the right file just a keypress away.
Reality is that computers just haven't reached a level of ease that suits the mainstream audience who just wants their product to run with zero maintenance. Is this wrong? Well, could you blame ford for not making its earliest cars as easy to operate as todays cars? Offcourse not. Tech has to develop. It has developped, compared to even the early home computers modern machines are a doddle to administrate.
You need to be your own "admin" of your system, know how it works, why things happen and how you can deal with them. Sure it would be nice if the system was advanced enough to just deal with it but that ain't the case. Yet.
Neither does your car, just ask your local mechanic how often they got to fix cars after their owner put in the wrong fuel. Why doesn't your car warn you before you put in the wrong nozzle? Because the tech ain't ready for it yet. One day it will, just as your car nowadays warns you when the oil is out (the oil light was once an innovation).
Same as your PC will one day warn you accuratly when you are about to download some dangerous software (No I am not talking about UAC or similar crap, that is closer to a sticker on your windscreen telling you to check the oil).
BUT not yet.
Early games required a lot more tweaking then they do nowadays. Believe it or not, once TV's didn't come with an AV button and you had to tune in you
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
> Software is approaching the complexity of organic life.
No, no it's not.
Bought a USR 8054, the features I needed weren't actually there... The update ...however long later added them, or the illusion of them, they never worked. The entire router became less & less stable as time went on. I tried to find a good one, but all of them were cheap POS because of the software involved. Even the "quality" stuff was hampered by poor software. So I figured I would try my luck using replacement software and not care. This I have a couple routers with 3rd party firmware now that work great, and do what they should have done out of the box that didn't.
While I appreciate the work the 3rd party firmware developers did, and it would be sucksville without them, its because none of the makers are making a good finished product period that we are in this situation and they had to develop something.
Freedom is merely privilege extended unless enjoyed by one and all.
Although some OSS projects never make any effort to produce a stable release (like Code::Blocks), many others are quite good about producing fully-functioning stable releases relatively often. Trunk source access and nightly builds don't make the stable releases any less stable.
2 weeks ago I bought a router and after using it 2 days I noted that the network was slow. I checked the linksys page and I found out that there was a big notice asking people to upgrade to a new firmware which suposedly would fix speed problems. Ok so I try to upgrade the firmware and the router goes dead. I speant 2 hours with linksys customer support. Then I went to the store to retun it, they would give cash back so I got another router, again with old firmware. This one upgraded ok. I think the store should sell the routers with the latest firmware, specially if there is a big advisory about it.
I read an article that the software was updated multiples times. An interesting point was the stuked bits in the processor registers (bit permanentely set to 1 or 0). NASA issued a software update to go around that.
More info here: http://voyager.jpl.nasa.gov/science/thirty.html
You may want to look at the Postfix mail server, it went a long time without errors or updates.
Harley was bought out in the early Seventies by AMF, the sporting goods company. It was AMF that decided they could bring certain efficiencies and cost-cutting measures to bear on the manufacture of the motorcycles. Unfortunately one of those was that the walls of the fuel tanks were flimsy and given to blowing out or exploding. Given the location of the fuel tank on the bike (the rider sits on it), the result was some horrific accidents. Those that weren't fatal left the rider hideously maimed. The bikes were flimsy in any number of other ways; it's just that the gas tank thing was so memorable. AMF changed the name of the company for a few short years to AMF Harley. It didn't take long for "AMF" to acquire its new meaning--"adios, motherfucker..." I believe (but am not sure) that Harley Davidson was bought out by its then-employees after sales fell through the floor. If that's not accurate, then whoever bought it dedicated considerable effort to bringing the bikes up to their former high quality.
It's somewhat interesting that the same era saw the exploding Ford Pinto gas tanks. The story making the rounds was that Ford knew about the problem but deemed the fix too expensive until people started being immolated by the dozens. The other spectacularly shoddy vehicle of the era was the infamous Chevy Vega with its warping aluminum engine block.
Shoddy workmanship isn't new, but the modern tradition of shoddy workmanship seems to have had its genesis in the early Seventies.
"Here's what's happening. You're starting to drive like your Dad..." - Red Green
Gee, volunteers mostly only do the things that are fun? I'm shocked!
If you're unhappy with the software, then pay someone to adapt it to your needs. If lots of people are unhappy with the software, then they can pool their resources to pay someone to adapt it to their needs. At least that's feasible with free software.
http://outcampaign.org/
... it's the UNIX philosophy. But it's really not just applicable to UNIX... it applies to software development in general.
Things can always be improved and tweaked, but while that code is unreleased, users are living with previous versions which may lack other features a new version brings. This is why lists of known issues are maintained. That list of caveats to let the users decide.
Also, at some point you just have to get that sucker out there for people to start using. Mac OS X 10.0 comes to mind. It was such a departure from OS9 with so many changes that Apple pushed it out the door just to get people using it and to give developers a reason to stop concentrating solely on OS9, even though it had many usability issues. Early adopters were affected, but people were able to make that choice for themselves. (Apple did release 10.1 as a free upgrade, unlike the following releases.)
Finally, as for abuse by companies constantly releasing paid frivolous updates/fixes.. the marketplace should take care of them and limit this abuse.
I agree. You can look at the current state of the printer market and see loads of crap that consumes vast quantites of supplies and fall apart in a couple years. But those manufacturers are the only ones left in the market.
I still have a dot matrix printer that functions flawlessly and is over 20 years old. That company no longer produces printers.
I think it happens to all industries when the profit margin is marginal. They'll dump it on the market and get new funding then fix the complaints as they happen.
I'm seeing that with several routers that started out great but now release buggy crap.
I'd go on a Vegan diet but the delivery time from Vega is too long. --brownkitty
Sure. The shop will do that for you. If, and only if you and all other customers there are willing to spend the extra $$$ for such a service. But I'm sure before you go out and buy your Linksys router, you check price levels on a couple of sites. If that up-to-date Linksys in your local shop then shows up at 3x the price, I'm sure you will pass up and buy from that cheap place. So your shop with service will be out of business real soon.
The entire issue revolves around people wanting everything cheap. Quality costs money. Service costs money. As soon as peope are willing to pay for qualiry and service then I'm sure they will receive a lot better products.
To Terminate, or not to Terminate, that's the question - SCSIROB
In the UK, if a product is advertised with certain features and those features either do not exist or do not work, you can return it for a full refund under the Sale of Goods Act. Items must be "fit for purpose" and advertising must be accurate.
That really is the best stratergy. If companies get too many returns, they will realise that their products are not up to scratch and either go out of business or fix them.
BTW, don't be fooled by retailers who claim you can't return things once the packaging is opened. The law appilies to everything, even software and things sold in those stupid "blister" packs you have to destroy to open. Just because the manufacturer made it impossible to find the defect without opening the product doesn't mean you can't return it. Even cars, which loose thousands of pounds in value when you drive them away from the dealers fall under the same law.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
Hell no. Actually. I think you'll find that in the rest of the world, they did exactly that. Harley Davidsons are seen as a joke pretty much throughout Europe
Deleted
Fast, cheap, and good.
I can give you two out of three, which do you pick?
jokes apart, [sic] will we be booting our cars up and installing flash updates every week to prevent computer viruses getting into the control systems?
It's no joke.
https://www.eff.org/https-everywhere
Gee, volunteers mostly only do the things that are fun? I'm shocked!
No, this is obviously not shocking. However, claiming this is a better development model than that for propietary software is definitely stretching it just a bit.
Apologies for ranting off at the most convenient target but:
EA only seem to release bugfixes when patches are coming out to support paid "booster packs". Battlefield 2 is a prime example of EA's continued disregard for their customers. Every time I see their intro movie I groan, because I know the game is going to have been rushed out the door.
Contrast this with Starcraft - those chaps seem to be still releasing patches (I think the last one was within the last 2 years - not bad for 1998 game!). Valve keeps CS ticking along nicely.
EA is similar to Sony in my eyes. I remember when I paid for BF2, and installed. Patched to 1.3, couldnt join a server due to punkbuster. Updated punkbuster, experienced the horror of the 1.3 patch level (unlikely you could remain in a server an entire round - nasty with the long load times). EA announces a new expansion (oh and BF2142). The cry from the BF2 community was pretty unanimous: "Fix the damn original first!".
3laws: No freebies, no backsies, GTFO.
Arguing about "proprietary software" as a development model is nonsensical. I think you're confusing commercial ("cathedral") vs. volunteer ("bazaar") development models, and free vs. proprietary licensing.
Lots of free software is developed by volunteers, and as a result, lots of free software is "unfinished". If you're going to use statistical models to show that free software licensing has an impact on product quality, you first need to adjust for that fact. Drawing conclusions about licensing schemes using data about development models is just bad science.
http://outcampaign.org/
Just liek a work of art, today's technology products are merely abandoned, and never complete. You can ALWAYS continue to refine and improve a product, but companies require a return on investment, so development work is abandoned.
Even if work was allowed to continue, no product would ever be "complete".
The result is products which are "good enough for most of our customers".
You want Product X - well, you can have it:
a) never, or
b) bloody soon, but slightly less than perfect.
Which do you choose?
How many escape pods are there? "NONE,SIR!" You counted them? "TWICE, SIR!"
Stop being a literal-minded nerd for a second and try to actually read the meaning of the post and not the individual words, please.
It has sadly become the norm for console game systems. When my coworker brought home his shiny new Wii (on launch day I believe), he said he had to hook it up to the internet and let it download software/firmware updates overnight. So basically, he couldn't just sit down and play...or maybe he could but it didn't have all the functionality it promised. The same is true with the other console systems now. It seems that everything wants to connect to the internet just because it can...basically since broadband access has become ubiquitous.
Well, you know what...maybe I don't want my refrigerator to connect to the internet. I don't want my home to be THAT connected. This is probably because I spent my college years working tech support for an ISP and a hosting provider. I'm all too familiar with how unreliable this interweb thing really is.
Sometimes you see a product pulled before it ever matures to a finished state. It might be that a good product doesn't sell because of a bad first batch. Other times a product gets sucessively better and may even be on the way to greatness, but the company wants to do "the next best thing" and shelves whatever they almost finished developing.
In such cases maybe you could hope that some community has seen around whatever shortsightedness there was by a product's creator, and there are some DIY mods or upgrades in existance.