Skip to content

feat: update FAQ #151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
magnus-madsen merged 1 commit into from
Jul 12, 2025
Merged

feat: update FAQ #151

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions src/page/Faq.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -608,6 +608,21 @@ class Faq extends Component {
</Answer>
</QA>

<QA>
<Question>
Interesting project but whoever decided "forM" is a good name for a language keyword should be made to gurgle Tabasco sauce for a few minutes.
</Question>
<Answer>
<p>
We much prefer <a href="https://en.wikipedia.org/wiki/Cholula_Hot_Sauce">Cholula Hot Sauce.</a>
</p>
<p>
That said, <code>forM</code> is clear, concise, and works well with <code>forA</code> allowing one to easily switch
between monadic-code and applicative-code.
</p>
</Answer>
</QA>

<QA>
<Question>
How the fuck can anyone understand such weird syntax? I hate all these symbols.
Expand Down