No, that's not it. Instead it's the right-wing "geniuses" running the government that have been a major cause of this. The NCP and Finns Party keep making a mess of things in the name of their ideology.
An individual pirate is morally a lot less objectionable than the capitalist class pirating from literally everyone else.
Yeah sure, it's on the open Internet, but then again, the capitalists could also actually adhere to the licensing terms of the free software they're hoovering up and all that. These are the same people who want to enforce all kinds of EULAs against the commons, employing measures such as DRM to protect their "intellectual property", so why is it suddenly okay to not comply with IP when it's them doing the infringement?
And that's just with software, but this also affects other creative endeavours. Also the individual HN user's 132 TB Plex server doesn't suck up ludicrous amounts of resources from the commons.
The difference with the book example is that having to hand over a list of books is tangible whereas technological profiling is extremely subtle and abstract in comparison. As IT professionals it's of course easy to see the ways that this kind of stuff can be abused, whereas the probability that someone outside of the industry or otherwise not interested in computers to be "woke" enough about the digital panopticon is diminishingly rare.
And there's of course also Sinclair's law, so even people who should know better might be either willingly ignorant or just not care if it means that they can maintain their quality of life, moral bankruptcy be damned. Similar arguments can be raised for example with the anthropogenic climate catastrophe or other abhorrent phenomena where there's a big chasm in the knowledge between laymen vs experts.
It is exceedingly difficult to convince someone that something is a problem unless said problem is staring the person in the face.
Surely tabs are only ambiguous if one considers the point of indentation to be to align things visually in relation to each other, as opposed to just being, y'know, indented.
Besides, I'm sure many people would look at your Scheme snippet and argue that it's not really about indentation as much as alignment of the subforms, because in a Lisp those two things are basically equivalent, and that the distinction between indentation and alignment is mostly a thing for the curly-brace or otherwise ALGOL-esque languages like Pascal or in this case Python. And in those cases the use of "tabs for indentation, spaces for alignment" is fairly popular although I don't frankly know if many editors actually support that.
I do however think that this whole discussion of spaces Vs tabs is pretty asinine and mostly just stems from people just wanting to align code text visually across lines. It's the same way people insist on monospaced fonts even though one could easily make the argument that proportional fonts are easier to read. Oh well, even I'm not _that_ deprived.
> the use of "tabs for indentation, spaces for alignment" is fairly popular although I don't frankly know if many editors actually support that.
It all works swimmingly until you introduce a nested scope (indentation, tabs) in the middle of an aligned scope (spaces). At that point it still works in the sense that everything is correctly aligned however depending on the editor the tabs might not all have the same width if you aren't able to disable tabstop.
So it isn't generally recommended for lisps in practice (because most common editors will correctly align any given block but when considered in whole the formatting will be inconsistent) but poses near zero problems for most c like languages. (If you're determined you can manage to create problems in a c like by nesting an anonymous lambda within an aligned list of statements or similar such shenanigans. However pretending that python or c++ is a lisp is generally frowned upon so in practice all tabs can be expected to appear to the left of any spaces.)
The other problem I've personally seen with "tabs for indentation, spaces for alignment" is when your editor destroys your tab-space mix when it adjusts the indentation. I've personally seen an editor, I believe VS Code but I don't remember for certain (EDIT: on second thought it was probably Visual Studio, as my memory is placing me in an office I worked in around 2010 or 2011, before VS Code was created), turn a `...` line into `...` when I intended or dedented it as part of a code block. I.e., I added or removed an `if:`, highlighted a section of code, and pressed the Tab or Shift-Tab shortcuts. And boom, that section of code was no longer in correct "tabs for indentation, spaces for alignment" syntax: the editor had converted a certain number of alignment spaces into tabs.
That was one of the moments that made me move away from tab characters in all circumstances. Because the only way to prevent that sort of thing from happening would be either to fix the editor bug (which I don't have time to do), or to turn on visible whitespace and pay close attention to whitespace every time I make an indentation change, knowing that the editor will sometimes do the wrong thing. I don't want to have to pay close attention to whitespace, and the only way I've found not to have to pay close attention is to either never align things at all, or never use tab characters. Tabs for indentation and spaces for alignment works great in theory, but in practice I have found I can't trust major editors to handle it right.
Then again, it's not like even before the plagiarising slop machines you couldn't just get around licenses if you were dedicated enough to evil and was comfortable lying about the provenance of the code you're using.
Sure, it'd make all the lawyer types nervous for obvious reasons, but that's why you'd also need to be comfortable with the evil deed. But you're correct that the evil plagiarism machine makes it way easier.
reply