Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Kuba Ober <ober.14@osu.edu>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: The OCaml Community (aka back from the	Developer Days)
Date: Wed, 30 Jan 2008 11:26:35 -0500	[thread overview]
Message-ID: <200801301126.36166.ober.14@osu.edu> (raw)
In-Reply-To: <200801301514.12327.jon@ffconsultancy.com>

On Wednesday 30 January 2008, Jon Harrop wrote:
> On Wednesday 30 January 2008 14:17:13 Kuba Ober wrote:
> > It would make sense as a business venture when you'd throw in some
> > economy of scale. MS can sell visual studio for peanuts, and keep that
> > business unit out of the red, of course because they sell so many.
>
> Visual Studio should be making a lot of profit. Microsoft have many
> commercial developers and it is illegal for them to sell products built
> using many of Microsoft's freely available tools. To buy decent tools for
> commercial development, you're looking at 3,000 euros. Either you're very
> rich, or that isn't "peanuts". :-)

I don't think you're prohibited from using Visual Studio Standard in 
commercial development, and that does sell for peanuts.

> If I wanted to pay you to "complete" the String module, how much would you
> charge? Many suitably qualified people would be happy to earn $100 for
> doing that and, I believe, many people/companies would be willing to pay
> that.

I'm sure as a student I'd be very happy. A professional who can choose between 
consulting hours and doing that, the person would probably choose consulting 
hours.

> I'd much rather give people a one-off small contract paid on-line by 
> credit card to solve a niggling problem that I didn't have time to fix
> myself than employ someone with tax, insurance and liability concerns. If
> they're good, I'll use them again.

Yet I doubt that professional developers who want to earn off of their work 
will pick up such projects.

> When I'm selling books like hot cakes and have more outstanding consultancy
> contracts than I can shake a stick at, I'll be more than happy to throw
> money at you to improve things. When I'm going hungry and struggling to
> keep my head above water, I'll be more than happy to solve your problems
> for a small fee. :-)

See? :)

> > I guess it's a big stride to break that small-to-mid-scale barrier.
> > Trolltech had done that, and they are IMHO good technical innvoators too.
> > If there was a way for some OCaml-centric business to do what Trolltech
> > had done, it could probably take off and make very feature-rich OCaml
> > environment available for a good price I wouldn't mind paying $1500/year
> > for an OCaml environment that could run natively (as in no .net and no
> > Cygwin dependencies) on Windows and Linux, and just "do the job". Qt is
> > really nice in that regard: you only need the C++ compiler, and
> > everything else is included and ready to go. It even builds its own build
> > tools (qmake, moc, uic).
>
> OCaml is not as big as TrollTech and has some annoying problems that make
> it unviable as a commercial platform in many ways but I think our company
> has shown that OCaml's commercial market is now sufficient that you can
> earn a living from it.

Which is why any sort of an OCaml startup, a company that could potentially 
provide a non-free toolkit, ide, and whatnot, would need to get some key 
customers very very soon. IIRC, the primordial trolls did get I think 10 
seats sold very soon after they were weaned off their wives (pun intended).

> To be honest, I would love to be able to buy more books on OCaml (e.g. on
> LablGTK2), more software written in OCaml and libraries for OCaml and so
> on. I believe there are now tens of thousands of prospective customers out
> there for such OCaml products.

If there was something on par with Visual Studio Standard for OCaml, even if 
the IDE was an order of magnitude simpler than that, I'd pay $1500/year for a 
single architecture without much second thoughts.

The compiler, though, would likely need to be much amended from the current 
state of affairs, as I can't see it as a viable product without offering a 
built-in C++ ABI support for ia32 at least. I.e. it must be able to interface 
not only to C libraries without writing any C code, but it must be able to 
interface directly with C++ libraries. It can, of course, use the C++ 
compiler to generate some of the needed code, but it has to be transparent. 

It also implies throwing in a C++ parser eventually, but there's no other 
way -- there's just too many good C++ libraries around to ignore them. And my 
key requirement is use of Qt -- if I can't use it, I won't buy such a 
platform, and I won't use any bindings either. To me, the whole binding thing 
is upside down: foreign-language stuff shouldn't be bent to mend with 
higher-level language, it should be the other way around: high level 
languages such as OCaml need to acquire necessary ABI support.

A good first step (good enough for me) would be for OCaml to support C++ ABI 
while not understanding any C++, i.e. only using for-the-purpose OCaml 
constructs. That way one could do the "bindings" by hand-translating some C++ 
headers to OCaml.

This could be implemented maybe in symbiosis with the trolls somehow -- after 
all they could benefit from opening up their market to functional programming 
folks.

Cheers, Kuba


  reply	other threads:[~2008-01-30 16:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27 13:09 David Teller
2008-01-28  0:38 ` [Caml-list] " Oliver Bandel
2008-01-28 11:27   ` David Teller
2008-01-28 13:42     ` Sylvain Le Gall
2008-01-28 16:38       ` [Caml-list] " Andrej Bauer
2008-01-29  0:26         ` Markus Mottl
2008-01-29 13:45           ` Gerd Stolpmann
2008-01-29 20:07             ` Markus Mottl
2008-01-30 13:04             ` Kuba Ober
2008-01-30 13:26               ` Jon Harrop
2008-01-30 14:17                 ` Kuba Ober
2008-01-30 15:14                   ` Jon Harrop
2008-01-30 16:26                     ` Kuba Ober [this message]
2008-01-30 17:41                   ` [Caml-list] Re: The OCaml Community (aka back fromthe " David Allsopp
2008-01-30 21:32                     ` Kuba Ober
2008-01-30 13:10             ` [Caml-list] Re: The OCaml Community (aka back from the " Vincent Hanquez
2008-01-30  9:22           ` Sylvain Le Gall
2008-01-28 17:25     ` [Caml-list] " Peng Zang
2008-01-28 13:35   ` Sylvain Le Gall
2008-01-28 15:25     ` [Caml-list] " Jon Harrop
2008-01-28 15:43       ` Sylvain Le Gall
2008-01-28 19:49         ` [Caml-list] " Jon Harrop
2008-01-28 20:16           ` Hezekiah M. Carty
2008-01-28 20:35             ` Jon Harrop
2008-01-28 20:48               ` Hezekiah M. Carty
     [not found]             ` <6f9f8f4a0801281235s136f53b4qae8ec2c928f931c@mail.gmail.com>
2008-01-28 20:46               ` Hezekiah M. Carty
2008-01-28 21:29             ` Alterlib? (was "Re: The OCaml Community") Dario Teixeira
2008-01-28 21:48               ` [Caml-list] " blue storm
2008-01-28 13:52 ` [Caml-list] The OCaml Community (aka back from the Developer Days) Romain Beauxis
2008-01-28 14:42   ` Sylvain Le Gall
2008-01-28 15:39     ` [Caml-list] " Romain Beauxis
2008-01-28 15:49       ` Sylvain Le Gall
2008-01-28 15:56         ` [Caml-list] " Romain Beauxis
2008-01-29 15:23     ` Stefano Zacchiroli

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=200801301126.36166.ober.14@osu.edu \
    --to=ober.14@osu.edu \
    --cc=caml-list@yquem.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