A bit more README
Getty Ritter
7 years ago
52 | 52 | |
53 | 53 | ## Frequently Asked Questions |
54 | 54 | |
55 | Nobody has asked me these, but I assume that if someone wanted to ask | |
56 | me questions, they would probably be some of these. | |
57 | ||
55 | 58 | ### Why? |
56 | 59 | |
57 | 60 | It's my party, and I'll bikeshed if I want to. |
58 | 61 | |
59 |
### Why |
|
62 | ### Why not Markdown? | |
60 | 63 | |
61 | 64 | Markdown isn't easily extensible, and also it's fraught with |
62 | 65 | edge-cases and difficult to implement in a new language. TeLML is |
63 | 66 | extensible, and it's easy to write a naïve recursive descent parser |
64 | 67 | for it in basically any language. |
65 | 68 | |
66 |
### Why |
|
69 | ### Why not XML? | |
67 | 70 | |
68 | 71 | I know XML is eXtensible, after all, but—do _you_ want to write XML by |
69 | 72 | hand? Because _I_ don't. Yeah, `\em{foo}` is more heavyweight than |
70 | 73 | Markdown's `_foo_`, but it's also a fair bit more lightweight than |
71 | 74 | XML's `<em>foo</em>`. |
72 | 75 | |
73 |
### Why |
|
76 | ### Why not ReStructured Text? | |
74 | 77 | |
75 | 78 | Because I didn't know about its extensibility when I started writing |
76 | 79 | TeLML, and now this exists and I use it and I don't really want to |
77 | 80 | switch. |
81 | ||
82 | ### Are there other language implementations? | |
83 | ||
84 | I have less-polished Scheme and Rust implementations that I haven't | |
85 | put online yet. I'm planning on using the Rust implementation for a | |
86 | project at some point, so it might show up before too long. | |
78 | 87 | |
79 | 88 | ### Why is your code so bad? |
80 | 89 |