interviewer was wrong that major reason is because internally react converts class to functions, if that was the main reason then we could use babel plugin which does that, anyways when we run npm run build, it is compiled to functions, major reason is react in future wants to imporve performance which can be done only with functional components like concurrent rendering
No after hooks we can have state inside functional components so Functional components are also statefull components. earlier when there is no hooks it is stateless component.
Key takeways for me: Have a reliable internet connection. Don't try to explain everything just by examples, because example is just one usecase, one usecase doesn't entirely defines a technology. Atleast understand the general definition of popular methods like, spread, rest, closures, currying, useEffect, etc. Dont't use jargon words like, global-context, lexical-scope, hierarchy, etc. Even if we know the significance of those words but don't know the exact meaning. A three years experience interview and doesn't know redux? Don't say I don't know. Instead say something like, "I don't think I've came across that term, to my knowledge". You not one time tried to make the interviewer clarify the quetion, you just listened to the nouns and told him what those nouns are. This was a really bad interview. And in this time of layoffs I don't think this interview is gonna work. Anyways good content, learned a lot of things.
