this post was submitted on 16 Apr 2024
36 points (95.0% liked)
Linux and Tech News
1011 readers
1 users here now
This is where all the News about Linux and Linux adjacent things goes. We'll use some of the articles here for the show! You can watch or listen at:
You can also get involved at our forum here on Lemmy:
Or just get the most recent episode of the show here:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is the best summary I could come up with:
You can see glimpses of this newer, less curse-laden approach in how Torvalds recently addressed a commit with which he vehemently disagreed.
The commit last week changed exactly one thing on one line, replacing a tab character with a space: "It helps Kconfig parsers to read file without error."
If you've read this far and don't understand what's happening, please allow me, a failed CS minor, to offer a quick explanation: Tabs Versus Spaces will never be truly resolved, codified, or set right by standards, and the energy spent on the issue over time could, if harnessed, likely power one or more small nations.
By attempting to smooth over one tiny part of the kernel so that a parsing tool could see a space character as a delineating whitespace, Prasad Pandit inadvertently spurred a robust rebuttal:
In fact, let's make such breakage more obvious than some esoteric ftrace record size option.
Yes, tab-vs-space confusion is sadly a traditional Unix thing, and 'make' is famous for being broken in this regard.
The original article contains 476 words, the summary contains 170 words. Saved 64%. I'm a bot and I'm open source!