From: Gour <gour@atmarama.net>
To: caml-list@inria.fr
Cc: "Damien Guichard" <alphablock@orange.fr>
Subject: Re: [Caml-list] UFO (United Forces of OCaml)
Date: Fri, 27 Sep 2013 20:58:52 +0200 [thread overview]
Message-ID: <20130927205852.5baa20e8@atmarama.noip.me> (raw)
In-Reply-To: <567994902695064341@orange.fr>
[-- Attachment #1: Type: text/plain, Size: 2346 bytes --]
On Fri, 27 Sep 2013 19:08:28 +0200
"Damien Guichard" <alphablock@orange.fr> wrote:
Hiya Damien,
> OCaml is multi-paradigm in nature.
Great.
> There are multiple ways (multiple trade-offs) a thing can be done.
Nice.
> Same about books, documentation, tutorials, IDEs ...
> In contrast with Caml-Light, OCaml has no 'official' book, tutorial
> or IDE. However i expect many to come, some to become almost
> forgotten, some to be cited as a reference point (Ocaml evolves
> continually). Actually there is an 'official' OCaml 2.2 book, but
> somewhat obsolete now.
I plan to use RWO book.
> Just my humble opinion of course.
Of course.
> I understand that, as a beginner, you may consider diversity as a
> danger. It seems your software is more fragile because some basic
> block could be discontinued.
Right.
> I would answer : the software fragility lies in the programmer,
> not in the language ecosystem being too weak.
Heh, "batteries included" still helps.
> Actually GTK 2.24 looks very great when a good theme is applied.
On Mac?
> You can have this metal brush look. Or this white water-button look.
> Or whatever look you can imagine (or design).
I'm more worried about the state of GTK's support on Win/Mac than about
LablGTK...
> Plus LablGtk is an excellent binding that makes GTK programming far
> much easier.
...which I actually consider very good bindings.
> Otherwise i would warmly welcome a Qt binding.
Me too...similar with wxOCaml if having them actively maintained.
> However, i dont wait for it, i go ahead.
Sure, I'll start learning OCaml and working on non-GUI things.
> Even if i switch to Qt some day i don't loose my time,
> because knowing GTK, whatever language, is an asset anyway.
That's true, but I'd prefer saving some of my free time meant to be
spent for working on this open-source project, if possible.
> I hope i am not too much rude with you,
> I apologize if i am,
Not at all. Thank you.
Sincerely,
Gour
--
A person is considered still further advanced when he regards honest
well-wishers, affectionate benefactors, the neutral, mediators, the
envious, friends and enemies, the pious and the sinners all with an
equal mind.
http://www.atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-09-27 18:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 17:08 Damien Guichard
2013-09-27 18:58 ` Gour [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-27 7:11 Gour
2013-09-27 11:20 ` Török Edwin
2013-09-27 12:04 ` Yaron Minsky
2013-09-27 12:15 ` Paolo Donadeo
2013-09-27 15:55 ` David MENTRE
2013-09-27 16:25 ` Siraaj Khandkar
2013-09-27 16:45 ` Ashish Agarwal
2013-09-27 12:13 ` Gour
2013-09-27 11:25 ` Lukasz Stafiniak
2013-09-30 1:40 ` Francois Berenger
2013-09-30 6:01 ` Gour
2013-09-30 6:33 ` Francois Berenger
2013-09-30 14:14 ` Sylvain Le Gall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130927205852.5baa20e8@atmarama.noip.me \
--to=gour@atmarama.net \
--cc=alphablock@orange.fr \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).