murraybiscuit
Executive Member
some comic relief. finally. this thread was getting a bit intense.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Tis the voice of the lobster..
the problem with piracy is that it's unlike other theft - the user ultimately has the ability to recreate the product and can thereby become a manufacturer themselves, without the costs of production. with most other products, the manufacturer is also the only person able to duplicate the product and thereby retains control of revenue.
@peterCH, i disagree.
to use your analogy of supply and demand:
in a free market, if you have x cash and you need x tool in order to create x product, you have choices:
1. buy a cheaper tool and sell your product cheaper
2. buy the more expensive tool and pass that cost on to the consumer
3. sell at the same price and pocket the profits yourself, which means you'll be undercut pretty quickly.
4. if a cheaper tool does not exist, because the demand will arise
thus, supply, demand and competition regulate the free market because buyers have a choice. the problem comes in when you decide not to buy the alternative, but to steal the original.
this effectively means that:
1. your competition will go under (you will always be able to undercut them)
2. the tool manufacturer will go under (they get less and less revenue)
3. there is no incentive for other companies to provide cheaper tools, because you can always have the best one for free.
You don't have a clue what it takes.
Yes, but unlike the manufacturer of tangible goods you don't have to worry about material costs to produce a product. Heck I'll take it further, if your warehouse gets robbed and 10,000 copies of software are stolen, you can recreate them with relatively little expenditure. You could even block the serial numbers of the stolen software if you have such a service running.
That only happens when someone 'steals' a software package instead of buying it. The 'instead of' is a very important point of contention here.
In these latest BSA ramblings, and in ramblings by the RIAA/MPAA/and other shill groups, made up figures based on subjective projections of expectations of what people should buy are not in line with reality.
So as with my example of Autodesk Autocad and engineering co's in JHB,
if you can prove that a certain number of copies is being used by businesses who could easily have afforded the software and would not have gone with cheaper or free alternatives, or none at all - such as fewer AutoCad licenses, if you can prove that - I will agree with you. I agree with you on principle but so far we're only seeing thumbsuck made up figures with no grounding in reality.
Perhaps you then need to offer value added services with your tool.
If your software is affordable, AND GOOD then very few businesses will want to do without it. If you give them value added benefits - such as good documentation, freebies, support - well you sell a product no pirate can reproduce.
Indeed I DO know what it takes!
I am currently developing a game server emulator for Aion written in java. This will be distributed FREE open source!
There are of course exceptions to every rule and yes you need to be rewarded for your hard work...There are just some who quickly develop something and then want to sit back and let that feed them forever, where in all probability you could find something in open source that fits the bill nicely!
your material cost is whatever your cost is to produce your product. in the case of software, it's your programmer's time, software, hardware etc.
this is built into the end cost for the consumer. loss of stock would equate to a server crashing and losing code - it would mean downtime/loss of revenue - a risk which can be underwritten by insurance.
Agreed. Basic stats 101. we're talking about people who should otherwise be buying the software here. if you download it and don't use it, you are the idiot for wasting your bandwidth.
hence my comment that the more software is purchased, the more the cost can be passed on to the consumer, in a free market with competition. it may be a simplistic example, but it illustrates the point.
but that doesn't address the ethical issue of piracy![]()
Care to elaborate? When does anyone have the right to decide who can use use their software when they put it on the common market?But they are deprived of the right to decide who can use their intellectual property.
Errr...also a software programmer, and 5+ years is an extremely long time to be working on any software, to the degree where one has to wonder if there is any point anymore? It's certainly not the industry norm, so you can't go getting upset because you want compensation for your 5+ years of work when it shouldn't be more than 6 months anyway.You don't have a clue what it takes. I've spent more than 5 years working on my current project. ... I've spent more time studying, writing and than many highly paid professionals in their respective spheres.
Care to elaborate? When does anyone have the right to decide who can use use their software when they put it on the common market?
Errr...also a software programmer, and 5+ years is an extremely long time to be working on any software, to the degree where one has to wonder if there is any point anymore? It's certainly not the industry norm, so you can't go getting upset because you want compensation for your 5+ years of work when it shouldn't be more than 6 months anyway.
I have the right to say "Please don't" = You can request. You never get to decide who uses your software when you put it into the public domain. From then on, it's the public's choice, not yours. Including whether or not to pirate. That's why PeterCH was saying your argument is based on selective ethics. It's wrong because I say it's wrong is not a valid argument. Piracy is a risk you accept when you publish software. You can't claim that you don't expect anyone to pirate software. You know it's going to happen.Point 1: I have the right when I say: 'Please do not copy my product for personal use or other without paying for it'. You'd have to be stupid not to understand that.
It depends on the software and the development methodology. Over half a decade is still unusually long, on average.Point 2: Huh? 6 Months? You are not a programmers ball. It often takes 6 months or more just to get a specification right for a new development.
I have the right to say "Please don't" = You can request. You never get to decide who uses your software when you put it into the public domain. From then on, it's the public's choice, not yours. Including whether or not to pirate. That's why PeterCH was saying your argument is based on selective ethics. It's wrong because I say it's wrong is not a valid argument. Piracy is a risk you accept when you publish software. You can't claim that you don't expect anyone to pirate software. You know it's going to happen.
Well strictly speaking, copyright is purely a right to retribution. It doesn't prevent piracy. All it does is give you legal recourse should IP theft happen. If you want to enforce copyright on your IP, you agree to that system of working. IE: If someone breaks your copyright, sue them, don't moan about lost revenue. That's the methodology you've chosen to work with. There are only pirates because there are copyrights. And it's a system that's a proven failure across digital systems, be it software, music, or movies.So do we do away with copyright altogether?
So do we do away with copyright altogether?