Yikes, I don't see any legitimate use for this, other than hacking for the sake of hacking. Interesting read though.

maccard 3 hours ago | parent | next [-]

Hot reloading for development loops is _the_ canonical use case for this.

lokar an hour ago | parent | prev | next [-]

I’ve seen this in large C++ systems to allow for a runtime patch, generally to add a simple debug call at the start of a function.

	▲	jerf an hour ago \| parent [-]
		While I would never consider this approach advisable in any language that doesn't build in support for this sort of thing from the start, the thinner the runtime, the less dangerous it is. Go's runtime is fairly thick, and also, concurrent. The odds of something blowing up are rather too high for me to even dream of putting something like this into production in Go. In C++ it may merely be somewhat crazy rather than completely crazy. (I suppose Rust is arguably an exception to this; thin runtime, but there's a lot of things the replaced function could do that would still blow Rust up if the rest of the code isn't compiled and correctly optimized to account for whatever the new code does.)

antonvs 2 hours ago | parent | prev | next [-]

wdym, now it will be possible to implement Wordpress in Go

	▲	pjmlp 2 hours ago \| parent [-]
		You could already do that today, via OS IPC mechanisms, at the expense of higher systems resources, with each plugin being its own process.

Well, we are on Hacker News after all...