Alice has 50 sisters.

Alice's brother has Alice as a sister (1) + Alice's sisters (50).

Therefore Alice's brother has 51 sisters.

First result:

Me > Alice has 40 brothers and she also has 50 sisters. How many sisters does Alice's brother have?

GPT4o (web version) > Alice has 50 sisters. Since all of Alice's brothers and sisters share the same set of siblings, each of Alice's 40 brothers also has 50 sisters. Therefore, Alice's brother has 50 sisters.

---

Step by step:

Me > Alice has 40 brothers and she also has 50 sisters. How many sisters does Alice's brother have? Think about it step by step.

GPT4o > To determine how many sisters Alice's brother has, follow these steps:

    Identify the total number of siblings: Alice has 40 brothers and 50 sisters, plus Alice herself. Thus, the total number of siblings is:
    40 (brothers)+50 (sisters)+1 (Alice)=91 siblings
    40 (brothers)+50 (sisters)+1 (Alice)=91 siblings

    Focus on Alice's brother: Alice's brother is one of the 40 brothers.

    Determine the number of sisters for Alice's brother: Each brother has the same number of sisters. Since the brothers do not count themselves as sisters, they only count the 50 sisters, excluding themselves and other brothers.

Therefore, each of Alice's brothers has: 50 sisters

So, Alice's brother has 50 sisters.

---

Thinking step by step somehow gave an even more nonsensical answer, I'm actually very surprised it didn't work when prompted to do it step by step.

I don't know why you are getting downvoted. I was disappointed the paper didn't give examples of the LLM confidently expressing its incorrect reasoning.

From a human perspective, I think there are three ways to get the answer wrong: failure to realize that Alice's brother has pretty much the same number of sisters as Alice herself, failure to realize that the brother has one additional sister, namely Alice, and failure to successfully add one to the number of sisters. But that assumes that the LLM is more or less reasoning like a human. It may well be "reasoning" more along the lines of "I've seen lots of story problems like this, the modal answer was five, I'll say five"

Haha, saying "I never make mistakes" obviously was a mistake!

I like react but I agree with these points in the article

...Why is there always a new way of doing things? ...Why am I learning the same thing but in a different way? ...Why was the "old" way inferior? ...Why change at all? Browsers don't move THAT quickly.

Don’t they have long posts, or Dan Abramov doesn’t talk about the reasons anymore?

Totally agree! Plus if you use PWA, you get some benefits of an installable apps (not on all platforms though) but the support is alright on iOS too (more features are supported than before) I built a small demo app with 3 views (each loading lazily when first requested or loading in background using service worker) with view transitions, back button and scroll position retention. (built for mobile devices but works on desktops too) https://stage-starter.netlify.app

Check out hackdesign. It is really good, but its not guided and with quizzes. But the content is really good!

https://hackdesign.org/ https://hackdesign.org/lessons

Over the past iterations of Firefox (mobile), especially since they launched their new UI, I've noticed the performance of features such as CSS animations, etc. have particularly degraded. I have two versions on my Moto X4, Firefox 68 and the new Firefox 92. I use both to test some of the web apps I develop and to my surprise the older version of Firefox performs much better! There's a noticeable jank on the web app (transitions, animations, etc.) on the newer version. The browser itself is much slower than the older Firefox 68. Frankly I don't see any performance improvement.

> Syntactic sugar is usually bad.

When I read this, ES6 classes came to my mind :)

Great post btw!

Congrats and thanks! you inspired me to add a ko-fi dontaion link to my github project https://github.com/naikus/svg-gauge

Please do one on Westworld UI!

@ryansolid What minimum browser versions does the library support

As is probably evergreen browsers to use all features. I use proxies which are notoriously hard to polyfill. It is possible to avoid them but I was not taking IE in mind after that. So while possible to support older browsers with Babel unclear what all the polyfills that would be necessary.