From: Dirk Vogel <lists@...>
Date: 2013-03-02T21:51:08+09:00
Subject: Re: Does this specific sound library exist?

Sorry for this delay, guys, I'm actually on a short journey.

@ Damián: thanks for your first link. Indeed it may help to get 
assistance if
I decide to use Ruby for my project (after this discussion, I can't be
sure anymore). Your second link is about a project that has to do 
nothing
whatsoever with mine; but it was interesting nonetheless.

What I didn't tell you: it's quite sure my project will become freeware,
maybe with an invitation to donate ;-) But I'd like to avoid spending
hundreds of Euros for IDEs, GUI builders or other helping tools on top
of spending lots of time and not being payed if it's not strictly
necessary. So even if it's worth its price, I don't think I'll buy
RubyMine.

@ Carlo: Ok, I think I get it. Thanks again for sharing your experience
with this multi-platform problem. But if I am to abandon the idea of
offering my project to as many users as thinkable, the moment of
decision for one platform at the expense of all others approaches. Your
last paragraphs seem to nudge me into the direction of MacOS / iOS.

Let's say (just as a hypothesis) I'll go for these two. As I see it,
arguments would be (correct me if I miss essential points):

Pro:
• familiarity with the UI environment

Con:
• various expenses (Apple developer cost: 99 $ per year / XCode is free,
but if I'd like to use Ruby, RubyMotion for iOS costs > 200 $)
• covers a little part of the users only
• attention to what you call the media-related part

This last comment of yours is a bit cryptic for me. You say that "the
media-related part should have been given proper attention". Why "should
have been"? Is it already too late? Do you reckon Mac or iOS
applications can't meet success without giving the medias a considerable
attention? Would that be less important with other platforms? (As I'm
completely new to this, I never thought about this aspect of
programming...)

Well, the (surely incomplete) list of cons seems larger to me than the
pros list. Let's try the same procedure with Android:

Pro:
• big part of the "market"
• free of expenses (?)

Con:
• "Crippled Linux" (I have no idea what that means concretely, but it 
just
sounds bad)
• every Android version (of every future hardware) will engender 
necessary
code changes
• no UI familiarity

Hm. Not really convincing either. And, as always, an important question
raises after all that. Would it still be a good idea realizing this
one-platform approach with Ruby? Wouldn't it be more straightforward to
choose Objective-C for MacOS or Java for Android? (Or even C# in the
less probable case of Windows?) Sure, my starting point was the choice
of a modern, relatively simple and interesting programming language, but
that was closely linked to my multi-plaatform hope. That being
shattered, isn't the linguistic disadvantage of Objective-C or Java
counterbalanced by the fact that they're the most direct, maybe failsafe
ways to address their OSes?


Thanks and bye!

-- 
Posted via http://www.ruby-forum.com/.