I recently had to work with XSLT (may it's inventor burn in hell for their crimes).
That's pretty much programming in XML. It's probably the worst possible thing.
XSLT is fine
If you have a program generate it
Sadly, it was done manually. I had to migrate it to this brand new bleeding edge technology, Apache Velocity. That's not great either, but it's much less terrible than XSLT.
For that task I had to learn two templating languages at the same time to port it from one to the other. Wasn't an easy task.
Pff. I know someone who generated programs using XSLT.
Bro the project I'm on uses XSLT and the first time I saw it I legitimately thought I was having a stroke because I could not accept that anybody would be stupid and/or masochistic enough to actually want something like that.
However, I've now made it my mission to master it because it makes me feel like a high-born wizard speaking of ancient secrets in a tower high above humanity
I totally know that feeling :)
Well, in the 90s, XML was the future. Luckily, not a lot of this future remains.
Just imagine what HTML would be like if JSON had been available back then.
No.
You should check out this new project, supposed to be twice as fast as HTML. It's called XHTML.
I thought that was the HTML used by Twitter.
Which of these wonderful languages is this? https://en.wikipedia.org/wiki/Category%3AXML-based_programming_languages
I will never understand how XML came into being when lisp already existed.
I don't either)))))))))
(reminds (it (of (story me))))
Would you really rather see
<\Foo>than)?There's a reason why most popular languages use
}rather thanend iforfi. The added verbosity doesn't actually help people read your code more than e.g. indentation or editors with paren matching or rainbow parens.
Meanwhile in APL, you just
20 50 60 90, 10Who ever designed this deserves to be killed.
What color theme is that?
Looks like Vampire.
someone should make lisp but with html syntax
