Aligning '=' on protocol buffers .proto files

Should the equals sign be alined on protocol buffers? I am having a huge discussion with a colleague and we can't get to decide on what's the best practice.

message foobar {
optional bool var_one_short             = 1;
optional bool var_two_looooooooong_name = 2;
optional bool another_var               = 3;
}


vs

message foobar {
optional bool var_one_short = 1;
optional bool var_two_looooooooong_name = 2;
optional bool another_var = 3;
}

-

I think the second version is much easier to maintain. If you have a new variable with a longer name (like var_two_reaalllllly_looooooooong_name) you don't have to modify three other lines too to keep it nice. The first version also could cause unnecessary patch/merge conflicts.

From Code Complete, 2nd Edition by Steve McConnell, p758:

Do not align right sides of assignment statements

[...]

With the benefit of 10 years’ hindsight, I have found that, while this indentation style might look attractive, it becomes a headache to maintain the alignment of the equals signs as variable names change and code is run through tools that substitute tabs for spaces and spaces for tabs. It is also hard to maintain as lines are moved among different parts of the program that have different levels of indentation.

-
I think it's important to note that a lot of modern editors support this (example: Sublime Text 2), so maintenance becomes trivial. –  seand Feb 28 '13 at 16:19
I use sublime and yes it makes it easier. But his opinion convinced me. –  fmsf Feb 28 '13 at 16:21
I like more the first solution because it visually groups together the variables on the left side of the = and the value on the right side. Unfortunately I can't back this preference with a strong reason other than personal taste.