Skip to content

Comment on Making a Python interpreter in 1024 bytesparent

Comments

I think we would need to balance practicability and code size since they tend to be mutually exclusive. Generally speaking, code size is not an important metric to make useful code, and usefulness is usually not the main point of code golf exercises such as this one.

The exception to this is obviously embedded systems with very low amounts of resources where C and assembly are practically unrivaled.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.