articles such as this one usually are optimized for their audience, you just aren't the audience. that's ok. I'm rarely the audience either :) a quick search should give you what you're looking for https://www.science.org/doi/10.1126/sciadv.adz3040
@programming.dev
articles such as this one usually are optimized for their audience, you just aren't the audience. that's ok. I'm rarely the audience either :) a quick search should give you what you're looking for https://www.science.org/doi/10.1126/sciadv.adz3040
for me vencord is working well doing what asked about https://vencord.dev/
GNU taler has been working on this, I guess someone just needs to adopt it. https://www.taler.net/en/index.html
I think calling one way better than the other is flawed. The reason the title is saying that tabs are objectively better is because they are used in addition to where spaces are used elsewhere. You could make the same argument in favor spaces due to keeping things simpler.
The argument of having variable indent size for tabs so viewers can decide how big they are is imho legitimate but also not the goal as it's addressing something that teams generally agree on. There is max characters per line, brace placement, general code style and rules. Yes we can eject the indentation from the rules that are agreed on but once again simplicity over complexity has an equal say.
In the end it doesn't matter that much, a good programmer will be able to work in either setting, the Editor will do most of the work anyways.
With all that said, spaces all the way!
thanks for using Leebra!
go to feed...