Hi Kris,<div><br></div><div>No offense taken, it was an argument that works to shut down constructive discussion of how to get Haskell running on mobile, a task which has perplexed me for several long days. I agree most apps are pretty terrible, at least on iOS though, despite the percentages being wildly off there are still a few hundred apps that are very well done and thoughtful, none of them using Haskell I'm sure.</div>
<div><br></div><div>I'm looking to pass Haskell lists of musical data and return processed musical ideas from it (not audio, not realtime). I was also planning on handling a database within Haskell as the information contained would be used by the music processing and from what I have read Haskell interfaces to SQL far more readily than with a C++ orm type solution. I was planning on working with Haskells Euterpea as base to build my ideas off of, my I might end up rolling my own similar library as my aims are a bit different than theirs.</div>
<div><br></div><div>Everything else would be C++, including the interface, audio and dsp processing etc. I already have the C++ stuff running on my phone. I have read about the difficulty of getting Haskell working in real world scenarios, but as far as I understand my plans for it are fairly well suited to it.</div>
<div><br></div><div>Since much of the documentation online about Haskell seems to be out of date, its tough to get a general feel for whats working. I see people mention that cross-compilation was finished a while back which should allow for targeting arm but nothing concrete and the website gives conflicting info. I've also considered using GHC to generate C to paste into the project but it seems there have been and may be more integrated ways to get it running.</div>
<div><br></div><div>casey</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Nov 10, 2012 at 9:31 AM, Kristopher Micinski <span dir="ltr"><<a href="mailto:krismicinski@gmail.com" target="_blank">krismicinski@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Sat, Nov 10, 2012 at 9:21 AM, Casey Basichis <<a href="mailto:caseybasichis@gmail.com">caseybasichis@gmail.com</a>> wrote:<br>
> As for you notion of "hard truth," and "dumb apps acting as web front ends"<br>
> its pretty blase to assume that anyone interested in this thread will share<br>
> that perspective in terms of their own goals on these platforms. I compose<br>
> professionally on my phone, its certainly not a toy for my purposes. I also<br>
> have no interest whatsoever in getting Cocoa commands into Haskell. I just<br>
> want a functional way of working with data.<br>
><br>
<br>
</div>I didn't perceive my comment would be taken as insulting by people,<br>
but I apologize if it was! It is based on quite detailed study of why<br>
people write apps that I've been working on for the past year or so.<br>
The vast majority of apps are thin wrappers around REST services. I<br>
didn't mean to imply that this is what you would be using it for here,<br>
but rather to give an explanation as to why Haskell may have not shown<br>
up.<br>
<br>
I only meant that, at some level, you are going to need to fit into<br>
the platform, you can't deny this: for the case of Android you *have*<br>
to hook into the lifecycle somewhere, because that's how the system<br>
runs your app. You also probably want a GUI (maybe *you* don't, but<br>
I'd wager most people *do*).<br>
<br>
In any case, you can get good programming done without much platform<br>
assistance using things like the NDK, some projects manage to do this:<br>
mostly projects with gobs of C++ code ported from desktop to Android<br>
where they need minimal Java sections because of fast production<br>
cycles.<br>
<div class="im"><br>
> I would greatly prefer to go the Haskell route, but have been considering<br>
> OCaml as well as they seem to have an active and enthused interest in iOS.<br>
> I would love a bit of perspective on whether OCaml would be worth pursing in<br>
> the long run for the short term benefit of having a more mature mobile<br>
> implementation.'<br>
><br>
<br>
</div>What do you want to do with it? From what I can tell about all the<br>
OCaml projects I've seen, they still mostly suffer from the problems<br>
of having a limited interface to the Android system proper.<br>
<br>
(I'm not saying that makes them bad, just harder to use to write real apps..)<br>
<br>
kris<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Casey James Basichis<br>Composer - Cartoon Network<br><a href="http://www.caseyjamesbasichis.com" target="_blank">http://www.caseyjamesbasichis.com</a><br><a href="mailto:caseybasichis@gmail.com" target="_blank">caseybasichis@gmail.com</a><br>
310.387.7540<br>
</div>