Ethereum

A smart contract programming language that prioritises readability, simplicity, and auditability is not just a good idea—it's essential. In our ecosystem, unlike in fields like aerospace engineering where only experts can design and build aircraft, anyone can build and deploy smart contracts. This democratisation of building capabilities—which is a feature to be clear—means we can't just cater to the 1% of highly skilled developers who excel at memory optimisation and EVM intricacies. Instead, we need to empower the 99% who could easily make costly mistakes. Built-in guardrails ensure safer development, and readable code is invaluable for auditors and the broader community. Most people appreciate a language that makes their work more secure and accessible, even if they might not admit it. You may not like this approach, and I'm not here to patronise, but complexity is the bridge to simplicity and not the end goal.

𝐖𝐨𝐫𝐤𝐢𝐧𝐠 𝐨𝐧 𝐰𝐡𝐚𝐭'𝐬 𝐧𝐞𝐱𝐭.

https://github.com/pcaversaccio

100% agree. On the extreme other end of the approach you're suggesting is maker contracts. Maker contracts have an insane amount of TVL, yet reading their contracts is nearly impossible unless you spend quite some time getting used to it. I never understood the rationale behind the unique naming convention