Yes, but in this case of spaces you get a strict style guideline. It lacks flexibility for user preferences and accessibility when working on a collaborative project.
About compression, do you think a website running PHP has minified files? The code is still on the server and using more disk space.
As I said, I'm on your side. I just think that if you do not show the arguments of the other side, your argument falls flat.
If you are running PHP, chances are it is running on apache2 or in some cloud environment. If you can't setup mod_compress or whatever equivalent is used in the cloud (which usually is one configuration switch), then storage is probably the least of your issues.
I suppose a claim of "significant savings in storage space" requires backing besides just the difference in number of characters, since real-world file storage is more sophisticated than storing bytes as-is.
If anything, it makes me curious on if there are savings, how much is it really?
While I am on the same team as you for mainly the same reasons, you neglected to address the arguments of the other side:
With spaces, you ensure the same formatting without the need to set up different editors and IDEs.
Since the code is usually stored and transferred in a compressed format, the difference in size is negligible.
Yes, but in this case of spaces you get a strict style guideline. It lacks flexibility for user preferences and accessibility when working on a collaborative project.
About compression, do you think a website running PHP has minified files? The code is still on the server and using more disk space.
As I said, I'm on your side. I just think that if you do not show the arguments of the other side, your argument falls flat.
If you are running PHP, chances are it is running on apache2 or in some cloud environment. If you can't setup mod_compress or whatever equivalent is used in the cloud (which usually is one configuration switch), then storage is probably the least of your issues.
There is of course some optimization possible but the code remains stored statically initially.
In a world where open source is important, user preferences and accessibility seem sufficient reasons to me. ;-)
I guess... has anyone actually done the math yet?
I suppose a claim of "significant savings in storage space" requires backing besides just the difference in number of characters, since real-world file storage is more sophisticated than storing bytes as-is.
If anything, it makes me curious on if there are savings, how much is it really?
Just did some maths with latest version of WordPress: dev.to/cyrez/comment/2d723