Requested by Benjamin Motz over email
I totally agree. It would be a great way to actually look at and to get actually hex data from the actual offsets that it says in things like CFF Explorer on Windows (And yes I can open up ELF format assemblies in it).
Two issues come to mind with this:
compiler-explorer if their binary output can be downloaded, because [note: this isn't how I feel, but roughly the line of logic they tend to follow] people who only need a few functions thoroughly optimized may simply use the online service to optimize and download said functions and skip out on paying for [the vendors'] compiler[s].Thanks @haneefmubarak for your input. Both are real issues. I need to come up with a decent solution for (ab)use, as I plan on launching a RESTful API for even the existing functionality, which will require some level of rate limiting/throttling. All that said though, currently I've been surprised by how well the existing infrastructure scales.
I'm actually pretty convinced this is a bad idea now. As @haneefmubarak says we don't want to be a compilation farm, and implementing the infrastructure to support this is out of scope for now. If anyone feels strongly about this we can add it to the long term, but in the interests of keeping our issue list manageable, I'm closing this.
Most helpful comment
Thanks @haneefmubarak for your input. Both are real issues. I need to come up with a decent solution for (ab)use, as I plan on launching a RESTful API for even the existing functionality, which will require some level of rate limiting/throttling. All that said though, currently I've been surprised by how well the existing infrastructure scales.