public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Austin <brian.austin@cirrus.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS]  Re: Is eCos project still alive?
Date: Fri, 14 Dec 2007 16:34:00 -0000	[thread overview]
Message-ID: <1197639922.23339.0.camel@localhost.localdomain> (raw)
In-Reply-To: <476190B4.2050606@mindspring.com>

I can see that, but as for what we use ( RedBoot ).  customers love it.

From my experiences, if it does what it's supposed to do, who cares how
old it is.  How many folks use X11?



On Thu, 2007-12-13 at 15:06 -0500, Frank Pagliughi wrote:
> As a embedded-systems consultant, I've been using eCos for several 
> years, and I love it.  I've used it for my own development - test apps 
> and demos - but I have never been able to sell a single customer on 
> using the OS for a project.  When a potential customer (usually a 
> manager type) has a look, those things do stand out: it *looks* old and 
> out of date, on first pass. Most don't seem to get past poking around 
> the web page.
> 
> For more technically sophisticated customers, when 2.0 first appeared, 
> it literally took ten minutes to download the code, and get a sample app 
> running on an old PC. Now when I tell a customer to take it for a test 
> drive, the setup gets involved, with pieces from several places.
> 
> I try to tell them to look closer, but by that time, they've already 
> chosen something else. From my experience, the current state of the 
> project doesn't seem to help sell it.
> 
> Frank
> 



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2007-12-14 13:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13  9:46 Loginov Alexander
2007-12-13  9:50 ` Loginov Alexander
2007-12-13 15:15 ` Grant Edwards
2007-12-13 15:43   ` Chris Zimman
2007-12-13 17:40     ` Grant Edwards
2007-12-14  0:48       ` Bob Koninckx
2007-12-14  1:41         ` Grant Edwards
2007-12-14  6:38           ` Frank Pagliughi
2007-12-14 11:15             ` Chris Zimman
2007-12-14 11:20               ` Andrew Lunn
2007-12-14 12:00                 ` Paul D. DeRocco
2007-12-14 14:28                 ` [ECOS] FSF copyright assignmnett. [Was Re: [ECOS] Re: Is eCos project still alive?] Ilija Koco
2007-12-14 16:21                   ` [ECOS] FSF copyright assignment. " Daniel Morris
2007-12-14 17:11                 ` [ECOS] Re: Is eCos project still alive? Grant Edwards
2007-12-14 18:10                   ` Brian Austin
2007-12-17 11:29                 ` Jonathan Larmour
2007-12-14 16:34             ` Brian Austin [this message]
2007-12-14 16:39               ` Sergei Organov
2007-12-14 18:47               ` Grant Edwards
2007-12-13 20:06 ` Mike Arthur
2007-12-14 13:47 ` Ilija Koco
  -- strict thread matches above, loose matches on Subject: below --
2007-12-14  9:07 Loginov Alexander
2007-12-14  8:28 Loginov Alexander
2007-12-14 11:09 ` Chris Zimman
2007-12-13  4:27 [ECOS] " Loginov Alexander
2007-12-13  6:15 ` [ECOS] " Grant Edwards
2007-12-13  3:31 Loginov Alexander
2007-12-13  8:07 ` Grant Edwards
2007-12-13 15:08   ` Brian Austin
2007-12-13  3:02 Anthony Tonizzo

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=1197639922.23339.0.camel@localhost.localdomain \
    --to=brian.austin@cirrus.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).