From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] dynamic gateway / hna / services
Date: Fri, 27 Jul 2007 18:40:31 +0200 [thread overview]
Message-ID: <200707271840.31922.lindner_marek@yahoo.de> (raw)
In-Reply-To: <71E83A5E-6CAF-43DD-9CA7-38B9F70839E7@lo-res.org>
Am Freitag, 27. Juli 2007 18:03 schrieb Aaron Kaplan:
> I don't feel personally attacked at all :)
But the unknown reader might get that impression ...
> I just again and again get the feeling from batman people that sort
> of "everything else sucks"
> Like academia sucks, olsr sucks etc etc.
> But that is a bit contra-productive. That is what I wanted to point out.
Where does this feeling come from ?
Because of "better approach to mobile ad-hoc networking" (you said: "since it
is already in the name") ?! Do you have in mind what OLSR means ? OPTIMIZED
Link State routing - that means OLSR is the first link state routing protocol
which optimizes ?!
GNU = Gnu is Not Unix => is Unix bad ?
KDE => Kool Desktop Environment => the others are not cool ?
VIM => Vi IMproved => vi seems to be bad ?!
We could continue this list a very long time.
Or is it because we always compare with OLSR ?
Don't forget that OLSR is the de-facto standard for routing protocols. So, we
compare against something the people know. Have you ever listened to a SVN
talk ? They compare to CVS. What is so bad about showing real problems in
existing solutions and offering something better ?
Please remember - OLSR is so good and well known because we helped it quite a
lot. Much of the intial testing was done in Berlin. Afterwards we disabled
MPR and Hysteris, developed ETX and Fisheye. It is not your child only. It
was not easy for us to find out that we have to restart from scratch if we
really want to solve the problems OLSR has.
We learned a lot from it and now we move on.
> nono... redo everything is like asking for a bit to much. Agreed. But
> step by step...
I meant they want us to clone the way OLSR solves certain problems and we
don't want that. It may need some time and effort but we want to attack the
real source of the problems.
Regards,
Marek
next prev parent reply other threads:[~2007-07-27 16:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 13:21 [B.A.T.M.A.N.] dynamic gateway / hna / services Freifunk Dresden
2007-07-24 18:35 ` Daniel Poelzleithner
2007-07-25 11:50 ` Alexander Morlang
2007-07-25 12:52 ` tetzlav
2007-07-25 15:06 ` Alexander Morlang
2007-07-25 15:19 ` Daniel Poelzleithner
2007-07-25 16:05 ` Alexander Morlang
2007-07-25 17:25 ` Daniel Poelzleithner
2007-07-26 12:33 ` Alexander Morlang
2007-07-25 16:21 ` clauz
2007-07-25 15:05 ` Daniel Poelzleithner
2007-07-25 14:56 ` Marek Lindner
2007-07-27 14:07 ` Marek Lindner
2007-07-27 14:43 ` Aaron Kaplan
2007-07-27 15:23 ` Marek Lindner
2007-07-27 16:03 ` Aaron Kaplan
2007-07-27 16:40 ` Marek Lindner [this message]
2007-07-27 20:41 ` Aaron Kaplan
2007-07-28 8:03 ` Axel Neumann
2007-07-27 14:59 ` Lui
2007-07-27 15:31 ` Marek Lindner
2007-08-02 14:26 ` Axel Neumann
-- strict thread matches above, loose matches on Subject: below --
2007-08-03 9:31 Freifunk Dresden
2007-08-04 9:43 ` Axel Neumann
2007-08-04 21:38 ` Freifunk Dresden
2007-08-20 13:10 ` Alexander Morlang
2007-08-04 10:34 ` Marek Lindner
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=200707271840.31922.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/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