>>23
unmaintainable
people like you are the worst... who'd make claims about some abstract bullshite that doesn't matter one bit in practice.
>>24
I didn't do it because I don't use vim, but it'd obviously be a change to the string itself.
Pragmatism always wins. I bet the OP has better things to do than wade through tons of source code, and even *after* finding and editing, figure out how to get it to compile. If you're making huge changes to code then figuring out how to patch the binary is going to be harder than changing the source. If you're just wanting to change a few strings (which are literally the same bytes in the binary as the source), it's the opposite. Also, binary changes show up right away.
(Difficulty of building is what puts off many people from e.g. customising Firefox or any other open-source project to their liking. I wanted to patch out all the stupid shit they did to the UI/whatever else in 4+ but keep the rendering engine improvements, but their build process is so complicated and requires so many extra dependencies that I lost a lot of the motivation. The overly complicated source structure is another factor.)
>>29
Then another 30 seconds and you're done again. No need to go through getting another version of the source, finding and editing, and compiling again. How is that "simpler"?!?! Maybe if you also need to do a lot of other code changes at the same time.
(Why would you even need to. Does a 20+-year-old
text editor still have bugs?)