why would I care about scaling my dotfiles, my zsh custom prompt, or my icon colors?
That those things don't scale is hardly news.
yak-shaving is fun and an experience in itself. not every activity needs to scale.
I just wrote a netfilter_queue[1] based DNS filter in C[2] to extract IDN/punicode domains from the kernel queue and drops the packet.
This is only useful to myself and maybe a handful of those who: run a local resolver, disable DoH, and hate punicode/IDN with enough passion to actually want to block it. But it has probably no use in the wider world because it only adds complexity for them. According to this post, now I should feel bad because it doesn't scale? What a strange way of looking at things.
I don't mean to disagree... yak-shaving is fun, and you get to learn about the internal workings of so many tools during the whole process (I myself am trying to have every project 'make'-able, with self-documenting Makefiles).
But I see the point the author has made:
That personalized configurations are hard to recreate for other users, particularly those that are less technologically adept.
Comments
why would I care about scaling my dotfiles, my zsh custom prompt, or my icon colors?
That those things don't scale is hardly news.
yak-shaving is fun and an experience in itself. not every activity needs to scale.
I just wrote a netfilter_queue[1] based DNS filter in C[2] to extract IDN/punicode domains from the kernel queue and drops the packet.
This is only useful to myself and maybe a handful of those who: run a local resolver, disable DoH, and hate punicode/IDN with enough passion to actually want to block it. But it has probably no use in the wider world because it only adds complexity for them. According to this post, now I should feel bad because it doesn't scale? What a strange way of looking at things.
[1] https://netfilter.org/projects/libnetfilter_queue/doxygen/ht...)
I don't mean to disagree... yak-shaving is fun, and you get to learn about the internal workings of so many tools during the whole process (I myself am trying to have every project 'make'-able, with self-documenting Makefiles).
But I see the point the author has made:
That personalized configurations are hard to recreate for other users, particularly those that are less technologically adept.
And then, you're stuck maintaining everything...