Sorry for the late answer and the missing context. usef- is right, the manual is probably the better page to share. Amp tries to give you a plug and play experience, where you can always see the actual costs and models/effort are autoselected for you. Some of my colleagues are big fans and use it a lot. I also like it, but prefer OpenCode.
We recently adopted Bruno at our company and I'm very happy with it. Versioning your requests with GIT is great, and the client is really nice as well.
Funny, the weather bit is also true of us Germans. Even our saying is almost the same. "Es gibt kein schlechtes Wetter, nur schlechte Kleidung." And we also have this one: "Wir sind ja nicht aus Zucker." (We're not made of sugar.)
Oh, that was fun; great article! During my MA, I wrote a paper on Swedish Melodic Death Metal lyrics and what common themes they have. I can't seem to find the paper now, but I remember having a blast. I think the result was something like anger, violence, and loyalty/brotherhood.
He's got a point. TypeScript alleviates some pain, but I still feel like JS is not a great language. I have some nostalgic love for it because I used to be "the JavaScript guy" at the beginning of my career. But ever since I started using TS and Go, using Vanilla JS feels like fighting code smells and complexity all the time. At the same time, I acknowledge and appreciate how much JS has improved.
I am not a big fan of nesting. I have yet to see a codebase where nesting makes CSS more readable. Even with BEM, I find it easier to reason about (and debug) the vanilla style. However, I must admit that `&:hover{}` does have a certain appeal. Also, I am very happy that nesting can be done without tooling in the future. It's a feature that many people love.
We've also been copied in the past. At first, it was a little concerning. But it turned out that people cannot be ahead of you if they're busy copying your features.