> Programming language design is at the same time the most interesting technical challenge you can take on, while at the same time being for the most part an ut

> Programming language design is at the same time the most interesting technical challenge you can take on, while at the same time being for the most part an utter waste of time. Yeah that's a hard disagree for me dawg. But when you write a programming language understand that you're writing it for yourself, so that you can look at other programming languages and understand the tradeoffs. Just the process of going through "holy shit, this thing I'd like to build is going to be so much harder than I thought" is useful. Particularly if you come to understand that some things you want are at odds with each other and you can't build it the way you thought you could. Then you can look at other languages and understand that to have feature A they had to give up feature B. Give up pretty quickly on things once you start to get the feel that they're pretty intractable and you start to hate thinking about them. If you enjoy something in particular then jump down the rabbit hole. Understand that you're going to wind up with something only 10% done that nobody will use. Then maybe when you learn a new programming language go write your language in the new language to learn it. Wash, rinse, repeat to learn new languages. Get good at rewriting your toy language.