Re: [MacRuby-devel] Failing installers
Thanks Mark, you're guess was right.
I'm using Xcode Version 4.2.1
After trying the script, I discovered that it was failing on
"XCODE_DIR=`xcode-select -print-path`"
so I looked it up and ran "sudo xcode-select -switch '/Developer'" and then
tried the installer again, and it worked.
I've never seen any of these commands before, so I'm not sure how that got
broken.
Thanks for the help, I will log the details in a bug report.
Fb
On 03/05/2012, at 00:44, Mark Rada wrote:
> Hmm, that does sound strange.
>
> The script that the installer runs is found here:
>
> https://github.com/MacRuby/MacRuby/blob/master/misc/release/package_script/postinstall
>
> I would guess that it is not able to get the Xcode dir properly and failing
> to set it up.
>
>
>
>
> On 2012-05-02, at 2:03 PM, stephen horne wrote:
>
>> Ok, thanks. Xcode is installed, and I don't remember doing anything funny to
>> it, but it's entirely possible I broke it somehow as much of it is beyond my
>> understanding - I will see if I can figure it out and log a bug if I do.
>>
>> fb
>>
>> On 02/05/2012, at 18:45, Mark Rada wrote:
>>
>>> The script might fail if you do not have Xcode installed or something is
>>> unusual about your Xcode setup.
>>>
>>> To answer your other question, everything except Xcode integration should
>>> be installed by the time that the failing script is run.
>>>
>>> Also, if it turns out to be something with your setup of Xcode, could you
>>> please log a bug with details? This seems like it should be a blocker for
>>> release.
>>>
>>> Sent from my iDevice
>>>
>>> On 2012-05-02, at 12:42, stephen horne wrote:
>>>
It's been a while since I installed a nightly build because I get a error
in the installer ("Installation failed", and "An error occurred while
running scripts from the package “macruby_nightly-2012-05-02.pkg”"), and I
haven't had the time to look into it.
I've just given it another go, and, to my eyes, it seems to have installed
everything it should have:
/Library/Frameworks/MacRuby.framework
/usr/local/bin/macgem
/usr/local/bin/macirb
/usr/local/bin/macrake
/usr/local/bin/macrdoc
/usr/local/bin/macri
/usr/local/bin/macruby
/usr/local/bin/macruby_deploy
/usr/local/bin/macruby_select
/usr/local/bin/macrubyc
/usr/local/bin/macrubyd
Does anyone know if that is everything? Can I just ignore the installer
error if the above is in place?
Cheers
--
Fb
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>> ___
>>> MacRuby-devel mailing list
>>> [email protected]
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> --
>> Stephen Horne
>>
>> ___
>> MacRuby-devel mailing list
>> [email protected]
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> ___
> MacRuby-devel mailing list
> [email protected]
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
--
Stephen Horne
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
This is awesome! I'm in. On 2012年5月4日Friday at 上午1:02, Laurent Sansonetti wrote: > Hi guys, > > I am extremely excited to announce the immediate availability of > RubyMotion, a revolutionary toolchain for iOS development in Ruby. > > (RubyMotion is what I have been working on these last 6 months. :)) > > RubyMotion is a commercial flavor of MacRuby for iOS that includes an > optimized runtime, a brand-new static compiler and memory model, and a > command-line interface. > > If you are familiar with MacRuby you should be all set to develop iOS > apps right away. > > You can find more information about RubyMotion on its website. > > http://www.rubymotion.com > > For a limited time only, RubyMotion can be purchased at a 25% discounted rate. > > The developer center features guides, articles and a pointer to the > sample code repository. > > http://www.rubymotion.com/developer-center > > Also, the awesome folks at The Pragmatic Studio released an amazing > 50-minute screencast on the product. Check it out, it's free! > > http://pragmaticstudio.com/screencasts/rubymotion > > If you want to stay connected, make sure to follow @RubyMotion on Twitter. > > http://twitter.com/RubyMotion > > Enjoy! > > Laurent > ___ > MacRuby-devel mailing list > [email protected] (mailto:[email protected]) > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
This is awesome news - congrats Laurent!! Aston On 3 May 2012, at 18:02, Laurent Sansonetti wrote: > Hi guys, > > I am extremely excited to announce the immediate availability of > RubyMotion, a revolutionary toolchain for iOS development in Ruby. > > (RubyMotion is what I have been working on these last 6 months. :)) > > RubyMotion is a commercial flavor of MacRuby for iOS that includes an > optimized runtime, a brand-new static compiler and memory model, and a > command-line interface. > > If you are familiar with MacRuby you should be all set to develop iOS > apps right away. > > You can find more information about RubyMotion on its website. > > http://www.rubymotion.com > > For a limited time only, RubyMotion can be purchased at a 25% discounted rate. > > The developer center features guides, articles and a pointer to the > sample code repository. > > http://www.rubymotion.com/developer-center > > Also, the awesome folks at The Pragmatic Studio released an amazing > 50-minute screencast on the product. Check it out, it's free! > > http://pragmaticstudio.com/screencasts/rubymotion > > If you want to stay connected, make sure to follow @RubyMotion on Twitter. > > http://twitter.com/RubyMotion > > Enjoy! > > Laurent > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
Awesome job. Congrats on shipping! On Thu, May 3, 2012 at 1:12 PM, [email protected] wrote: > This is awesome news - congrats Laurent!! > > Aston > > On 3 May 2012, at 18:02, Laurent Sansonetti wrote: > > > Hi guys, > > > > I am extremely excited to announce the immediate availability of > > RubyMotion, a revolutionary toolchain for iOS development in Ruby. > > > > (RubyMotion is what I have been working on these last 6 months. :)) > > > > RubyMotion is a commercial flavor of MacRuby for iOS that includes an > > optimized runtime, a brand-new static compiler and memory model, and a > > command-line interface. > > > > If you are familiar with MacRuby you should be all set to develop iOS > > apps right away. > > > > You can find more information about RubyMotion on its website. > > > > http://www.rubymotion.com > > > > For a limited time only, RubyMotion can be purchased at a 25% discounted > rate. > > > > The developer center features guides, articles and a pointer to the > > sample code repository. > > > > http://www.rubymotion.com/developer-center > > > > Also, the awesome folks at The Pragmatic Studio released an amazing > > 50-minute screencast on the product. Check it out, it's free! > > > > http://pragmaticstudio.com/screencasts/rubymotion > > > > If you want to stay connected, make sure to follow @RubyMotion on > Twitter. > > > > http://twitter.com/RubyMotion > > > > Enjoy! > > > > Laurent > > ___ > > MacRuby-devel mailing list > > [email protected] > > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
This does look awesome, and I just bought a license - the price is less than the prevailing rate for an hour of iOS dev time, and you deserve to be paid for your hard work. That said, I'm wondering if/when any of this will become open source? It's been a long time since I trusted proprietary code more than open source stuff. Open source projects can aways be forked or maintained by someone else, but if a proprietary company drops support for whatever reason, your codebase depending on them is in trouble. I'm not trying to suggest in any way that you guys would do that, but it does make me a little nervous suggesting using this to any of my clients. Sorry if this comes across as a downer, I'm really excited about this project and would love to use it, I'm just curious about future plans. I wonder if this could be handled with a dual license - perhaps free/open source apps could use it for free, but paid apps would require a license? I think that would encourage a lot more people to use it overall. Anyway, thanks for your hard work, and I'm looking forward to testing it out. - Ian On May 3, 2012, at 12:02 PM, Laurent Sansonetti wrote: > Hi guys, > > I am extremely excited to announce the immediate availability of > RubyMotion, a revolutionary toolchain for iOS development in Ruby. > > (RubyMotion is what I have been working on these last 6 months. :)) > > RubyMotion is a commercial flavor of MacRuby for iOS that includes an > optimized runtime, a brand-new static compiler and memory model, and a > command-line interface. > > If you are familiar with MacRuby you should be all set to develop iOS > apps right away. > > You can find more information about RubyMotion on its website. > > http://www.rubymotion.com > > For a limited time only, RubyMotion can be purchased at a 25% discounted rate. > > The developer center features guides, articles and a pointer to the > sample code repository. > > http://www.rubymotion.com/developer-center > > Also, the awesome folks at The Pragmatic Studio released an amazing > 50-minute screencast on the product. Check it out, it's free! > > http://pragmaticstudio.com/screencasts/rubymotion > > If you want to stay connected, make sure to follow @RubyMotion on Twitter. > > http://twitter.com/RubyMotion > > Enjoy! > > Laurent > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
On Thu, 03 May 2012 13:15:52 -0500 Ian Ragsdale wrote: > That said, I'm wondering if/when any of this will become open > source? It's been a long time since I trusted proprietary code > more than open source stuff. Open source projects can aways be > forked or maintained by someone else, but if a proprietary company > drops support for whatever reason, your codebase depending on them > is in trouble. > > I'm not trying to suggest in any way that you guys would do that, > but it does make me a little nervous suggesting using this to any > of my clients. I have to agree. I have no fundamental problem with paying for stuff, but I do have trouble with a code base that can't later be picked up and actively developed by someone else if the initial developers vanish. Apologies for injecting any negativity here. Perry -- Perry E. [email protected] ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
The catch in situations like this is that it may have never been written in the first place if Laurent wasn't able to take the time and dedicate the energy full time to build it. Personally, I'd rather fund continued development of it with a license than never to have had it in the first place. --Jeremy On Thu, May 3, 2012 at 3:04 PM, Perry E. Metzger wrote: > On Thu, 03 May 2012 13:15:52 -0500 Ian Ragsdale > wrote: > > That said, I'm wondering if/when any of this will become open > > source? It's been a long time since I trusted proprietary code > > more than open source stuff. Open source projects can aways be > > forked or maintained by someone else, but if a proprietary company > > drops support for whatever reason, your codebase depending on them > > is in trouble. > > > > I'm not trying to suggest in any way that you guys would do that, > > but it does make me a little nervous suggesting using this to any > > of my clients. > > I have to agree. I have no fundamental problem with paying for stuff, > but I do have trouble with a code base that can't later be picked up > and actively developed by someone else if the initial developers > vanish. Apologies for injecting any negativity here. > > Perry > -- > Perry E. [email protected] > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > -- http://jeremymcanally.com/ Positivity every morning: http://goodmorninginterwebs.com Bowties, ties, and more: http://wickhamhousebrand.com ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
On Thu, 03 May 2012 15:04:46 -0400 "Perry E. Metzger" wrote: > > I'm not trying to suggest in any way that you guys would do that, > > but it does make me a little nervous suggesting using this to any > > of my clients. > > I have to agree. I have no fundamental problem with paying for > stuff, but I do have trouble with a code base that can't later be > picked up and actively developed by someone else if the initial > developers vanish. Apologies for injecting any negativity here. One possibility that comes to mind, btw: if you GPLed the code but made a different license available for proprietary apps, people would at least know that if support ends abruptly, the code base will at least remain available. (This might not be the best idea, but it was one that came to mind quickly.) Perry -- Perry E. [email protected] ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
> Can I use Ruby gems? > Because RubyMotion implements a dialect of Ruby that is statically compiled, > regular Ruby gems will not work in RubyMotion. We provide documentation which > describes how to architect gems to work with RubyMotion. Would love to see those documents online! On 2012年5月4日, at 上午1:02, Laurent Sansonetti wrote: > Hi guys, > > I am extremely excited to announce the immediate availability of > RubyMotion, a revolutionary toolchain for iOS development in Ruby. > > (RubyMotion is what I have been working on these last 6 months. :)) > > RubyMotion is a commercial flavor of MacRuby for iOS that includes an > optimized runtime, a brand-new static compiler and memory model, and a > command-line interface. > > If you are familiar with MacRuby you should be all set to develop iOS > apps right away. > > You can find more information about RubyMotion on its website. > > http://www.rubymotion.com > > For a limited time only, RubyMotion can be purchased at a 25% discounted rate. > > The developer center features guides, articles and a pointer to the > sample code repository. > > http://www.rubymotion.com/developer-center > > Also, the awesome folks at The Pragmatic Studio released an amazing > 50-minute screencast on the product. Check it out, it's free! > > http://pragmaticstudio.com/screencasts/rubymotion > > If you want to stay connected, make sure to follow @RubyMotion on Twitter. > > http://twitter.com/RubyMotion > > Enjoy! > > Laurent > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
What impact does this have on the plans for MacRuby for iOS? Henry ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
Personally I'm happy to pay for it, and in fact already have. I'd just like to see some of these improvements make their way back to the open source community, and be reassured that if HipByte for some reason doesn't work out, any projects I have built in MacRuby are supported going forward. - Ian On May 3, 2012, at 2:12 PM, Jeremy McAnally wrote: > The catch in situations like this is that it may have never been written in > the first place if Laurent wasn't able to take the time and dedicate the > energy full time to build it. Personally, I'd rather fund continued > development of it with a license than never to have had it in the first place. > > --Jeremy > > On Thu, May 3, 2012 at 3:04 PM, Perry E. Metzger wrote: > On Thu, 03 May 2012 13:15:52 -0500 Ian Ragsdale > wrote: > > That said, I'm wondering if/when any of this will become open > > source? It's been a long time since I trusted proprietary code > > more than open source stuff. Open source projects can aways be > > forked or maintained by someone else, but if a proprietary company > > drops support for whatever reason, your codebase depending on them > > is in trouble. > > > > I'm not trying to suggest in any way that you guys would do that, > > but it does make me a little nervous suggesting using this to any > > of my clients. > > I have to agree. I have no fundamental problem with paying for stuff, > but I do have trouble with a code base that can't later be picked up > and actively developed by someone else if the initial developers > vanish. Apologies for injecting any negativity here. > > Perry > -- > Perry E. [email protected] > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > > > -- > http://jeremymcanally.com/ > > Positivity every morning: http://goodmorninginterwebs.com > Bowties, ties, and more: http://wickhamhousebrand.com > > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
I agree with most of you, I think that Laurent deserves the financial backing for his work but I also have to admit that I'm worried about the future of MacRuby and what would happen to my RubyMotion projects if Laurent decides to move on. I don't have an issue with the commercial aspect of RubyMotion, I think that's fair and will ensure support, continuous development and proper attention. However the proprietary aspect of RubyMotion is a bit more problematic for someone who strongly believes in open source. That said, none of the other alternatives are currently open source either. (I guess MobiRuby will be the first) Currently RubyMotion is a great solution to hack/prototype small apps for iOS but I'll seat back and see what the community does with it and where Laurent will take the project. If RubyMotion's source code was open, I would certainly be less worried but I also understand Laurent's reasons. I'm looking forward to seeing the upcoming UI libraries and the first cocos2d based game written in RubyMotion and all the nice UI libraries to avoid writing all the Cocoa cruft. As a matter of fact, I believe that RubyMotion will open the door for creative people to come up with something equivalent of http://processing.org/ on iOS. That said, I'm looking forward to seeing Laurent contribute his new memory management system back to MacRuby and finally make it GC free since he proved it's totally doable! My 2 cents worth - Matt On Thu, May 3, 2012 at 10:49 PM, Ian Ragsdale wrote: > Personally I'm happy to pay for it, and in fact already have. I'd just > like to see some of these improvements make their way back to the open > source community, and be reassured that if HipByte for some reason doesn't > work out, any projects I have built in MacRuby are supported going forward. > > - Ian > > On May 3, 2012, at 2:12 PM, Jeremy McAnally wrote: > > The catch in situations like this is that it may have never been written > in the first place if Laurent wasn't able to take the time and dedicate the > energy full time to build it. Personally, I'd rather fund continued > development of it with a license than never to have had it in the first > place. > > --Jeremy > > On Thu, May 3, 2012 at 3:04 PM, Perry E. Metzger wrote: > >> On Thu, 03 May 2012 13:15:52 -0500 Ian Ragsdale >> wrote: >> > That said, I'm wondering if/when any of this will become open >> > source? It's been a long time since I trusted proprietary code >> > more than open source stuff. Open source projects can aways be >> > forked or maintained by someone else, but if a proprietary company >> > drops support for whatever reason, your codebase depending on them >> > is in trouble. >> > >> > I'm not trying to suggest in any way that you guys would do that, >> > but it does make me a little nervous suggesting using this to any >> > of my clients. >> >> I have to agree. I have no fundamental problem with paying for stuff, >> but I do have trouble with a code base that can't later be picked up >> and actively developed by someone else if the initial developers >> vanish. Apologies for injecting any negativity here. >> >> Perry >> -- >> Perry E. [email protected] >> ___ >> MacRuby-devel mailing list >> [email protected] >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >> > > > > -- > http://jeremymcanally.com/ > > Positivity every morning: http://goodmorninginterwebs.com > Bowties, ties, and more: http://wickhamhousebrand.com > > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
I like the idea that somebody is invested in Ruby for IOS to make money. Open Source is great for projects that become very popular. Projects related to Apple like MacRuby are inherently risky since Apple will be indifferent at best to weather it does something to break MacRuby, especially as they see it being a competitor for their preferred mindset. If a company can make money ensuring that MacRuby for Mac and IOS continue to survive Apple's passive aggressive ways, then it gives me greater incentive to invest my time using MacRuby. On the other hand we have to serious consider Apple's commitment to computing at all. As Apple ignores the computer market, the point will come where none of the rest of it maters. If the next computer I buy is not an Apple product, the likely hood grows that the next phone or tablet I buy will not be a MAC OS/iOS product. As someone who makes a living from computing, it is the computer that leads not the other gadgets. ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
I don't really understand the issue being raised here by many people -- namely, "what would happen to my RubyMotion projects if Laurent decides to move on." If I invest time & energy into writing an app using RubyMotion, I'll still own all my code. Further, that code will (apparently) be written in fairly standard MacRuby, which already has one open implementation (on OS X, but with existing plans and ideas to port to iOS), not to mention all the other Rubies out there that might be able to run the code of my app. To me, this seems like being afraid of writing my app in C because the vendor of my particular C compiler might go out of business. That's an understandable worry with a niche, proprietary language, but I don't see the big issue with something as well-supported as Ruby. Of course, I would feel more hesitant if the RubyMotion environment automatically deleted itself if I didn't pay for another year of licensing, thereby making it impossible to build my project at all. But I haven't heard anything about that, so I don't count that as a high risk. Best, --John On 3 May 2012, at 2:12 PM, Matt Aimonetti wrote: > I agree with most of you, I think that Laurent deserves the financial > backing for his work but I also have to admit that I'm worried about the > future of MacRuby and what would happen to my RubyMotion projects if > Laurent decides to move on. > > I don't have an issue with the commercial aspect of RubyMotion, I think > that's fair and will ensure support, continuous development and proper > attention. > However the proprietary aspect of RubyMotion is a bit more problematic for > someone who strongly believes in open source. That said, none of the other > alternatives are currently open source either. (I guess MobiRuby will be > the first) > > Currently RubyMotion is a great solution to hack/prototype small apps for > iOS but I'll seat back and see what the community does with it and where > Laurent will take the project. > If RubyMotion's source code was open, I would certainly be less worried but > I also understand Laurent's reasons. > I'm looking forward to seeing the upcoming UI libraries and the first > cocos2d based game written in RubyMotion and all the nice UI libraries to > avoid writing all the Cocoa cruft. As a matter of fact, I believe that > RubyMotion will open the door for creative people to come up with something > equivalent of http://processing.org/ on iOS. > > That said, I'm looking forward to seeing Laurent contribute his new memory > management system back to MacRuby and finally make it GC free since he > proved it's totally doable! > > My 2 cents worth > > - Matt > > > On Thu, May 3, 2012 at 10:49 PM, Ian Ragsdale wrote: > >> Personally I'm happy to pay for it, and in fact already have. I'd just >> like to see some of these improvements make their way back to the open >> source community, and be reassured that if HipByte for some reason doesn't >> work out, any projects I have built in MacRuby are supported going forward. >> >> - Ian >> >> On May 3, 2012, at 2:12 PM, Jeremy McAnally wrote: >> >> The catch in situations like this is that it may have never been written >> in the first place if Laurent wasn't able to take the time and dedicate the >> energy full time to build it. Personally, I'd rather fund continued >> development of it with a license than never to have had it in the first >> place. >> >> --Jeremy >> >> On Thu, May 3, 2012 at 3:04 PM, Perry E. Metzger wrote: >> >>> On Thu, 03 May 2012 13:15:52 -0500 Ian Ragsdale >>> wrote: That said, I'm wondering if/when any of this will become open source? It's been a long time since I trusted proprietary code more than open source stuff. Open source projects can aways be forked or maintained by someone else, but if a proprietary company drops support for whatever reason, your codebase depending on them is in trouble. I'm not trying to suggest in any way that you guys would do that, but it does make me a little nervous suggesting using this to any of my clients. >>> >>> I have to agree. I have no fundamental problem with paying for stuff, >>> but I do have trouble with a code base that can't later be picked up >>> and actively developed by someone else if the initial developers >>> vanish. Apologies for injecting any negativity here. >>> >>> Perry >>> -- >>> Perry E. [email protected] >>> ___ >>> MacRuby-devel mailing list >>> [email protected] >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >>> >> >> >> >> -- >> http://jeremymcanally.com/ >> >> Positivity every morning: http://goodmorninginterwebs.com >> Bowties, ties, and more: http://wickhamhousebrand.com >> >> >> ___ >> MacRuby-devel mailing list >> [email protected] >> http://lists.macosforge.org/mailman/l
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
What happens to your skills, though, now that they have been finely honed for a particular *flavor* of MacRuby (iOS development). BUT, my thinking is this: the more people use it, the more successful it will be. The more successful it is, the less likely that Laurent will drop support for it! :-) -- Colin Thomas-Arnold ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
That is a completely different situation - there are many compatible C compilers out there currently, and only one compiler that lets you run a RubyMotion project on iOS. Having a bunch of iOS code in "fairly standard MacRuby" is fairly useless if the only existing implementation that runs on iOS were to no longer work for some reason (say due to a new version of iOS). If it were open source that's not something that worries me, but I've had that problem with proprietary products in the past. Let me reiterate that I think Laurent deserves to get paid well for creating this, and I've already purchased a copy for personal use. I'm not trying to rain on anyone's parade, nor suggesting nobody should use it under the current terms, I'm just asking if there are any future plans. - Ian On May 3, 2012, at 5:24 PM, John Labovitz wrote: > I don't really understand the issue being raised here by many people -- > namely, "what would happen to my RubyMotion projects if Laurent decides to > move on." If I invest time & energy into writing an app using RubyMotion, > I'll still own all my code. Further, that code will (apparently) be written > in fairly standard MacRuby, which already has one open implementation (on OS > X, but with existing plans and ideas to port to iOS), not to mention all the > other Rubies out there that might be able to run the code of my app. > > To me, this seems like being afraid of writing my app in C because the vendor > of my particular C compiler might go out of business. That's an > understandable worry with a niche, proprietary language, but I don't see the > big issue with something as well-supported as Ruby. > > Of course, I would feel more hesitant if the RubyMotion environment > automatically deleted itself if I didn't pay for another year of licensing, > thereby making it impossible to build my project at all. But I haven't heard > anything about that, so I don't count that as a high risk. > > Best, > --John > > > On 3 May 2012, at 2:12 PM, Matt Aimonetti wrote: > >> I agree with most of you, I think that Laurent deserves the financial >> backing for his work but I also have to admit that I'm worried about the >> future of MacRuby and what would happen to my RubyMotion projects if >> Laurent decides to move on. >> >> I don't have an issue with the commercial aspect of RubyMotion, I think >> that's fair and will ensure support, continuous development and proper >> attention. >> However the proprietary aspect of RubyMotion is a bit more problematic for >> someone who strongly believes in open source. That said, none of the other >> alternatives are currently open source either. (I guess MobiRuby will be >> the first) >> >> Currently RubyMotion is a great solution to hack/prototype small apps for >> iOS but I'll seat back and see what the community does with it and where >> Laurent will take the project. >> If RubyMotion's source code was open, I would certainly be less worried but >> I also understand Laurent's reasons. >> I'm looking forward to seeing the upcoming UI libraries and the first >> cocos2d based game written in RubyMotion and all the nice UI libraries to >> avoid writing all the Cocoa cruft. As a matter of fact, I believe that >> RubyMotion will open the door for creative people to come up with something >> equivalent of http://processing.org/ on iOS. >> >> That said, I'm looking forward to seeing Laurent contribute his new memory >> management system back to MacRuby and finally make it GC free since he >> proved it's totally doable! >> >> My 2 cents worth >> >> - Matt >> >> >> On Thu, May 3, 2012 at 10:49 PM, Ian Ragsdale wrote: >> >>> Personally I'm happy to pay for it, and in fact already have. I'd just >>> like to see some of these improvements make their way back to the open >>> source community, and be reassured that if HipByte for some reason doesn't >>> work out, any projects I have built in MacRuby are supported going forward. >>> >>> - Ian >>> >>> On May 3, 2012, at 2:12 PM, Jeremy McAnally wrote: >>> >>> The catch in situations like this is that it may have never been written >>> in the first place if Laurent wasn't able to take the time and dedicate the >>> energy full time to build it. Personally, I'd rather fund continued >>> development of it with a license than never to have had it in the first >>> place. >>> >>> --Jeremy >>> >>> On Thu, May 3, 2012 at 3:04 PM, Perry E. Metzger wrote: >>> On Thu, 03 May 2012 13:15:52 -0500 Ian Ragsdale wrote: > That said, I'm wondering if/when any of this will become open > source? It's been a long time since I trusted proprietary code > more than open source stuff. Open source projects can aways be > forked or maintained by someone else, but if a proprietary company > drops support for whatever reason, your codebase depending on them > is in trouble. > > I'm not trying to suggest in any way that you guys would do that, > but i
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
Personally I think it's the next best thing that could happen aside from Apple releasing it as a 'serious' platform with their full weight behind it. MacRuby was great, but Apple didn't really care about it, Laurent did - as much as he could while not getting paid for it - but Apple didn't, least not from what I saw. Now Laurent has a big reason to care not only about RubyMotion but MacRuby as well, and I think so long as the price is always fair, and the support is good, it will be a success. For people wanting an open source solution, don't forget about MobiRuby which will be based on mRuby. If Laurent did want to play around with free/paid version, I would suggest a free version without any support, and a paid version that gives access to support forums/tickets etc with an annual renewal of about $20 - $100 (most forum platforms charge around 20 to $40). Exciting times for Ruby developers! I'm just sad I haven't got the time to have a play with RubyMotion yet, but hope to use it for my 3rd Ruby/Rails project. Aston On 3 May 2012, at 23:29, Colin Thomas-Arnold wrote: > What happens to your skills, though, now that they have been finely honed > for a particular *flavor* of MacRuby (iOS development). > > BUT, my thinking is this: the more people use it, the more successful it will > be. The more successful it is, the less likely that Laurent will drop support > for it! :-) > > -- > Colin Thomas-Arnold > > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
On Thu, 03 May 2012 16:29:52 -0600 Colin Thomas-Arnold wrote: > What happens to your skills, though, now that they have been finely > honed for a particular *flavor* of MacRuby (iOS development). > > BUT, my thinking is this: the more people use it, the more > successful it will be. The more successful it is, the less likely > that Laurent will drop support for it! :-) Laurent could be hit by a bus. I'm not keen on having my ability to do work going forward depend on code in the hands of one individual without recourse. (Sorry, Laurent, and again, I don't mean to be a drag. You've done something very cool and should be proud of it, and I want you to make money so you can keep doing it.) Perry -- Perry E. [email protected] ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] RubyMotion: Ruby for iOS
This argument can truly be made about any commercial tool you use to build with or build upon. Any company of any size can discontinue a product or service at any time. You have to realize that. The RubyMotion you use today you can continue to use whether you pay for ongoing support or not. From the FAQ you will get updates to the toolchain for the next year. This is no different than Corona or MonoTouch or any of the other commercial frameworks you use to build apps with. The question becomes, does the toolchain provide you something that creates an advantage over the tools you have today. If the answer is yes, then the question becomes what is the risk vs. that advantage. I feel the advantage of using Ruby for iOS development is substantial and far outweighs the risk. Its not about learning Objective C vs. Ruby. To me the advantage hinges on using the syntactic flexibility of Ruby to create performant and maintainable applications in significantly less lines of code. RubyMotion is made by HipByte (Laurent's company). Laurent is bootstrapping it. I am confident it will grow as a company both in terms of people and products. I think HipByte is off to a fantastic start! -rich On May 3, 2012, at 10:32 PM, Perry E. Metzger wrote: > On Thu, 03 May 2012 16:29:52 -0600 Colin Thomas-Arnold > wrote: >> What happens to your skills, though, now that they have been finely >> honed for a particular *flavor* of MacRuby (iOS development). >> >> BUT, my thinking is this: the more people use it, the more >> successful it will be. The more successful it is, the less likely >> that Laurent will drop support for it! :-) > > Laurent could be hit by a bus. I'm not keen on having > my ability to do work going forward depend on code in the hands of one > individual without recourse. (Sorry, Laurent, and again, I don't mean > to be a drag. You've done something very cool and should be proud of > it, and I want you to make money so you can keep doing it.) > > Perry > -- > Perry E. Metzger [email protected] > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
