On Wed, Apr 9, 2025 at 3:45 AM chao an <magicd...@gmail.com> wrote:
> > > > On Tue, Apr 8, 2025 at 7:17 PM Lwazi Dube <lwa...@gmail.com> wrote:
> > > > An open source project's ability to innovate should not be
> > > > held up by your preferences.
> > >
> > > The last sentence is completely wrong. Its not about "preference" but
> > > impacting self-compatibility and long term maintenance. Messing the
> > > foundations and defaults is not innovation. Try building a home when
> > > the project constantly changes during the process, when you have 10
> > > floors ready and suddenly you need to change pavements. Innovation is
> > > when you create new functionality and give users a choice without
> > > breaking existing working stuff.
>
>  So you think it's more important to maintain your current 10 floors
> building, and it's none of your business if a 100 floors skyscraper appears
> in the future? so could you afford all the developer time spent on this
> kind of problem?

Anchao, what I meant was to finish 10 floor building as planned
(development), let people live inside that building (maintenance), and
move development resources to 100 floor building as planned, without
changing plans in the middle of construction, not getting stuck on 10
floor building construction because plans change all the time and
never getting to that 100 floor building. Its good to have solid
immutable tools that you can depend on. Imagine there are devices
already deployed out there that may not be possible to update, yes
maintenance (in terms of keeping them inter-operational) may be the
priority in that case, because replacing all devices may wipe out the
company and leave owner with ubearable financial debt.

I know this CRC is an important and quite hard problem, and I hope
there can be a win-win solution where users have choice when they need
one, thank you for bringing this up to the attention.. to be honest I
have no clue what is the best solution here if there is no standard to
relay on :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Reply via email to