Not tolerating sexist jokes isn't emotional immaturity. Especially in a very sexist industry and in a sexist society where making these jokes about women is somehow seen as okay by way too many men. It's not funny. I have values (such as those of respect and equality) that stand in opposition to childish jokes like that one. You don't and that's okay, but don't go painting others as "immature" when you're unwilling to recognize your own ethical and moral failures.
Hi, as the author of this repo, I cannot emphasize this same sentiment enough. I've posted explanations elsewhere in the comments, which you're welcome to read if you would like. Regardless the "joke" has been removed.
You're telling someone not to paint others as "immature", yet you're painting them as having ethical and moral failures. I hope you recognize one of these is more severe than the other.
Fortunately there are big and significant parts of the civilised world, where the so-called cancel "culture" is considered a mental disease, and no amount of downvotes some of you will just try to apply will change that.
Even more, in some countries there is a discussion if the cancel "culture" is a part of totalitarian agenda, and if it will be considered as such, it would be prosecuted by a criminal prosecutor, as any other totalitarian stuff. Dodge that....
Yeah it doesn't really land well as a joke because it's the very first thing. Joking hot takes at least need a bit of warm up so readers know what's going on, whereas this just opens with a no-context dis at women where it's not even clear what the joking read is supposed to be talking about. What hard work? What's happening?
I placed it on the readme after a long night of working on this project. The joke was directed at my partner who had giggled with me about the absurdity of writing a dsl to template my website.
That said, I do agree that it doesn't land well out of context for the general audience, and for that reason will be removed
mmm ... i should start my readme as "> black people are always late." it just isn't acceptable even though that's an inside joke where/how i was raised. have some empathy. not everyone is going to get it and it's your responsibility to understand that. no context was explicitly given other that it's quoted so we may or may not attribute the comment as the perception of the README author
You're correct, it was my responsibility to understand how it would be perceived by a wider audience. Without the context of my own identity and the tone of the rest of the readme, it is just sexist.
It's not appropriate because it reinforces the idea that women are fragile and not interested in working for anything. Regardless of my intent when I wrote the readme (which was to suggest that I'm better than other people), it's still sexist in it's essence and delivery
But surely the fact that you can't say it gives credence to the idea that women are 'fragile'. And I've never come across the idea that women aren't interested in working for anything.
This fuss wouldn't have been kicked up if it were the male equivalent. That to me is sexist.
Anyway, you've already deleted it, so it's moot now.
It's a good idea to reduce templating languages into a simpler form, I'll agree to that, but the issue here is that you still need loops and data input.
For example, the test script has a 'li' function but <li>s are list items and they reside, usually more than one, inside <ol> or <ul> elements. At the very least, there should be a way to take some form of data file (list of blog posts and nested metadata) an iterate over it. Otherwise you're just writing whatever markup you want as the output, with an additional layer, and nothing of added value.
This is true. In the spirit of the project it might be good to add a predefined map function.
`(map li (eval "cat file"))`
Where `file` is newline separated text, and li is applied to each line, and the full string is returned.
For this example
```
(func ul "<ul>{0}< /ul>")
(func li "<li>{0}< /li>")
(ul (map li (eval "cat file")))
```
Would return each line of the file nested in a `li` tag nested in a `ul`
Considering this was something I was creating for a specific use case for the fun of it, unless it becomes useful to my goals, and shelling out is preferable as far as I am concerned
While Lisp is my preferred normally my go-to language, tbh I think sed or awk are probably adequate and, already being installed, probably in some sense “better”.
That being said, thanks for posting this; it made me think.
Truthfully I was tired and writing it at 2 in the morning, and I wanted the tone to come across as full of itself. Opening with a epitome of a pick-me statement seemed like the right move
I am not happy with the "joke" in the README and if I could I would report it but it looks like it doesn't fall into Github categorization of abuse. Keep your bad jokes to yourself, inside your head, where nobody can see them.
Based on the rationale given I think the author could have used GNU m4. While I'm definitely not fond of the syntax, it can get the job done. I don't think many (if any) projects use it (excluding autoconf).
TL-WHO, like CL-WHO, compiles the with-html-output form into something that uses constant string literals that are as long as possible. It closes all your tags, HTML-escapes what has to be escaped and can pretty-print with indentation.
Code can be freely used: attributes and tags are distinguished by virtue of being Lisp keywords. Anything that is not a keyword is evaluated as code.
Only when code produces a string is that string interpolated into the output, making it possible to write code with useful side effects and no HTML output, by not returning a string.
Side-effecting code can explicitly write into the HTML stream; the output will go to the right place in the generated HTML:
Note that the output of "ls -l" isn't being HTML escaped; this example just shows how something can write to the stream as an alternative to interpolation, not that it's a good idea to dump ls -l into that HTML stream.
60 comments
[ 5.4 ms ] story [ 124 ms ] threadWhen someone expresses an critical opinion, it is not a violation of someone else's free speech.
Even more, in some countries there is a discussion if the cancel "culture" is a part of totalitarian agenda, and if it will be considered as such, it would be prosecuted by a criminal prosecutor, as any other totalitarian stuff. Dodge that....
I placed it on the readme after a long night of working on this project. The joke was directed at my partner who had giggled with me about the absurdity of writing a dsl to template my website.
That said, I do agree that it doesn't land well out of context for the general audience, and for that reason will be removed
Genuine question. Is it because it's sexist? Would it be appropriate to write "unlike most men"? Unlike most people?
Or is it because it's suggesting the author is better than other people???
This fuss wouldn't have been kicked up if it were the male equivalent. That to me is sexist.
Anyway, you've already deleted it, so it's moot now.
For example, the test script has a 'li' function but <li>s are list items and they reside, usually more than one, inside <ol> or <ul> elements. At the very least, there should be a way to take some form of data file (list of blog posts and nested metadata) an iterate over it. Otherwise you're just writing whatever markup you want as the output, with an additional layer, and nothing of added value.
Otherwise what, template the slisp in Jinja too?
`(map li (eval "cat file"))`
Where `file` is newline separated text, and li is applied to each line, and the full string is returned.
For this example ``` (func ul "<ul>{0}< /ul>") (func li "<li>{0}< /li>") (ul (map li (eval "cat file"))) ``` Would return each line of the file nested in a `li` tag nested in a `ul`
Technically you also need cond, eq?, and pair? (because car and cdr only take pairs not symbols).
That being said, thanks for posting this; it made me think.
Here's the manual on one page https://www.gnu.org/software/m4/manual/m4.html
An m4 example, similar with the snippet within the README
It has a deftag macro for defining new tags.
We can define :atag, which destructures the first two items of its body as url and class: Then use that in the definition of :page: So now that we have :page, wrap that in :li: TL-WHO, like CL-WHO, compiles the with-html-output form into something that uses constant string literals that are as long as possible. It closes all your tags, HTML-escapes what has to be escaped and can pretty-print with indentation.Code can be freely used: attributes and tags are distinguished by virtue of being Lisp keywords. Anything that is not a keyword is evaluated as code.
Only when code produces a string is that string interpolated into the output, making it possible to write code with useful side effects and no HTML output, by not returning a string.
Side-effecting code can explicitly write into the HTML stream; the output will go to the right place in the generated HTML:
Note that the output of "ls -l" isn't being HTML escaped; this example just shows how something can write to the stream as an alternative to interpolation, not that it's a good idea to dump ls -l into that HTML stream.