diff options
Diffstat (limited to 'src/blog/gsp/index.gsp')
| -rw-r--r-- | src/blog/gsp/index.gsp | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/src/blog/gsp/index.gsp b/src/blog/gsp/index.gsp index 5fae118..3989073 100644 --- a/src/blog/gsp/index.gsp +++ b/src/blog/gsp/index.gsp @@ -34,7 +34,7 @@ html lang="en" { Why do I mention all of this? Well as anyone who’s ever tried their hand at web-development knows, websites are written in HTML. I wish I could say that’s a good thing, but as anyone who’s ever looked at HTML - before would know, that language is — to put it lightly — really not + before would know, that language is – to put it lightly – really not great. It’s extremely verbose, and awkward to write- and edit (angle brackets are not the easiest-to-reach keys on the keyboard). } @@ -115,11 +115,11 @@ html lang="en" { p {= While Pug certainly hits the ‘maintain the same structure’ point right - on the head, it fails in one very crucial area — it’s a JavaScript + on the head, it fails in one very crucial area – it’s a JavaScript library @em{-only}, and so requires a whole JS setup simply to transpile your site to HTML. What a bummer. There is also a second issue which is that it uses an indentation-sensitive syntax. Normally I am actually - a fan of languages like this — such as Python — but in the case of a + a fan of languages like this – such as Python – but in the case of a markup language like Pug, this is terrible as it makes macros and templating with tools such as @code{-m4} exceptionally difficult. Pug @em{-does} offer templating faculties via JavaScript, but I really try @@ -152,7 +152,7 @@ html lang="en" { p {= Templating and macros are also very easy via macro processors thanks to the use of braces instead of whitespace-based scoping. As an example, I - like to have code samples in articles like this one — but I like to have + like to have code samples in articles like this one – but I like to have the code in an external file. To achieve this I use the following m4 macro to insert the named file verbatim into my document with delimiters escaped. As a bonus it also syntax-highlights diffs: @@ -228,7 +228,7 @@ html lang="en" { p {= As you can see, this is all really simple stuff, which is what I love so - much about Tree Sitter — it’s just so easy! With these basic + much about Tree Sitter – it’s just so easy! With these basic annotations your editor knows that attribute values should be highlighted like strings, braces like tag delimiters, etc. In a similar vein, writing a query to describe code-folding is really easy: @@ -250,7 +250,7 @@ html lang="en" { to instead identify the specific thing that annoys you and find a fix for it. I thought that the syntax of HTML was annoying and bad, so I found a solution for the syntax, while keeping the core structure the - same. In the same line of thinking, try not to over-abstract — I’m + same. In the same line of thinking, try not to over-abstract – I’m looking at you, Java developers. Abstraction often leads to exponentially increased complications the moment we want to do anything different or out of the ordinary, so unless you can find a really nice @@ -266,4 +266,4 @@ html lang="en" { footer { FOOT } } -} +}
\ No newline at end of file |