2 ms·
Let's say someone developed a variant of Go with manual memory management. How far would this be from a "friendly C"? EDIT: " I doubt anyone is willing to pay
by stcredzero 11y ago
Let's say someone developed a variant of Go with manual memory management. How far would this be from a "friendly C"?
EDIT: " I doubt anyone is willing to pay 2x performance for their C code to be more friendly. If they were, why are they writing in C?"
Because it's friendly? Because the cost/benefit in terms of avoided bugs and productivity is worth it to the company/shop.
- pcwalton 11y ago> Let's say someone developed a variant of Go with manual memory management. How far would this be from a "friendly C"? Depends on what the semantics of that hypothetical Go variant are. How would that Go variant solve the load-load forwarding problem described in the article? > Because it's friendly? Because the cost/benefit in terms of avoided bugs and productivity is worth it to the company/shop. I think the point the author was making is that if you are OK with that performance hit you're probably OK with Java, which banishes undefined behavior in the C sense entirely.
- stcredzero 11y agoI could see someone being ok with 100% overhead, but not with 400%. Last I checked (which was years ago) hitting 50% native speed in a JIT managed language was an admirable feat and not guaranteed.