ralf.mardorf at rocketmail.com
Thu May 28 00:22:39 UTC 2020
My reply is intended as an explanation for the OP, not a reply
addressed to Aryeh Friedman.
On Wed, 27 May 2020 16:48:56 -0400, Aryeh Friedman wrote:
>Will it? Almost all the best IT/programmers I know started with just
>as difficult of a challenge so if the OP wants to do something hard
>from the get go let them.
Many skilled coders never maintained an official port for a BSD or
Linux distro. Lots of them try to avoid soname issues  by not linking
against shared libs of BSD or Linux default installs and they try to
workaround other pitfalls, too. Let alone that some very skilled coders
even don't support BSD or Linux at all.
One of the best, if not the best professional EQ is from fab filters.
"We're not planning support for Linux any time soon. It's a significant
amount of work, and testing is harder than on Windows or Mac because
there are various major Linux distributions, all with subtle
differences. And of course the market is very small."
It's more or less the same for FreeBSD. "Maintaining" even a binary
blob that doesn't link against shared libraries is still time
While unskilled but giftet people might learn better when starting
programming a more challenging software, than when programming
something trivial, maintaining a port that needs to fulfil
the policy of an operating system gains not that much, than first
learning the basics without taking care about port guidelines.
The porters handbook and similar guidelines of other operating systems
don't help a novice to become familiar with computers and/or a
particular operating system. Trying to become familiar with computers
and FreeBSD by maintaining a port is like hanging wallpaper to
alongside learn how to lay bricks, too. You could do that, but
especially to learn use of computers, it's way better to start
a little bit structured. IOW first lay bricks, than hang the wallpaper.
Starting with the wallpaper is a poorly structured strategy.
More information about the freebsd-questions