From: Dirk Schnitzler <dirk@dirk-schnitzler.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Mono with ptxdist for ARMv7 Cortex A8-AM335x
Date: Mon, 18 Nov 2013 00:25:45 +0100 [thread overview]
Message-ID: <52895079.1000007@dirk-schnitzler.de> (raw)
In-Reply-To: <20131117185828.GX31417@pengutronix.de>
>The mono packages in PTXdist is really old and has not been tested in
a long time,
>as far as I know. If you're serious about using it, then I recommend
you start with
>updating it to the latest version. Michael
I know, this is some kind of OT here, but
I would be interested in your opionion about using mono for application
logic / api
development. I think it can help when you have a small team of
developers with
c#/.NET experience and time to market really counts. Stuff like dbus,
json parsers,
http/soap servers, etc, can be done really fast and 'safe'.
Can someone provide pointers ro resources other than the 'usual
Microsoft patent
/ promise issues' and 'why mono is not good for linux/fos'?
More specific technical pros/cons would be really welcome.
Kind regards,
Dirk.
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2013-11-17 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 13:21 Bruno, Daniel
2013-11-17 18:58 ` Michael Olbrich
2013-11-17 23:25 ` Dirk Schnitzler [this message]
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=52895079.1000007@dirk-schnitzler.de \
--to=dirk@dirk-schnitzler.de \
--cc=ptxdist@pengutronix.de \
/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