From: Alessandro Rubini <rubini-list@gnudd.com>
To: barebox@lists.infradead.org
Subject: Re: NFSv4 boot support?
Date: Tue, 20 Feb 2024 14:53:47 +0100 [thread overview]
Message-ID: <ZdSu671i2n4RQPoz@arcana.i.gnudd.com> (raw)
In-Reply-To: <20240220004316.fdc79907089c7358a1e67f62@gmail.com>
>> This hasn't
>> seen development activity in 5 years.
>
> Please see https://github.com/virtualsquare/picotcp
But the TCP/IPV4 standard didn't change, either.
>> lwIP on the other hand still sees active development.
>
> I agree with you. It looks like lwIP is more popular than picotcp.
Sure. It's older and it has a loyal (or addicted) user base and
commercial support. Or it just needs more commits because it'w worse and
full of bugs.
As far as I know, lwIP is horrible code, difficult to integrate and
maintain, while picotcp is designed in the right way (although I admit
I only looked at the former, about picotcp I only talked with the main
author without looking at the code).
I'd love to add mqtt to my microcontroller projects, where I have udp
but no tcp yet, and I would never rely on lwIP. That's just a personal
opinion, but I'd better not rely on the date of last commit to pick
or not pick a library.
Regards
/alessandro
next prev parent reply other threads:[~2024-02-20 13:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 21:03 Dan Shelton
2024-01-31 21:37 ` Ahmad Fatoum
2024-02-05 9:59 ` Antony Pavlov
2024-02-17 8:51 ` Ahmad Fatoum
2024-02-19 2:17 ` Dan Shelton
2024-02-20 14:17 ` Ahmad Fatoum
2024-02-20 15:28 ` Uwe Kleine-König
2024-02-19 21:43 ` Antony Pavlov
2024-02-20 13:53 ` Alessandro Rubini [this message]
2024-02-26 12:17 ` Ahmad Fatoum
2024-03-08 10:23 ` Sascha Hauer
2024-03-09 10:01 ` Alessandro Rubini
2024-02-28 7:26 ` Antony Pavlov
2024-02-28 9:20 ` Sascha Hauer
2024-02-28 11:50 ` Antony Pavlov
2024-02-28 12:27 ` Sascha Hauer
2024-02-05 18:41 ` Antony Pavlov
2024-02-06 4:40 ` Dan Shelton
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=ZdSu671i2n4RQPoz@arcana.i.gnudd.com \
--to=rubini-list@gnudd.com \
--cc=barebox@lists.infradead.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