Comment by rf15
2 days ago
To piss off architects, managers and linguists all at the same time: language isn't much of a standard at all, it's more the current agreed-ish state of things, quite similar to the current state of a code base. Your inner model of what you like things to be is without direct effect to how things de facto are.
In addition: it's not wrapped around a problem, it's wrapped around an attempt at a solution - the problem space is often not even depicted in code, and often only minimally described in documentation.
It is that, and it’s the best we got. Code is downstream and strictly worse. Of course it is great for expressing you want integers of certain sizes being added, but that’s.. yeah, don’t know what to tell you if you think that is the problem domain.
It’s not a secret we use DSL’s to express our Actual Problem. The Ancients told us it is The Way. Problem is devs think stacking int64s in a struct is a proper abstraction boundary.
If you guys would have said proper DSLs are the spec I might have agreed but “code” in general without constraints is useless noise.