This stuff is not what makes code beautiful and any code can be converted to look like this with simple formatting tools. Judging code on being 'good' or 'bad' based off whether someone hastily dumped it through a neatness format tool is a terrible precedent.
Code is beautiful if
1) Accomplishes the goal it has to perform in an
easily understandable format.
2) Is designed in a way that modifying one part of
the code will have minimal/no impact on other parts
3) Is named well enough ('self documenting') so that
the amount of comments can be kept to a minimum
4) Hides as much boiler plate code inside helper
functions/libraries as possible so that the real
logic is not lost in a sea of boiler plate.
5) Is specific enough that 'tricks' are not required
to use it for the intended purpose.
6) Uses generalized code in common areas - and has
this generalized code moved to external libraries
for maintenance and re-use across projects.
And very importantly (but often missed in this case): Uses system knowledge to optimize code to run as well
as (within an order of magnitude) the most performant
possible code for that problem can run.
Systems can be as beautiful as they want, but if your OS takes 15 minutes to boot or your FPS game runs at 2 fps (and as people are beginning to notice: your web app server can only handle 50 users), all of your beautiful code is wasted and should be thrown out.