# Modern Frontend Development

## Hot Takes

1. [Typescript](https://www.typescriptlang.org/) is better than Javascript
2. [The Cascading part of CSS is a mistake](https://www.youtube.com/watch?v=iniwPUEbPUM)
3. [CSS-in-JS](https://github.com/emotion-js/emotion) (a.k.a. CSS-in-TS) is good
4. Style overrides are almost never good
5. Immutability and purity are essential
6. [Redux is mostly irrelevant](https://kentcdodds.com/blog/application-state-management-with-react)
7. GraphQL is cool
8. [Approaches like redux-thunk and redux-saga are an anti-pattern](https://github.com/bfollington/use-stream)
9. Typescript should just add support for pattern matching and `|>` 
10. Semicolons suck
11. If you've gotta use CSS, use [BEM](http://getbem.com/introduction/)

## Technology Stacks

### Web

#### React

* Typescript
* emotion
* rxjs
* Ramda (or Sanctuary)
* fp-ts
* framer-motion
* use-spring
* jest

#### Reason

* ReasonReact
* bs-css
* wonka

#### Elm

* Elm

#### F\#

* F#
* Fable
* [Feliz](https://zaid-ajaj.github.io/Feliz/)
* Elmish

### iOS

#### SwiftUI

#### React Native


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://notes.bf.wtf/programming/modern-frontend-development.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.