9 ms·
Sorry for nitpicking, maybe you didn't think through the choice of word, but what is a "technical" argument and how is it different from other types of argument
by robalni 3mo ago
Sorry for nitpicking, maybe you didn't think through the choice of word, but what is a "technical" argument and how is it different from other types of arguments?
I think all arguments about a technology like systemd need to have a technical part (what systemd does) and a (sometimes implicit) personal part (what I think about it). If it doesn't have the technical part then I don't think it's an argument about systemd at all.
The difference I can see between your example arguments is that the "technical" one is more precise. "Not supporting x" is pretty specific while "being bloated" is not very precise. But of course it could be more precise if you say something like "systemd is made of x megabytes of code. I only want the code I need which I think can be implemented in 1% of that" or just "systemd includes parts x, y and z which I don't want".
So did you by "technical" just mean "precise" or is there another meaning that I missed?
- 0dayz 3mo agoTechnical as in there a precise and empirical reason for it such as a technological reason for it. The bloat argument is perfectly suitable once you remove its derogatory meaning and instead say resource constraints such as when working in embedded.