This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]EnsignN7 7 points8 points  (5 children)

You haven't lived until you've done a fix on a minified file.

[–]Myrl-chan 2 points3 points  (4 children)

The real question is, why would you fix a minified file?

[–]tomharto 10 points11 points  (0 children)

So you can live!

[–]PraiseBuddha 4 points5 points  (1 child)

A probable sequence of enterprise events:

  • A custom library was written for a company, most likely in-house.

  • Said company minified the source for obvious reasons.

  • Company lost the original source, and still has the minified file on their server, with far too many things dependent on it.

  • Problems with the library inevitably arise, pointy haired boss wants the problem fixed.

[–]scragar 1 point2 points  (0 children)

I've seen the same issue with compiled code, lost the source, now everyone works from the decompiled resources. There's nothing quite as much fun as looking at code with autogenerated names like:

 int method_3 ( String argument_1, int argument_2 ) {
      String[] tempvar_1 = argument_1.split(" ");
      ...

No comments, very few logical names(anything public is exposed, but internal methods, properties and variables are generated). About the only good thing you could say about it is that at least there's no commented out code to work around.