public inbox for
 help / color / mirror / Atom feed
From: Stanislav Meduna <>
To: "" <>
Subject: Re: [ECOS] Re: is eCos dying?
Date: Sun, 04 Oct 2015 08:30:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 03.10.2015 10:15, John Dallaway wrote:

Hi Abhishek,

>> Would it be worth to start learning on eCos or is it dying ?I have seen
>> enough activity in 2007 but now it is minimal this year.
>> Is it getting outdated?

> eCos is not dying, but I would have to agree that there has been less
> activity on the mailing lists recently.

Well the last commit in is 5 months
old one-liner, followed by a 12 and 15 month old ones, so this is not only
on mailing lists. I'd say that while it is still a good OS with clean
and easy to use architecture, the open source version basically died
and there are parts hopelessly outdated (TCP/IP from ~2000 if
I remember correctly etc).

I cannot comment on eCosPro, but then you are in a price segment
where there are more alternatives to explore.

>> should i begin to work using eCos or should i look for other alternative?

It depends on what your short and long-term plans are. Definitely
also take a look at FreeRTOS.


Before posting, please read the FAQ:
and search the list archive:

  reply	other threads:[~2015-10-04  8:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2015-10-03  8:15 ` John Dallaway
2015-10-04  8:30   ` Stanislav Meduna [this message]
2015-10-04 15:00     ` Grant Edwards
2015-10-06  7:51 Richard Rauch
2015-10-06 12:59 ` Mikhail Matusov
2015-10-12 23:57 ` Jonathan Larmour
2015-10-13 12:31   ` David Fernandez
2015-10-14  0:57     ` Frank Pagliughi
2015-10-13 17:20   ` Grant Edwards
2015-10-13 19:38 ` Alex Schuilenburg
2015-10-14 23:05 ` Sergei Gavrikov

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).