After years of language creation, absorb essential advice: define a clear purpose, use established libraries, write tests and documentation, and brace for complexity and extended effort.
My experience in developing programming languages has emphasized the importance of starting with a well-defined goal and design philosophy. Using established libraries for parsing and interpretation can drastically reduce initial complexity and streamline development. Testing and documentation are indispensable, as they assist in tracing issues and refining the language over time. Though the process is arduous and prone to unexpected challenges, focusing on incremental development and clear code structuring can provide significant long-term benefits. This measured approach has proven effective in my practical projects.
lol, language design is wild. i learnt that starting small helps alot. build a simple prototype first then scale up. breaking stuff sometimes teaches more than perfect planning. it’s a bumpy but fun ride!
hey ppl, crafting a language is wild. ever thought of starting with an experiemintal dsl core to test ideas rapidly? i’m curious if mixing paradigms early on could boost creative flexibilty. what do u all reckon?