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.
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 suc
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, leas
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 i
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! :
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
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
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 RubyMo
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.
-
What impact does this have on the plans for MacRuby for iOS?
Henry
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 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日
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, b
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.
-
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
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 c
Awesome job. Congrats on shipping!
On Thu, May 3, 2012 at 1:12 PM, az...@gmx.net 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
> > RubyMot
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
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
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 ne
19 matches
Mail list logo