All software sucks.

All software sucks.

I figure lots of predictions is best. People will forget the ones I get wrong and marvel over the rest.

Everybody in the real world will agree - the moment a project is behind deadline, quality assurance tends to go out the window.

Live fast, die old, and make very sure everyone knows you were there.

All software sucks.

Defect-free software does not exist.

Software development is technical activity conducted by human beings.

Digital art software has empowered both the painterly side of photographers, and the photographer side of painters.

Red Carpet Enterprise has been really well received since one guy can install it in about an hour, and it makes it trivial to deal with software management issues like deploying updates and creating standard package sets for your various machines.

Adding manpower to a late software project makes it later.

As every new breed of virus is conceived, created and released into the wild, another small change is made to the anti-virus software to combat the new threat.

While the creative works from the 16th century can still be accessed and used by others, the data in some software programs from the 1990s is already inaccessible.

Twenty-five years ago, the notion was you could create a general problem-solver software that could solve problems in many different domains. That just turned out to be totally wrong.

Diaspora starts about a thousand years from now. Most of human civilisation has moved inside computers; essentially, a major branch of our descendants consists of conscious software.

We also had good software in the key categories and more focus on the gameplaying capability, so more of the marketing effort was targeted at game customers.

None of our competitors have ever made two systems that run the same software.

I want people to use Perl. I want to be a positive ingredient of the world and make my American history. So, whatever it takes to give away my software and get it used, that's great.

When it comes to software, I much prefer free software, because I have very seldom seen a program that has worked well enough for my needs, and having sources available can be a life-saver.

However, writing software without defects is not sufficient. In my experience, it is at least as difficult to write software that is safe - that is, software that behaves reasonably under adverse conditions.

Since when has the world of computer software design been about what people want? This is a simple question of evolution. The day is quickly coming when every knee will bow down to a silicon fist, and you will all beg your binary gods for mercy.

I think it is important for software to avoiding imposing a cognitive style on workers and their work.

By the time Apple's Macintosh operating system finally falls into the public domain, there will be no machine that could possibly run it. The term of copyright for software is effectively unlimited.

The scanning of barcodes, or the reading of RFID transponders, generates data that is used in a software package to provide management or control information.

You get the software you pay for. In every sense. To the nth degree. That's the way the world works.

I want to avoid locking people into solutions that work only with Postfix. People should have a choice in what software they want to use with Postfix, be it anti-virus or otherwise.

I developed some unique software to public it on the web that I call the Folklore Project.

Shareware tends to combine the worst of commercial software with the worst of free software.

So what I was essentially doing was, I compromised the confidentiality of their proprietary software to advance my agenda of becoming the best at breaking through the lock.

People enjoy the interaction on the Internet, and the feeling of belonging to a group that does something interesting: that's how some software projects are born.

From day one our next generation system will run all our exsisting software - so that gives us a head start.

Qmail out of the box works fine, so people will want to use it regardless of licensing restrictions, even when the software does not ship with their system software.

When I write software, I know that it will fail, either due to my own mistake, or due to some other cause.

The challenge with Postfix, or with any piece of software, is to update software without introducing problems.

We've been in the Mac software business for more than 20 years. And it's been a great business for us.

Well, user feedback was excellent. Even when the software didn't work at all, there were few people who were avid users, and there were people who were just sending excellent feedback and excellent ideas.

Then people started using it more and more and it became the most downloaded software on the internet.

We're entering a new world in which data may be more important than software.

I don't believe in government regulation of the software industry.

Why shouldn't we give our teachers a license to obtain software, all software, any software, for nothing? Does anyone demand a licensing fee, each time a child is taught the alphabet?

In software systems it is often the early bird that makes the worm.

There is no neat distinction between operating system software and the software that runs on top of it.

Of course, all of the software I write runs on Linux; that's the beauty of standards, and of cross-platform code. I don't have to run your OS, and you don't have to run mine, and we can use the same applications anyway!

Like all software, Qmail can survive only when it keeps up with changing requirements.

Computers have become more friendly, understandable, and lots of years and thought have been put into developing software to convince people that they want and need a computer.

With bundled machines you can throw away the hardware and keep the software, and it's still a good buy.

I think we're proving ourselves as we go along. The past several months our strategy has been evolutionary - making maximum advantage of our client browser, as well as our enterprise software for people who want to build Web sites.

Most of the effort in the software business goes into the maintenance of code that already exists.

Our strategy in dealing with patents in Mono is the same strategy that any other software developer would take. In the event of a patent claim, we will try to find prior art to the claim of the patent.