Since you write web based apps with rails, it wouldn''t matter if it was
licensed under the GPL.
The code you write for your app is your code, not a derivative of rails,
so you can use your choice of license for your code.
If you host your app on a server, and your users browse to that server.
You never have to distribute your code. If you do redistribute copies of
Rails to your end users you are allowed to under the MIT license, but
you would be allowed to under the GPL as well.
If you choose to distribute your code, then choose an appropriate
license for your code.
Now, If you are planning on taking the Rails code and forking that code
into your own web framework, that''s when you have to worry about the
license Rails is under. But that is a completely different situation
than using rails to host an app you are writing.
Heck you can buy a copy of Microsoft''s Visual C++ and write proprietary
closed source code with that, or you can write MIT or GPL code with it.
It is under a much more restrictive license than GPL or MIT. The code
you write and the tool you use to write and run it are two different
things.
In the same way, you could use the GPL''d compiler gcc to write closed
source proprietary code if you wished.
(In both the gcc and visual C++ cases, you may not be allowed to include
other people''s libraries in your end product depending on their
licenses.)
-Sean
Edgardo Hames wrote:> Hi guys,
>
> I understand Rails is licensed under the MIT license, does this allow
> me to write proprietary applications with Rails?
>
> Thanks a lot,
> Ed
>
> --
> Encontr? a "Tu psic?pata favorito" http://tuxmaniac.blogspot.com
>
> Thou shalt study thy libraries and strive not to reinvent them without
> cause,
> that thy code may be short and readable and thy days pleasant and
> productive.
> -- Seventh commandment for C programmers
--
Posted via http://www.ruby-forum.com/.