Well, my plan is to write the v1.0 compiler with the syntax that it itself implements and then try to rewrite it barely good enough to compile itself in v0.3
My language has changed a bit since it was first created so I dunno if Lang fits but basically it's a text processing language and specialized for things like parsing data like CSV, JSON and other programming languages and making compilers. Originally my only goal was for it to be very good for compilers, assemblers, etc so that's why I called it "Language for Languages" so just Lang
Getting external feedback might be helpful, as often other people will spot things that you didn't while designing... but also requires some time, and if it's something you've poured a lot of passion in, also the ability to handle well criticism, as not everyone is always nice on the Internet...
The buffer thing sounds very peculiar! Reminds me a bit of Lisp and Perl, but approaching functional programming with a focus on the processing chains themselves instead of the operations they're composed of, kind of like what Bash does with pipes!
@steffo I'm basically just trying to optimize as much as possible, the solution to these text processing problems. My language will probably be sacrificing a bit of performance for that but this will get better over time. The interesting thing is that since this is a "language language", you can just come up with your own syntax that's suited for solving a specific problem and since my language can do just in time, you can just place that custom code in a buffer and process it while compiling into valid Lang syntax. This optimizes some problems like assemblers with their big tables. I have this and many many more features in mind that will hopefully help optimize development time by a huge factor. I may need to go through quite a few iterations when making the v1 standard document and ill probably ask people on here for their time