The commenter argues that developers should solve problems in the language of the domain, using domain-specific languages (DSLs) so solutions map naturally to domain concepts and teams can communicate with experts. In practice, they say, programmers are constrained by mainstream host languages picked for them and therefore embed DSLs (eDSLs) inside those hosts - citing jQuery and React as examples. That leads to multilingual systems composed inside a common host, and the commenter contends this multilingual eDSL programming is currently ad hoc, awkward, and burdens developers with extra tooling and integration work.
According to the commenter, typical workflows force developers to step outside the host language to create and deploy languages, fiddle with configuration and compilation, and link object files; host languages themselves lack mechanisms for sound integration across eDSL components, and most IDEs fail to recognize or support eDSLs. They present Racket and the broader idea of language-oriented programming (LOP) as an attempt to bridge the gap - providing primitives to create, use, and integrate eDSLs immediately - and frame the debate as one between an ideal, domain-centric development model and the messy realities of existing languages, toolchains, and IDEs.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.