Design patterns & good practices – don't want having multiple small files (w/ longer fsck!!!) –the fish's source directive
Of course, pacman.conf NoUpgrade directive can omit this negative result/impact – but I don't like too much mess (chaos, if you can read) in system, although. It suffices American language is narcistic psychopathy chaos from ancient view! Why they code, code, code!!!?? Maybe to make something similar to Esperanto? No, rather to be still unfunky „monkey” — despite IT, sci, & more.
Yea, but Linux administration has to be practical.
They should mention it just inside fish shell manuals. Additionally, coproc functionality should be programmed AGAIN – NOT such PLANNED PRODUCT AGING (REGRESSIONS).
Alex Jones is right in his narration.
I remember regressions even from good open source soft of Bender/Bfor Artists!!!!
Fine that they used paranthesis — "()" — in fish command line. BUT why TO CUT HISTORICAL, GOOD PRACTICE in name of „new”, „new”, „ANEW” ??
No comments:
Post a Comment