Why Does Beta Last So Long?
Carl Bialik writes "Noting that Google News has been labeled 'beta' for nearly three years, and Microsoft's antispyware program for nearly a year, the Wall Street Journal looks at why 'beta' lasts so long these days. The article mentions the usefulness of getting the masses to test the product, but also notices another possible reason: 'Betas also have become a marketing device in a fiercely competitive industry, allowing software and Internet firms to release new products or services sooner and cultivate early buzz. Betas, which once had been quietly distributed, are trumpeted in press releases and at news conferences. "I deplore it as a consumer; I admire it as a marketing professional," said Peter Sealey, a marketing professor at the University of California at Berkeley and former chief marketing officer at Coca-Cola Co. "I can't come up with anything else in the entire marketing world where marketers knowingly introduce a flawed or inadequate product [and] it helps grow your user base." '"
The reason people like products released as Betas, is because it's the most honest software companies ever get about their products. It's pretty much as simple as that; Beta implies under-constant-improvement, and even I as a consumer don't mind imperfect software, as long as the company will at least advise me it's been released in Beta - under construction.
so thay must just be very slow in geting stuff done
seriously, why wouldn't you do this with dedicated gamers AND still charge them money for the xbox?
It allows for the company to release the product and have it utilized by the public, but if something were to break, they still have the cruch of "well, it is in beta" to fall back on.
why 'beta' lasts so long these days
Because companies are being more realistic with project life cycles?
"I can't come up with anything else in the entire marketing world where marketers knowingly introduce a flawed or inadequate product [and] it helps grow your user base." Doesn't this describe the computer industry in general?
Am I open minded towards open source, or closed minded towards closed source?
If a product is labelled as beta, and they have to completely overhaul it or a severe security flaw is found. Any 'damages' can be shrugged off as "This was only a beta, use at your own risk".
~Matt
~Belly
where marketers knowingly introduce a flawed or inadequate product...
Heck, that's been Microsoft's business model for 25 years!
$7.95/mo, 200 GB disk, 2TBxfer, MySQL, PHP, RoR.
We thought we would finish this sooner... but we didn't.
Eventually we kind of gave up trying, but we're too nice to just take it off the website?
Who would have thought?
Or... my personal favorite:
"Beta" as a kludge to workaround users who don't read disclaimers and get hopping mad when things don't work. I swear that accounts for a big percentage of the people who do this.
Tired of Political Trolls? Opt Out!
This is a public beta for First Post, and I'd appreciate it if you could report any placement-related or other bugs.
___ In the words of Gen. Douglas McArthur: "I'll be right back."
The thing is, most software that we get is flawed and inadequate in some respect. Labeling the software as being beta reduces people's expectations. Thus when there is a serious flaw, the customer doesn't feel that irritated with it because it was beta. If it was a released official product, then they might have more room to criticize.
This sig has been temporarily disconnected or is no longer in service
You know, those tools you might work or live with who think that kmowing about and running the 'latest' software is some kind of life goal. Gleefully runnig bug-laden betas crashing their systems and reducing productivity.
I must be some kind of throw-back geek. I won't touch it until it ships. I don't do bug-testing for free...and no...none of these 'betas' are really that interesting anyway.
Blar.
Alphas have to work too hard, plus they have to think too hard all the time. They don't get to laugh and play. And Gammas and Deltas wear those ugly jumpsuits. I'm so glad I'm a Beta! Aren't you glad you're a Beta, too?
Well, there is nothing wrong with Betas, except if their is no real intention of a production/stable release in a reasonable timeframe. Something in Beta for three years should raise questions. The implication is tha by tagging something as Beta, software/service suppliers can absolve themselves of responsibility for defects. This is sort of like an even further erosion of the standard EULA weaknesses regarding bugs and defects. Software that is in Beta indefinitely should be called "abandoned".
How's that Windows XP beta been going? The OS X beta I've been involved with has been pretty good. We're up to 10.4.3b, and I'm confident we'll see an RC before the 10.5 beta comes out. =)
It's not offtopic, dumbass. It's orthogonal.
Drug companies do beta test their drugs. Usually- they pay the recipient to take them.
The point is- you get what you pay for.
"I can't come up with anything else in the entire marketing world where marketers knowingly introduce a flawed or inadequate product [and] it helps grow your user base."
Coke was the first to market, I strongly doubt that Coke as it is now was exactly the same as it was when it was first released (Cocaine anyone?).
The first to market is usually the one who wins. It is rare that the market leader falls off their perch (unless they make an error, like "New Coke", which nearly cost them their dominant position).
Therefore, knowing this, the businesses want to get to market fast, ergo, "beta". With the tag of "beta" if anything does not work as expected, the reply is "hey, well it *IS* beta!" In the case of google it seems that they label anything beta until they can figure out how to make money with it.
So, web businesses use beta to gain a market position - if MSN were not beta, it would have been in design for that year that it is still marked beta - and had no market presence at all.
Try to hack my 31337 firewall!
one of the excuses for releasing something in beta is "it's under testing, we are not responsible for lost data, etc. etc".
Because most programmers are male, and most male programmers have a fear of commit.
Chr0m0Dr0m!C
Because the developers want to publically show that they are a harmless bunch of Master Betas.
For a momement I thought the article was about Betamax... (Which I thought was conclusively dead.)
ELOI, ELOI, LAMA SABACHTHANI!?
I think the world just found out what happens when you rush a product to the shelf. Fortunately, Microsoft has had no real competition for its OS marketshare, so when they released buggy software no one could really do much about it. With the XBox360, people have other choices, and are moving on to the PS3/Revolution camp. Now its up to Sony to see if they can deliver a well tested and stable product that can survive being placed in a typical stuffy AV Rack, on the carpet under some dirty clothes, or on some hyper kids bed like consoles are typically used. Nintendo? Hell, i've seen pictures of melted gameboys from mortar attacks in the gulf and they still work!
Google haven't figured out how to make a bunch of money on things like Gmail yet, so, because they ALSO don't want the support hassles if something goes wrong, they mark their product as "beta".
Because, "beta" means "hey, don't bug us if it broke, it's beta, remember?"
"...and former chief marketing officer at Coca-Cola Co. "I can't come up with anything else in the entire marketing world where marketers knowingly introduce a flawed or inadequate product..." '""
CARS.
No wonder Coke got rid of him. Sheesh.
Beta is there to test a product and with Quality Assurance in place, errors get found and fed back to development, leading to more design and implementation steps, which then go back to QA, which find more errors ad nauseam.
...
Oh, and if it's not QA that comes up with a problem, then (depending on what you do) the security team raises some concerns, and it's back to the drawing board again.
Sometimes I wonder what there are still any releases
"I can't come up with anything else in the entire marketing world where marketers knowingly introduce a flawed or inadequate product [and] it helps grow your user base."
This is like saying,... "Why should there be free software?. I can't come up with anything else in the entire marketing world where you can get something for free".
Clearly, Google is the next Microsoft.
I think Google perpetually labels things "beta" because of arrogance. It can always respond to criticism by saying "but it is beta".
It's been in beta for nearly 10 years ;)
Part of the reason is that they can reserve the option of making it non-beta in the future and charge for it.
Because that is how they specified it, according to their Test Plan.
At least, this is how things should be done (speaking from experience, on both sides of the coin).
I remember reading an article on Wired a long time ago about why Google News will forever be beta: it's all about money and copyrights. As long as it is beta, Google can claim it makes no profit from Google News. As soon as it gets "released," though, every newspaper with a lawyer will try to shut it down.
Give a man fire, and you warm him for the night. Set a man on fire, and you warm him for the rest of his life.
The reason, in the case of the two examples given, is because they both have an incredible pressure on them to work properly and be secure. Meanwhile there is very little added benefit in going from their current beta status to production status because people are already using them in full force.
Not all betas last forever, but if you can release your product without the accountability of releasing your product, then it makes perfect sense. I don't really see it as a marketing ploy because I don't see any added hype either upon beta release or production release. If a product is publicly available without any significant obstacles, and works well, then it has been released...regardless of what they call it. Releasing it again isn't going to generate any serious momentum unless there are significant new features, and that is the same as with a 2.0 release.
Welcome to the internet, things move slowly here, and always have...but wait until Internet 2.0 (currently in beta) then things will move really fast!
(yea, yea, I know there is an internet2, it's a JOKE OK?!)
The basic sleazeware produced in a drunken fury by a bunch of UCBerkeley grad students was still the core of BIND. --PV
The reason people don't mind betas is that generally by the time they're released out to the public their main feature set is working. Also, the google and similar betas we've been seeing are not just betas of the next versions of apps, they're betas of new and interesting software.
If the new and interesting software fills a niche, it's primary functionality will be used by people. The primary functionality is generally in the publicized betas, therefore people use the beta.
Linux is a piece of shit and should be considered "beta", at best. Server crashes and installation issues are just some of the problems organisations get from mislabeled products.
I had never thought about it that way before, but if you think about it, how many times have you used software and it crashed and you got upset. Now on the flip side, how many times have you downloaded a buggy beta test software and had it crash and been really upset? Interesting concept, someone releases something sub-par, we test it, they fix it and sell for lots of money! Maybe Vista should be released this way, free download off of the MSFT site, fix it and then sell it to me.
Generation Trance: What generation are you?
Betas are indeed helpful to consumers. It allows them to get an early look at a product and guide its final look and feel and feature set. This allows the company to develop a better product and consumers get a product that more suits there needs.
While it's true that using beta software is not for everyone, there are many users who do and make this symbiotic relationship worthwhile. As a software developer for enterprise customers, I see this play out with great success all the time.
10 minutes working on a sig. What a waste.
even the less tech savvy internet users these days may have heard the word beta, associated with new products that are coming out. It is a very calculated ploy on the part of large companies these days to release products to beta first, in marketing campaigns that have if anything, become more complicated and expensive to develop. Truly Advertising is the premier product of the 21st century.
Promote Charity on Myspace, Show Your Colours!
It means a compay is being honest about developement status. It takes time to make quality software. Thought I still don't believe Windows ME was anything more than an alpha status :P The company is basically saying this is their software, there's bugs in it, help us make it better by giving your feedback.
"I can't come up with anything else in the entire marketing world where marketers knowingly introduce a flawed or inadequate product [and] it helps grow your user base."
Think Sega dreamcast! Sure, it isn't software, but the flaw that shipped with it that allowed you to boot CD-rs was what sold most of those systems
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
Does Microsoft releases past-beta software? I mean other than just changing the name and remove beta.
I gave up with the idea of an useful sig...
I think the real reason many companies do it is it reduces any perceived liability. If a company releases "beta" software, they are saying up-front that it is in development and may have problems, some possibly serious. That way- if their software destroys your computer or just doesn't run right- there really isn't any recourse. The company can simply say- "Hey, it's in beta!"
As to complaints about why one has to pay for "beta" software in some cases- many companies charge for beta software in one way or another. Some, like Microsoft, force you to pay to be in special groups, like Tech-net or MSDN to get some betas, or you may need to buy another "production" version of the software to qualify for the beta.
i dont think this is a bad thing. more and more people are becoming aware of how difficult it is to program GOOD software. By releasing betas, it allows people to get their hands on software much earlier than if it had to be absolutely perfect before being released. Besides, by the time software is actually "complete" and stable its often either obsolete or there is something better out. Betas are just realistic, but you do have to draw the line somewhere I think.
Fascism is the greatest political ideology ever conceived. Sorry.
Google haven't figured out how to make a bunch of money on things like Gmail yet, so, because they ALSO don't want the support hassles if something goes wrong, they mark their product as "beta".
Gmail has been making money from the beginning. Ever notice those ads on the side of your email?
Google News is the hard one. The actual content is provided by other companies who are also trying to make money off of it. If Google pushes too hard to get their ads in, the companies providing the content will cut them off.
My dad was a bit of a gamer in the Apple II days-- and every once in a while, he'd spot a bug. Being a programmer, he knew how to document bugs, and because of this, he belonged to a couple of beta test programs-- Omnitrend's Universe II, for one. Every so often, we'd get new releases in the mail, and were told to test the hell out of them. The games were usually feature incomplete, though whether this was by design ("We'd really prefer that you concentrate your efforts on testing this feature) or by omission ("really haven't gotten around to coding that, sorry"), I don't recall.
Now, with the internet ("please download our patch") and open source software ("my box is so optimized that it can rebuild a kernel in 45 seconds"), the exclusivity is gone...
Beta DEFINITION is no known bugs, no defects!
A wise and detailed tech note by Darin Adler (of Blue meanie fame) at apple distributed to all apple developers on the definition of Beta, Alpha, Development, and release describes beta accurately.
At the precise mement software is labelled something such as 2.3b (beta) there are NO KNOWN bugs and all features are complete.
It is the idiotic masses that do not understand the meaning of beta.
I shipped millions of dollars of software I proudly labelled "Beta' I only removed the beta mark after it was in the customer base for a few weeks.
The vendors all wanted my latest newer betas... never the older "non beta" labelled software from three weeks earlier.
Do not blame the developers! They are the only honest ones in this matter.
Over 700,000 people used my software and PAID for it. And most of it was labelled "Beta", except boxed shrinkwrapped copies on store shelves.
Darin Adlers Tech note is one of the wises things I have ever seen come out of Apple. I wish it was online (it probably is) so that you all would know what i mean.
BETA means no known bugs and 100% feature complete, at time of designation, and it always has meant that.
You are thinking of alpha software, or development builds if you disagree.
As for Google News, one reason it remains in beta is that it has no business model. If Google tries to put ads on Google News, the newspapers and magazines whose stories are listed on Google News would probably file lawsuits, alleging that Google is trying to profit from their content. Google's emergence is a threat to the major media outlets that represent much of the content on Google News, and some folks in the news business believe it will remain in beta untilthis problem is settled.
RichM
Data Center Knowledge
Why Does Beta Last So Long?
Sometimes, the universe is pretty cool.
The opinion above is fiction. Any similarity to real opinions, including facts and logic, is purely coincidental.
It's well known that Google News is in beta because the company cannot make money from it. Once it starts making a profit its "fair use" defense will disappear and the lawyers from all of those news sources will start suing it dry. It'll be in beta forever, or at least until they find a way to make a profit off of it without risking a lawsuit.
If someone says he and his monkey have nothing to hide, they almost certainly do.
"I can't come up with anything else in the entire marketing world where marketers knowingly introduce a flawed or inadequate product [and] it helps grow your user base."
I guess he wasn't around for new Coke.
But, are they making ENOUGH money from that to cover the cost of creating and maintaining the service? Now, I know that neither you or I can answer that question authoritatively
Perhaps a better way to make my point is that google aren't ready to put their full support team behind the product, so they market it is an "as is" product, and call it "beta" by way of covering their butts.
I think it's because labeling something 'beta' makes it so that a company can release flawed software publicly without the hassle of providing tech support for it.
Most software released as 'gold' these days should actually be marketed as 'beta', because that's what it is. And now that 'beta' has become a marketing word, I think we'll see more and more of this practice.
SYSOP ('sih-sop) n.: the guy laughing at your typing.
Then started the epedemic of teen obesity.
At least that's what THEY want you to think...
the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff
Well sometimes it is so they don't get sued. Google News has been in beta for 4 years, and the consensus is that it will stay that way for years to come.
From this article:
"The reason: The minute Google News runs paid advertising of any sort it could face a torrent of cease-and-desist letters from the legal departments of newspapers, which would argue that "fair use" doesn't cover lifting headlines and lead paragraphs verbatim from their articles. Other publishers might simply block users originating from Google News, effectively snuffing it out. "
PS on a related note Service Packs will be referred to as product "Enhancements" on that version. I fondly call them little dutch boy pluging holes in the Dike.
Linux is a piece of shit and should be considered "beta", at best. Server crashes and installation issues are just some of the problems organisations get from mislabeled products.
y Shuffle."
Thank you for your input, Mister Balmer.
Now go work on your dance for the next developer conference. Try to find something more inspiring than the Miami Sound Machine for music, and come up with better moves than the "Gunshot-In-The-Thigh-And-Need-To-Pee-Really-Badl
- Superior picture quality and signal-to-noise vs. VHS
- Widespread adoption by studios and professionals (Beta SP)
- Convenient smaller-sized cassette
- Mfr'd and licensed by Sony, a company known for their progressive stance regarding consumer rights.
The problem isn't that stuff is "beta", but that people mislabel their warez as being beta. It's marketing baloney on par with "Professional" or "Enterprise". Where once meaning existed, it all reduces to "1337".
Unless you're wearing an ugly jumpsuit ofcourse.
...and I wonder: If they lost everybody's mail, and didn't have any backups, does this mean they would be off the hook? "Hey, we told you it was beta."
"I can't come up with anything else in the entire marketing world where marketers knowingly introduce a flawed or inadequate product [and] it helps grow your user base."
Talk about silly nonsense. In previous marketing terminology, this was called "last year's model." Marketers have ALWAYS used product improvements as a basis for selling essentially the same product again. My '06 Honda Odyssey has newfangled headlamps. Big whoop. Was the previous model "inadequate" because it had a different type?
Beta is simply about calling something "free but use at your own risk." It's better for software companies than releasing Version 1.0 for free, because you can NEVER go back to charging for it once you do that. Ask Netscape.
There exists no way of exchanging information without making judgments. --Bene Gesserit Axiom
I use it every day. Couldnt live without it!
__________________
http://www.MailEater.com - Disposable email addresses. No Registration required!
I'd much rathar have a product that is unfinished, and gets slowly finished in a way that the featured that get implemented are those that users actually need and want than a "finished" product that has features that a marketing department decides that I need.
"Your superior intellect is no match for our puny weapons!"
Another real reason when you're a big company to get into beta (or...when software is "viable") is that you can move software development costs from expenses to depreciable long term assets. There is some interpretation that goes on, but there are many cases when large corporations benefit from pushing toward beta sooner, rather than later.
I'm still running WinXP Beta. Oh, no wait a second.....
Because teenage pranks are fun when you're about to die!
Can't be Herr Ballmer, he hasn't sworn to Fucking Kill(TM) Linux even once.
"The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
Please get a dictionary and look up the definition for "arrogance". You seem to think that an arrogant person is one who shirks responsibility or likes to have easy excuses. I don't know what word you were really looking for, but it sure wasn't "arrogance".
*sigh* back to work...
Is anyone else tired of every asshat on the planet trying to compare computers and software to every other product in the world; from cars to soda pop?
Being a programmer, I like participating in my favorite products' forums. Like, I report a bug, and a couple of days later, it's "fixed in CVS". I only have to recompile, and voila.
Anyway, one thing that is very needed, is the frequent release of products (release early, release often), which is why I love looking at the latest beta's of a product.
However, what I wouldn't like, is having to widthstand an awful beta full of bugs, specially if i can't contact the programmer.
And it's even more frustrating if said "beta" is actually a finished product, like this one or this one.
Haven't you guys been frustrated by the stupid MSN window re-scrolling whenever your buddy types something and you haven't finished reading what you missed? It's a nightmare!
This is why I like beta. At least I expect bugs to be present, and I'm ASSURED that, since it's beta, those bugs will be fixed soon.
And beta is also where the newest features are implemented, and I can say "wow! you rock!" I think Beta is the best part of a software development.
So, it depends. Beta, for open source products, is a dream come true. For closed source products, it's a nightmare.
Even frogs notice being boiled alive
Never confuse volume with power.
I wonder if there are any compelling legal or fiscal reasons to keep software as "Beta" for a long time. Could beta software have less liability than production software? Does it matter in corporate accounting if the software is beta or production? I also had read once that Google News is still beta because of potential legal problems around republishing of the news content which for some reason didn't fall under Fair Use.
1. You can't afford actual beta-testers.
2. You're more honest than Micro$oft who's beta products are called New Releases. (eg WinXP+SP2 is the *real* finished product)
3. Most hired beta-testers are fairly tech savvy. Public beta allow you to get your releases tested by people who often aren't as clued up. You cant make software idiot-proof because idiots are ingenious.
4. People are more likely to suggest ideas than if they feel it is finished.
5. The users feel as though they are a part of creating it.
6. Someone else is releasing something similar and you want yours 'out there' first.
7. Its easier to type the greek capital letter for beta than gamma.
8. People are usually more forgiving of bugs/flaws in beta code.
9. Your product has been/will be in development a long time and you want people to see it before they lose all interest/forget.
I am a free slashdotter. I will not be modded, blogged, DRM'd, patented, podcasted or RFID'd. My life is my own.
Well... aside from marketing reasons and the like, Beta periods are longer these days because the software is typically more complex as well. You'd like a good beta audience to test your code breadth-wise and depth-wise, which may be difficult given some products (think about Microsoft Office and all the features and combinations of features you'd want tested).
Plus, there's always getting your product out in Beta form to let some air out of competitors' offerings. If you can get your game out in a pretty good beta, for instance, you might curb some of the fever for some other competing game has. Just look at the EQ2 and WoW Beta and release times, they were fighting who would release first to get a lot of initial sales.
Perhaps the question is not, "why do betas last so long, these days?" Perhaps the question should be, "why didn't betas always last this long?"
Seriously here, how much buggy software might have been avoided if manufacturers had been more concerned about the final product?
As a side-note: while the majority of software has experienced lengthening betas over the past few years, there is one market that has gone the polar-opposite: games. Ever notice how many patches come out for games, these days? Or how many really crappy games get rushed through just to get it out the door? Game companies could learn a lesson by following the rest of the industry, for once.
/dev/random
Their "BETA" reminds me of the early 90's where you came across sites with the damn "Under Construction" animated GIFs everywhere. All these new web-app betas are nothing more than the new "under construction" signs.
The premise behind a beta is to get the product into the customer's hands to increase the number of testers to improve the product. The OSS model of development uses this as a framework. Although versions are released as "final", it is understood that it can and will be changed quickly if any problems arise. I personally have gotten into several OSS while they where beta and still use them now.
I do find it frustrating when paid-for services are in perpetual beta. If a OSS is broke, I haven't paid anyone any money, and I "could" fix it myself if I wanted.
A software beta wont necessarily make you ill, but it may make you sick.
However a foodstuff (loosly stated) can make you both.
The secret of success is honesty and fair dealing. If you can fake those, you've got it made. (Marx)
free as in beer anyway. And neither is flawed or inadequate compared to their competition. So what's the problem? People are complaining that they want their free stuff to be perfect?
Beta means under construction, right? It means "here, play with what we have right now, but we're going to come out with a bunch of changes real fast." For software that you purchase in a box, there's a clear line between beta and non-beta software. The software that you purchase in a box in a store has a version number tied with it. You know that you are using v 7.0 or whatever. It had a definite ship date and list of features. You can't magically start using a new version. For web apps, it's a blurry line. Web apps can push out new builds several times a week, and many companies do, in fact, push out changes weekly - and roll them back when things go very wrong. So you think Google News, which has been out for several years, shouldn't be called beta? Why, because it's been out for several years? That doesn't mean anything. As we speak, Google is writing code and putting it into Google News. It's not like you're using the same version of Google News that you were using when it first came out. Every time they push a new feature - which could well be several times a month - it's in beta all over again. Frankly, all web apps that aren't released in "versions" should be called beta. Google's just more honest about it.
This has got to be the stupidest quote ever! Flawed products are constantly introduced and grow user bases . . . in areas where there is not already an established consumer base or need. To go for the prosaic example, look at George Foreman's damn grills. They were introduced and other similar products had not yet hit the mainstream. Where they perfect? No, and I still can't think of a decent use for them. But they were "flawed," as is made evident by mainstream competitors jumping into the market and introducing refinements.
Most new technologies, when introduced, are flawed: cars, computers, planes, building materials, etc. The difference is that on the software side, they are just finally getting a little more honest about it. For material goods, that change will probably never come. Who wants to drive around in a "Honda Civic, Release Candidate 2?" Between the financial outlay for material goods, and the inability to 'upgrade' to a stable release, it doesn't make sense.
However, if someone wants to hand out free software or provide a free service and call it 'beta,' what's wrong with that? It's truth in labeling and I can start reaping benefits from a new technology before it becomes 'stable' or 'feature mature.' So much of software is now open source, the development relies on a community of interested users and developers, and beta software allows that.
And if, as long as it is marked 'beta' the product or service continues to evolve and get better, who can complain about that? It's better than some Redmond-based company that has been charging people out the wazoo for years for software that, if it weren't for corporate mandated use, would have died a thousand deaths by now.
Say... did anyone ever actually manage to use up all their Gmail invites? Every time I got close, they gave me more. Did they start everyone out with a small number on purpose, so they'd feel "special"? Just a hypothesis. I have no proof.
I believe Microsoft, too, will jump the bandwagon seriously and label the next version of Windows (somewhat realistically), Windows Beta!
Like comment #14132447 said, "you get what you pay for" -- obviously, this, too, seems to be somewhat accurate in the case of Windows.
In the end, Beta is only good!...
THIS IS THE INTERNET. PLEASE PICK UP YOUR SERIOUS BUSINESS SUIT AT THE FRONT COUNTER.
Why Specifically?
The economics of a beta work out very well. It's cheaper, and gives them the advantage of nonbinding reviews. When you release a bad 1.0, you get bad press, and that image sticks in people's minds.
That I remember anyway was Linus Torvalds, because he didn't want people to use Linux 0.2 - 0.9 as production-ready, yet everyone knew it was at least as good as the "production" software everyone else was selling. Better than minix.
It started a (not good) trend... there were already too many excuses and justifications available to sell or publish bad software (including open source) and now there are more. How many freshmeat project web pages include the text "This software is beta" which the programmers include as a cop-out for mediocre or poorly written code? It's your own fault if it breaks, because it's beta.
Open Source software in general is too mediocre in quality. The thrill of release and accolades from users come from making the software in the first place and releasing it, not from the longer and more boring work of making it easy to use, bug free, or keeping it stable enough for production.
This is a major problem with the gift economy of free software... it's too easy for the gift givers to receive praise for giving us something worthless. It also dilutes the praise for those who truly deliver a valuable gift that may not look as shiny as some of the fool's gold projects out there.
Erik
PS: Taco, get Kupu
Because software development is difficult (at least writing something reliable for a large user base; any idiot can write 100 lines of script).
Because it makes a change from IT over-promising and under-delivering. No citations but add your own government, EDS, MS, project over-run feature-descoped effort here.
Honesty, may be? It's just not finished yet. Or laziness, it'll do - please excuse the errors - we're off doing something more interesting instead.
Again no link but from Uni I recall seeing a survey where users would prefer feature-rich and buggy against limited and boringly stable. (Any MS reference in replies is implicitly redundant, okay?)
"It's beta". Such a great excuse. Everybody's off the hook. Also: It's true. Everything is beta. When I was interviewing for entry level tech support back in the mid-90s, one of the test questions was "why might Netscape GPF"? I gave a laundry list of standard reasons, but at the end I put "the whole thing is really still beta anyway". The interviewer loved that and I got the job. Netscape had the gaul to take stuff out of beta, but it still crashed quite often. At least now they are being honest, although perhaps not for the right reason. Now, back to my much nicer job...
having a web product in "beta" state is simply the new fashion for web2 apps.
it gives a "cool" look, like "beware, you are testing and unfinished product" and at the same time avoids harsh complains about bugs because... "you are testing and unfinished product"
I think this is another example of the "worse is better" philosophy in action. Having just reread Richard Gabriel's article, I'll post a link to it: http://www.dreamsongs.com/WorseIsBetter.html. He is originally decrying the shoddiness of Unix software compared to ITS, TOPS-10, or LISP-M, but the point is valid here as well.
The whole point is that good software takes time to write, but that the last 20% of the functionality takes 80% of the time to write. Different end-users also have different ideas about what that 20% should be, compounding the problem. Why do you think that MS Office has so many useless features? They are trying to please everyone, which gets you nowhere. Far better to release something that is only 80% done and get to market first, because then nearly everyone is 80% satisfied. Otherwise you end up with a product years late, and only 20% better!
As for explicitly calling it "beta," hey, at least they're being honest with us!
Not only are they using you (xBox360 owners) as beta testers, they're using you (xBox360 detractors) to hide their real plans! When MS comes out with the xBox361 just in time to pre-empt any competetor's release, we'll see the true .
All hail Bill Gates, Hero of Capitalism!
Betas in general take so long because the first 90% of a project takes 10% of the time, and the last 10% takes 90% of the time...
Shoot Pixels, Not People!
Peter Sealey, a marketing professor at the University of California at Berkeley and former chief marketing officer at Coca-Cola Co. "I can't come up with anything else in the entire marketing world where marketers knowingly introduce a flawed or inadequate product [and] it helps grow your user base."
New Coke!!
Whatever bad things you might say about proprietary software, one good thing in terms of reliability is that it's typically statically linked. That means someone who sells a proprietary app can test with a particular version of a library, and then just keep on shipping the app with that version linked in. If a later version of the library comes along that they do want to switch to, they can test it carefully, and then roll it out. But as an OSS programmer, you're at the mercy of your users -- they could install any version of a library, and if it doesn't work right, they consider it to be your fault.
Find free books.
Google's Gmail works so well in "beta" form I could use it the rest of my life as is.
Software that is in Beta indefinitely should be called "abandoned".
So it's been in Beta a long time, being improved and should therefore be "abandoned"?
Fran
:):):)
1st 1st Poster of the new Millennium!
I think the move toward releasing beta( of course, I say beta software, what they are really releasing is Alpha software (how many "beta" programs have you used that have not had any features added?) ) software by companies is a move to "embrace and extend" the open development style that has served the F/OSS development communities. While some may argue that they are missing the most important ideological aspects of what makes F/OSS software great, I think that companies are finding that by allowing users to provide real feedback that will actually be used in the development of the application- and by allowing users to use software for free- they are able to make applications that appeal more to the target userbase (or modify the target userbase based on who they see using the application), and they can get people "hooked" before they start to charge for the software.
While I certainly do not have a problem with proprietary software using a modification of a traditionally F/OSS development method, I think that in the end this might have an unintended effect that companies may not forsee.
One of the big hurdles I see to people adopting Open Source software is that many people are uncomfortable using version 0.x of a program. With this big push to label software "Beta" people are going to become more used to the idea of using programs that aren't quite finished, or are labled as beta or development releases. As people get used to that idea, it takes away one more mental obstacle a lot of people have toward adopting F/OSS solutions.
Famous Last Words: "hmm...wikipedia says it's edible"
The reason people like products released as Betas, is because it's the most honest software companies ever get about their products. It's pretty much as simple as that; Beta implies under-constant-improvement, and even I as a consumer don't mind imperfect software, as long as the company will at least advise me it's been released in Beta - under construction.
True, but the problem with this is that, if it is over-used, the term loses all meaning. The whole point of a "beta" period is that, at some point in the foreseeable future, the product is expected to move into a "production" phase. This doesn't mean, of course, that it is completely finished and requires no more improvement. Even the most naive computer user today knows better than that. But when all (or at least the largest) developers leave their product in eternal beta mode, then eventually "beta" will mean nothing.
Look at google news closely. The articles are 90%+ AP, UPI and are the *same exact stories* from a thousand little places, either directly or a step away, albeit some have a word or three changed from the original copy. Whoopedy forking zinggy do there. That's the dirty little secret of newspapers and MSM broadcast "news" today, it's repacked crap they pull off the wires.. Google could just pop for a subscription to those two sources and be their own online newspaper legitimately, yahoo apparently does it already.
Google is just being cheap, and the critics are being ignorant and naieve, and the content owners would be hard pressed to try and counter current US copyright fair use provisions given Google offers an extremely small piece of the content, and gives exact reference and credit.
It's a manufactured non issue. Why? I don't know, but it sure is. In googles case I think it's so they can claim "thousands of news sources crawled by de minute!!1BBQ 11". Whoop! It's a few dozen really at best.
I think the funniest one is online newsrag A makes you REGISTER to go see the SAME AP or UPI crap you can get elsewhere without registering. Why would I want to "register" when the only thing I can't access at newsrag A is the pathetic local high school soccer scores and similar?
Big fat jokeski
That it is run by Google? Using their special 'searching algorithms'? It's Yet Another Web-Based Mail System. Nothing there that hasn't been done many times before.
Blar.
I'm used call it "Banana Software ... maturating at the customers expense"
I still remember the mid-90's, when application software widely sucked, and I remember loving betas because they offered a glimpse at the future which might not suck as much. New features, bug fixes, an interface that wasn't complete shit... betas had it all. Sure, sometimes they were crashy, but so was everything, and it wasn't like there were all that many bugs that made an application unusable.
You see? You see? Your stupid minds! Stupid! Stupid!
...so I wouldn't think the current trend of long-running beta releases has anything to do with whether or not they're ready for prime time. It sure looks like a lawsuit avoidance tactic to me.
Yes, at some point improvements should be captured in a production release and the next improvements can be Beta again. The point is to have something to rely on (i.e. no scripting vulnerabilitites and such) due to testing/hardening of a certain release. Endless improvement != endless Beta
Simple,
If you're in beta you're likely not to get sued for security issues and other "nasties" of complex developments.
There are only 10 kinds of people in the world. Those that understand binary and those that don't.
Maybe the FTC needs to step in. Throw the "Beta" tag into the "New and Improved" bin somehow. Just as companies can only advertise something as "New and Improved" for so long, software can only carry the "Beta" label for so long..
Of course, OSS is one of the worst offenders. There is an implied "Beta" for software with a version 1.0 IMHO. How much OSS that has been around forever (openSSL anyone?) still has a version 1.0?
Just my $0.02
Why you complaining about Beta.... WINE has been in Alpha for YEARS.
(ok maybe they officially just became a beta but still)
My karma's to high, must bring back to reality.
Blender And Linux Fan
"I can't come up with anything else in the entire marketing world where marketers knowingly introduce a flawed or inadequate product [and] it helps grow your user base."
This guy must have been talking about Windows!
Now if a site goes south, and it's production, there is hell to pay.
but it goes south and it's BETA, it's like you are a hero for finding a problem!
Another reason might be is because you can. Software can be 'shipped' or tested even if not complete. It is dificult to ship a TV or a car that is fully not ready. i.e. you cannot ship a car, and say in a couple of months the engine will follow. In the case of software that almost works, it is easy enought to 'ship' a patch of a more complete product. In the case of server based web driven software it is even easier.
You are right that the ultimate provider of the stories are AP and other newsfeeds, but they are on the sites of other news providers (nytimes.com, cnn.com etc), and they have just as much legal basis to get pissed as they would have if the stories in question were locally available content. Just being supplied by the AP does not mean that the same legal strategies that have worked against "deep linking" could not be applied here.
That said, I'm still skeptical whether this was the reason that Google News is still in beta.
This has got to be close to the record. Hotmail support in Outlook Express been in beta for the best part of a decade. I reported the bug where it downloads duplicates of messages 7 *years* ago! The (automatic) response? This product is in beta (so don't expect us to do anything about it). Microsoft clearly use the term "beta" to free themselves from the obligation of product support.
One of these days I'm moving to Theory - everything works there
"I can't come up with anything else in the entire marketing world where marketers knowingly introduce a flawed or inadequate product [and] it helps grow your user base." '"
So says Peter Sealy.
The funny thing is both beta's mentioned by the article are not flawed or inadequite. Todays betas are far closer to an actual realease than previous generations of software.
Also they forgot to mention that betas are typically free. Who wouldn't want free near commercial grade software?
I've heard they're very enduring.
But, alas, my daughter's beta always lay at the bottom of the aquarium. It is quite vivid as it recognizes me and starts to swim quickly as I approach to feed it (I guess it must be saying in fish lingo: "I'm not dead yet!").
I already gave it that green medicine but to no avail. Maybe the disease is irreversible, maybe it's no disease -- just age... maybe it's a bummer and wants to lay down all day long -- hey, it must run in the family!
Anyway, any veterinarian in the room by any chance?
Remember when Orson Wells was hawking Paul Masson wine in the 1970's? "We will sell no wine before its time."
While I may be anxious for software to "go gold", there is a reason why there is a wait - it's not ready.
It may still be crap when it is eventually released, but at least its not as crappy as it would have been had it been shipped early.
is that off-topic or just [+0.5 mildly interesting] ?
... in different situations. Or maybe I just have different expectations for different types of beta products.
As an example, look at a free web app. It should be easy to deploy new features quickly. It should be easy to fix bugs and release them to the user quickly. An extended "beta" period is okay as long as there's constant improvement and the number of defects is kept low. Users will tolerate a bump in the road every once in a while.
With a desktop app where the vendor doesn't have control over the users machines, you can't deploy a new version of your app instantly. That changes everything. I'm expecting a beta release to feature complete (mostly). I'm expecting more defects, but I'm also expecting the focus to be on removing defects, and not adding new features. An extended beta period is bad because it tells me that new bugs are always popping up. But development is proceeding like in my first example (new features and low number of defects), then calling your product a beta may be sending the wrong message.
Then again, if you're continuously adding features and keeping defects low, then "beta" is probably a bad way to describe your product. It's beta, but with a wink or an asterisk at the end.
What's wrong with being conservative and cautious as opposed to MS which thinks your hard drive ist their sandbox?
Try this formulation:
And guess what? The user base for flawed product Bush beta 1 DID grow, resulting in a greater user base for the subsequent Bush beta 2. I can't say whether this trend is going to continue.
not that I disagree with what you said but google news has been in beta for 3 years most likely because of4 1&tid=217
http://slashdot.org/article.pl?sid=04/09/29/21142
sarchasm
Sometimes it's just a name, if a program does what I want and works how I want and is reliable enough for me, it doesn't matter what the name of it is.
Beta doesn't mean releasing sooner; it means being buggy longer, but with liability protection.
Saying "It's just a beta" generally means that it's still got bugs to work out. This is another way of saying "it might eat your lunch, and we're not liable for that". Though the legalese might say that too, it looks better in court if it's trumpeted with a term like "beta" which most users understand, instead of in fine print which they don't.
That, and you can't uninstall the old ones because it'll break all of them.
You were supposed to uninstall the old version before you install the new one. That would prevent the duplicate entries in Add/Remove Programs. Your bookmarks/cookies/extensions/ect would be safe because they are stored in the profile folder, which is not removed when you uninstall Firefox.
"I can't come up with anything else in the entire marketing world where marketers knowingly introduce a flawed or inadequate product [and] it helps grow your user base." It seems he's never heard of "Windows"
The problem with Google's "beta" offerings is that for the most part they aren't really "in beta", they are really abandoned. No one at Google is working on them. There are no new releases planned. They were worked on for a while until their creators got bored and moved on to other projects.
All these Google services have been in Beta for more than a year, have serious bugs, no support, and no signs of development:
I'm glad to see that someone on Wall Street is starting to take notice. Maybe this will shake things up at Google and get some action. I have 201,322 messages in the trash mailbox of my gmail account (stuck there since August of 2004 when I filled up my 1 GB allocation after just 4 months of use...) and I'd REALLY like the "messages that have been in Trash more than 30 days will be automatically deleted" function to operate as advertised. Deleting them 100 at a time (the only way to delete them manually) is not feasible.
jc
"I'd much rather be mistaken as a lesbian by a bigot than be mistaken as a bigot by a lesbian."
There's a perfectly good reason why people like beta software. Sure, it contains bugs -- but so does production software. However, beta software is in a state of constant improvement. Actual people, right now, are working on the product to make it better. If you run into a problem, there's a good chance it'll be fixed reasonably soon. Designating software as a final release means that the developers (or managers) think it's "good enough" for now. Still not good enough for you? Well, too bad.
This is part of the appeal of open source software: the software is in a constant state of improvement. If the original developers aren't improving it, you can improve it yourself, or find someone who will. The software is never "final," and never orphaned, as long as it's open.
Cheers,
IT
Power corrupts. PowerPoint corrupts absolutely.
I disagree with your logic. However, this post is still in beta, and as such, my points are not yet complete.
Waltre cannot be held accountable for whether the punter reading this post is amused, since it is still in beta. My roadmap includes many points of argument, a new sig, and some funny bits.
Isn't this how all products work? Sell it, then milk the flaws via repairs/service/replacements.
http://en.wikipedia.org/wiki/Planned_obsolescence
One place I worked I used to stamp every document "DRAFT". That way if anybody complained, I could simply say, "It's only a draft".
Table-ized A.I.
As long as you're posting grammar tips in your sig, it's "betas", not "beta's". "Beta's" would be the abbreviation for "beta is".
PenguiNet: the (shareware) Windows SSH client
ICQ
Mirabilis hasn't released an actual 1.0 version in oh, 10 years.
"No problem. I have the capacity to do infinite work so long as you don't mind that my quality approaches zero."-Dilbert
Isn't it basically a way to save your ass when something doesn't work as advertised?
Perhaps its those little pellets that they eat? Or maybe the bloodworms, they like bloodworms. Or perhaps its because they do not have the same requirements as other exotic fish, such as goldfish or clown-fish; they can live in low oxigenated water, and eat pretty much anything a fish could eat. It also helps not having other fish around for it to fight with (they usually fight to the death!).
I know I have a Beta (his name is Fishy, by the way), and it has lasted so far almost a whole year! (We got it for Christmas last year).
-dZ.
Carol vs. Ghost
"I can't come up with anything else in the entire marketing world where marketers knowingly introduce a flawed or inadequate product [and] it helps grow your user base."
Spoken like a true 'marketer' I would say. Surely most manufacturers would admit that they have not 'perfected' their product before taking it to market. In fact I believe it is those very same 'marketers' that apply the pressure on the manufacturing part of the business to release a product to take advantage of 'time to market' when that product may well be far from perfect.
It is also true, as many have said already, that software is somewhat unique in that modifications can be fairly easily distributed, so people still working on the product can improve something that people already have.
The wide use of a 'beta' also provides far better user testing than could be performed in-house and provided the beta phase proves responsive to user feedback then the overall confidence in the company, from its customers, benefits as well.
Don't marketing types call this stuff 'win-win' or something ?
I am a budding (Mac OS X) shareware author, currently running an open beta.
...
I am intending to charge about $35 for my software, but am currently giving away limited duration (three month) licences for free.
Before going public, I ran a closed beta for about three months, with 20 or so users that I recruited from various Mac OS X forums. This helped me eliminate the most egregious and common issues.
My public beta has now been running for about a month - I've had a couple of thousand downloads, and nearly four hundred registered users - mainly finding me through version tracker and macupdate listings.
The quality of the bug reports from my public beta users has generally been fantastic (it may help that I've promised bug reporters free permanent licences) - I have about 24 bugs in my bug tracker, of which 10 are open, and maybe half of these are serious. Generally my public beta users have been far, far more productive than my closed beta users - there are lots of issues that you simply aren't going to hit until you get out to a relatively large number of users, and these bug reports are like gold.
Once I've closed the remaining serious issues, and added one remaining feature, probably early in the new year, then I'll end the public beta, start doing publicity and send the product out for review, and start charging for licenses.
This seems like a very good deal for both sides to me - poossibly even a virtuous circle. Beta users get free early access to the software, but are aware that there may be unresolved issues. They also get a chance to influence the final form of the product - one could look at that in a very cynical way (they're doing the developers work for them), but the impression that I get is that people really appreciate this,
From the developers point of view, the larger public beta base enables a much higher quality final product, which clearly beneficial to both sides
i think it would be etaBay...
anyway, eBay comes from the name for an auctionhouse, or a "bay"
Actually, no. That would be pig latin for "Beta", not "B".
anyway, eBay comes from the name for an auctionhouse, or a "bay"
Actually, no. It stands for Echo Bay, as Echo Bay was the original name of the Consulting Firm of the founder.