Skip to content

Comment on How Swiss tables work in Go built-in mapparent

Comments

It’s important for you to hear that this kind of syntax thing really, really doesn’t matter that much. Having this kind of complaint about languages is a sign that you haven’t worked on compilers or learned about the field of programming language theory. Which is fine! But worth knowing that there are more interesting and important things to argue about.

Aspects of language design that are way more important are: the semantics, including type system, memory model, concurrency model, module system and so on; tooling; performance; FFI and OS interface; and lots of other things.

The reason these things matter more than surface-level syntax stuff is that they change what kinds of problems you can solve with the language, and what tradeoffs you’ll accept if you use it.

Of course, hyperpalatable syntax can be a factor in a language’s success, like Python. But at this point it’s Python’s ecosystem that perpetuates its dominance, and if they made some syntax changes it wouldn’t change that by much.

In response to GP post, it's a valid concerns to programmers (to some extend to machine in form of AI/LLM code generation cost see ref [1]), and certainly we have nice things in programming language as D language aptly shows.

Aspects of language design that are way more important are: the semantics, including type system, memory model, concurrency model, module system and so on; tooling; performance; FFI and OS interface; and lots of other things.

D have pretty much all of aspects of your main concerns and being much better than Rust and Go [1].

[1] Language Plasticity is More Important Than Ever:

https://blog.dlang.org/2026/08/10/language-plasticity-is-mor...

AboutSource Built by g1lg1l

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