From: Grant Edwards <grante@visi.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: ECOS - MIPS
Date: Thu, 23 Jun 2005 15:28:00 -0000 [thread overview]
Message-ID: <20050623152839.21EAE49B78@rivatek.dnsalias.net> (raw)
In-Reply-To: <200506231325.41733.sinany@beko.com.tr>
In gmane.os.ecos.general, you wrote:
> patterns means reusability of the design and architecture. if
> u want your opearting system to fullfill future requests, i
> must strongly suggest to use them.the things that eCos uses is
> traditional C programming way of doing reusability and
> maintainability.
Right.
> modern operating systems must modern software ideas and
> architecture.
You're free to write your own. eCos suits my needs quite
nicely.
> Pattern oriented architecture is not a new idea
> but none of the embedded operating systems uses them.
Firstly, there might be a reason for that. We're not stupid,
you know.
Secondly, I have no idea what you mean by "pattern oriented
architecture" can you point to a description? The things that
Google found were either describing ways to fail:
Pattern oriented architecture - A trend that's found in
systems created by architects who've recently read and
digested books on architectural patterns and come to the
conclusion that implementing patterns (such as
front-controller, etc) is the key to a successful
architecture. Rather than determining if common patterns are
appropriate, and picking the most suitable one, all patterns
that can be applied are done so, on top of one another,
creating an entangled, schizophrenic system.
or were marketing buzword-bullshit:
A standards-based, pattern-oriented architecture that follows
industry best-practices assures that the NEFS will fit right
into your development environment.
> Java classes are dynamically loaded. Java will be a future for
> embedded systems. Many companies started to use java. it has
> many benefits. If performance problems are solved, Java will
> be a revolution for embedded systems.
People have been saying that for 10 years. I stopped paying
much attention 5 years ago. Java requires MASSIVE amounts of
storage compared to eCos.
> i am going to write an operating system with patterns and
> reusable architecture. i will share it with you in the future
> when i finish.
OK.
--
Grant Edwards grante Yow! I own seven-eighths
at of all the artists in
visi.com downtown Burbank!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-06-23 15:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <W646741726646371119364845@webmail3>
2005-06-22 7:09 ` [ECOS] " K. Sinan YILDIRIM
2005-06-22 10:21 ` Fabian Scheler
2005-06-22 18:28 ` L D
2005-06-23 6:29 ` K. Sinan YILDIRIM
2005-06-23 7:03 ` Andrew Lunn
[not found] ` <200506231102.17394.sinany@beko.com.tr>
2005-06-23 8:07 ` K. Sinan YILDIRIM
2005-06-23 8:34 ` Jerome Souquieres
2005-06-23 9:02 ` Andrew Lunn
2005-06-23 10:27 ` K. Sinan YILDIRIM
2005-06-23 15:28 ` Grant Edwards [this message]
2005-06-24 6:14 ` [ECOS] " K. Sinan YILDIRIM
2005-06-24 9:07 ` Nick Garnett
2005-06-24 14:08 ` Grant Edwards
2005-06-24 14:52 ` K. Sinan YILDIRIM
2005-06-24 16:39 ` Grant Edwards
2005-06-23 16:19 ` [ECOS] " Richard Forrest
2005-06-24 0:04 ` [ECOS] " Grant Edwards
2005-06-24 7:48 ` Richard Forrest
2005-06-23 15:17 ` Grant Edwards
2005-06-24 15:04 Ali, Khurram
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=20050623152839.21EAE49B78@rivatek.dnsalias.net \
--to=grante@visi.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).