Programming

17405 readers

60 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

How we reduced the size of our JavaScript bundles by 33% (dropbox.tech)

submitted 1 year ago by [email protected] to c/[email protected]

17 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

For WASM you can probably use tools like ghidra to decompile and read.

Sure, as I said it's similar to decompiling normal binaries, which is hard to read (even when you're used to it).

Minified js not a lot better then raw ASM, single letter names and crazy optimisation patterns will make your life hell. Patching both I think is out of the question, maybe just inject some new js that interact with the DOM.

I'm not talking about reading minified JS. I'm saying: un-minifying JS gets you a way more readable result than decompiling native binaries does. I've done both more than often enough to know this difference well.

I've written mods and patches for dozens of minified sites, and it's never been too hard. I've written mods and patches for native applications, and it's waaaay harder - even just finding free space in the binary where you can inject your code and jump to/from is annoying, let alone actually writing your changes in ASM. All of this is immediately solved even with minified JS.