Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

[REBOL] Re: Licensing, components ... Re: REBOL FAQ updated

From: greggirwin:mindspring at: 13-Sep-2002 14:11

Hi Jason, Just to voice my own opinion... << The only reason people will use REBOL these days is because they have fallen in love with the language and love to explore. >> Or because they can see the potential and are willing to a) deal with the licensing issues; or b) work with RT to come up with a licensing model that is viable for them. I have nothing agaist Perl, Python, or any other language (If I hadn't found REBOL, I might be using Ruby right now), but I come from a different world, a world where I paid for the software I used, so that's OK with me. On one hand, some languages are free, OTOH Visual Studio .Net costs from $1,000 to $2,500 (an upgrade is $550). Do I like their current licensing model? Not entirely. I also come from a world where tools that required royalties fell out of favor very quickly. I'm a simple guy and I want to keep things simple. The thing that is off-putting to me is the extra accounting/paper-work involved, much more than the money. Also, I think encap was an annual license so there's no point in buying it until I have a product ready for testing and a site up through which to sell it. I think the new model they proposed a while back would be good. Give the full power to people that want to try it out, create shareware, etc. so they can do everything on a "trial" basis. Then charge them if they start making money with it, use it internally at a business, etc. For me, I'd like to pay once and not have to worry about it after that. If I want to protect my code, I'll buy encap. If I distribute things in source form, say shareware style stuff, is that valuable to them as far as getting the word out and making REBOL visible to more potential users/buyers? If so, should I pay less? I'm *more* than willing to pay $100 (current View/Pro price) to do that, but I can't ask users to pony up $100, on top of a small shareware fee to use my app. Now, the trick is how to get those new users to pay if they already have *my* licensed version on their system? Since we don't know everything they know, it's hard for us to make truly informed decisions, but I think they do listen. Like us, they do what they think think is best. --Gregg