Live data from Hacker News

First platform to sell ruby gems?

gemforsale.com

11–20 of 25 posts

Re: First platform to sell ruby gems?

#11
Slightly off topic, but I'm curious about the page's design. There have been a few others with the exact same kind of general vibe (showoff.io comes to mind first). The grainy background, sunken dark text, the whole thing.

Is it just designers borrowing ideas from each other, or is there something I've missed?

Re: First platform to sell ruby gems?

#12

Slightly off topic, but I'm curious about the page's design. There have been a few others with the exact same kind of general vibe (showoff.io comes to mind first). The grainy background, sunken dark text, the whole thing. Is it just designers borrowing ideas from each other, or is there something I've missed?

Not quite the same, but there was a lot of love for Tweetie's sunken logo (http://i.imgur.com/u6u4v.png). Twitter bought that app out and started using their fat bird instead :'(

Re: First platform to sell ruby gems?

#13
It pretty much contravenes the current community conventions surrounding Ruby and the sharing of gems. Good luck selling that to a community that was built by people sharing ideas and code while having them peer-reviewed, who are also adamantly opposed to the idea of selling snippets of code.

Re: First platform to sell ruby gems?

#15
Its great that the ruby community has traditionally made so much code available for free.

But certainly there must be things that would only be implemented if the costs of doing so were defrayed.

But it will certainly complicate things like deployment. Will we be putting license codes into bundler eventually?

Re: First platform to sell ruby gems?

#17

Slightly off topic, but I'm curious about the page's design. There have been a few others with the exact same kind of general vibe (showoff.io comes to mind first). The grainy background, sunken dark text, the whole thing. Is it just designers borrowing ideas from each other, or is there something I've missed?

I don't pretend to be a designer (I know how to use photoshop though) and I designed this page in 2 hours. I assume I follow the current trends. Nothing wrong, is it ?

Re: First platform to sell ruby gems?

#18

It pretty much contravenes the current community conventions surrounding Ruby and the sharing of gems. Good luck selling that to a community that was built by people sharing ideas and code while having them peer-reviewed, who are also adamantly opposed to the idea of selling snippets of code.

first, who speaks for the whole ruby community ? all the ruby/rails developers are a part of the ruby community but we never signed a paper telling us that we must not sell snippets of code. Besides, just to remind you something, I spent an extraordinary number of (not paid) hours on my open source project which is used by people making money of it (which is fair and I'm totally fine with that).

Anyway, I don't have in mind to replace the ruby gems platform by something else which will be not free. really. And trust me, that won't happen because it won't work.

But, in some situations like mine with LocomotiveCMS, having a platform to sell modules (it happens that my modules are ruby gems) makes perfectly sense. And what I'm looking for here by posting this is to see if other people will be interested in as well.

Believe me, I'm not the evil, not at all

Re: First platform to sell ruby gems?

#20
post #7

gem should be free.. I hate this idea. What if I want to fork the code ? And I don't want to put licenses all around the place when it comes to deployments.

I should have explained the context of the idea. I just wanted to sell a tool for my cms (locomotivecms). This tool happens to be a ruby script which is regularly updated and that I want to sell to "finance" the cms (free of charge since it's an open source project). And the best way I found is to sell it as a ruby gem so that the installation / update become easy for the ruby users.

By the way, the code is not obfuscated. So yes, basically, users who paid for the gems can put this in their own git repository and do "whatever" they want with it as long as they don't share it.

Does it make sense ?

Post reply on HN