Hello, just a recommendation. If something is prone to missuse by the users, don't remove it.
Rather: * Document clearly it's quirks. * Provide checks and assertions catching the missuse. On Sun, Apr 23, 2023, 14:49 Sebastien Lorquet <sebast...@lorquet.fr> wrote: > Hello, > > I have a similar feeling about this. > > Remember, if it isn't broken, dont fix it. > > Sebastien > > > On 4/23/23 13:32, Tomek CEDRO wrote: > > hey there Yun, i am also strongly against removing working code that had > > been here for a long time has been carefully designed gives granular > > control etc. > > > > understanding of the code and possible misuse is up to developer. > > > > maybe the problem needs better explanation and discussion which is always > > good. > > > > but removing basic building blocks that work and already have strong > > dependencies is not how things are done in unix world. in fact this is > the > > kind of approach that destroys modern world (and the ict technologies). > it > > is impossible to build anything with no solid fundaments that constantly > > change. progress is about systematic development, step by step, on what > is > > already here, not by enforcing changes and removing things that work, > > evolution not revolution. > > > > have a good day :-) > > > > -- > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > > >
