The Google Play Store uses a technique called delta patching to calculate the diff server side and avoid transferring parts of the app that haven’t changed since your original installation.
This is understandably not perfect because they want to avoid load on their servers and also the extra processing on your device to “unpack” it. So what you have is a happy medium between sending the entire app again and sending strictly the diff.
I think code golf is a great dataset for this kind of analysis specifically because they are artificial and people are paying attention to the number of characters used. Leetcode solutions might be a better option though.
In real world projects there are too many confounding factors. People aren’t implementing servers in brainfuck or websites in C. Even rewrites of a project into another language have more/fewer features. So it’s an apples to oranges comparison.
Even when running an instance for yourself, you’re not really safe. The threat to your privacy goes from being a third party in control of your data to your own operational inexperience.
I tried to host my own personal Lemmy instance and ran into a lot of issues hosting it. On the one hand you want to be safe by restricting unnecessary access, but on the other hand you have no idea why federation doesn’t work, or the postfix-relay docker cannot send an email, or why you cannot ssh into your own host, so you want to just allow everything and just get it to work somehow. In the end, unless you are already an expert at this stuff, trying to host your personal instance safely is a tall task.
It’s also going to be very costly. Especially for an image sharing website like Pixelfed.
Maybe there is a market for self-service managed hosts like we have with Wordpress blogs.
You know, saying that everyone except caucasians are “people of color” itself reeks of inherent racism.
Racism is quite common in the world. It always has been. It’s just that in most of our history our out-groups were still local so racism didn’t manifest.
Right now we’re at a point in the human journey where we see people of different races quite often, but we don’t interact often enough that it is no longer relevant for anyone. It’s improving.
Well, life is about trade-offs and neither spaces or tabs are perfect in every scenario, but the industry overall prefers spaces over tabs nowadays and the tooling reflects that too. For me personally, as long as a project is consistent in its formatting and developers don’t need to fight its tooling, I’m happy with either. We can yak shave all we want (and lots of people are doing that on the internets) but I hope I at least answered your initial question about why people prefer spaces over tabs.
It makes a difference when you’re working on a large project with lots of people. Even Linux mandates 1 tab = 8 spaces
.
The only argument i see in favour of tabs is the “i can change the width on my own machine!” which isn’t very convincing if you are working on a team and need to follow conventions every time you commit code. The indentation will keep looking weird on your machine.
If you’re using monospaced fonts for writing code (please tell me you are) spaces make sure that the code will look roughly the same on everyone’s machine.
def function(paramX: str,
paramY: str,
paramZ: str) -> int:
pass
If I’d used tabs, the second and third parameter might not align with the first.
Also, left-side indentation is only a small part of the overall whitespace in code. You’re adding whitespace even when you write x = y
. Spaces make sure that this whitespace around the =
grows in the same scale as the indentation.
To play the devil’s advocate, most professional development happens on proprietary IDEs but software development isn’t under their control. AI assisted intellisense isn’t much different. The nature of our work will become more abstract as our tools improve. There are at least some open LLMs. One of them might surface as the alternative.
You missed a /s marker