Timeline for Does Google care about code formatting?
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 16, 2020 at 10:32 | history | edited | CommunityBot |
Commonmark migration
|
|
Feb 27, 2016 at 9:57 | history | tweeted | twitter.com/StackWebmasters/status/703519243866935296 | ||
Feb 25, 2016 at 17:14 | comment | added | Binh LE | I think Google not care about this. | |
Feb 24, 2016 at 20:22 | comment | added | Ajedi32 | Google the company? Yes. Google the search engine? No. | |
Feb 24, 2016 at 18:35 | comment | added | Hagen von Eitzen |
Even if the human-readable file should be somewhat larger, it is well possible that the zipped (i.e., Transfer-encoding: gzip ) version is not larger, especially if the structuring is consistent (sach as always two newlines between rules)
|
|
Feb 24, 2016 at 17:29 | comment | added | Richard Parnaby-King | The second developer's argument is that it reduces file size. | |
Feb 24, 2016 at 17:20 | comment | added | MrWhite | Possibly pedantic but you never can tell... "One developer is trying to convince the other to put line-breaks between rules in his css file, as opposed to inline. The argument is that it reduces the file-size" - you seem to have your "argument logic" reversed? | |
Feb 24, 2016 at 16:38 | answer | added | knif3r | timeline score: 4 | |
Feb 24, 2016 at 16:29 | comment | added | Stephen Ostermiller♦ | If you are minifying the CSS after it is developed, Google will only ever see the minified version. They way that the code is formatted for your developers can only ever by an in-house issue at that point. | |
Feb 24, 2016 at 12:29 | answer | added | Rob | timeline score: 8 | |
Feb 24, 2016 at 12:25 | history | asked | Richard Parnaby-King | CC BY-SA 3.0 |