I'm confused with the parser and lexer. The lexer takes the rules, the string and parse it into a ComponentToken. That information is fed to parser. The parser renders an HTMLElement from a component token. It does look like the job of lexer is to parse and the job of parser is to render. Why does the names convey a different idea?
thanks for all your videos, i appreciate it, can you make it more like a "Drawling application (lucid chart)", "File-storage application(google drive, dropbox)", or "Rider-sharing app (Uber)" please?
Thanks! I think you pay too much atterntion to the component API design. In the real 45 minutes intreview setting you won't have time for it. And would disagree about dumping websockets: 1) they're different from HTTP protocol, so version doesn't matter 2) with REST you'll have too much load on the backend, possible lost updates and junky experience 3) when in the future, collaboration part will be required, you will have to basically do a major rewrite of the app
Helpful tutorial . But your filming should be better. I couldn't watch comfortably on my mobile device. You should zoom video into focused areas of the screen when explain. Everything looks so tiny.
![[Front-End System Design] - Chat application](http://i.ytimg.com/vi/LEaiGjffLEs/mqdefault.jpg)
Would love to see this channel being updated more!
Your video are mind changing things. Your explantion you so nice that it blows my mind. Please continue
Thank you a lot for the extremely useful content!
I appreciate what you're doing ❤
You always give the best. Thank you so much
Thanks for sharing, Ray!
very insightful, there are so many few good content on FE system design, please keep up the great job
Thank you so much for this quality content, you are the best❤
I'm confused with the parser and lexer.
The lexer takes the rules, the string and parse it into a ComponentToken. That information is fed to parser.
The parser renders an HTMLElement from a component token.
It does look like the job of lexer is to parse and the job of parser is to render. Why does the names convey a different idea?
I think I am in love with this. thank you very much!
thank you for sharing your mythology of breaking problems 3rd eye achieve :)
thanks so much for your efforts!
Great work! Zooming into the parts of the design might help! But you shared the link to the diagram so its ok!
a bit confused about syncing server and client data
can you share your notion page, looks quite useful :)
Nice, thanks!
Thank you!
why page content is stored as String and not as object? what are its advantages
thanks for all your videos, i appreciate it,
can you make it more like a "Drawling application (lucid chart)", "File-storage application(google drive, dropbox)", or "Rider-sharing app (Uber)" please?
Thanks for sharing great ideas! It's in my plan :)
"websockets are not supported in http2"- a bit confused by this. My understanding is they are supported, and have been for years?
The content is good, but I don't know why is blurred.
Please upload more contents
Hello, could you share your resume and talk about it, thanks.❤
Sir do you earn 150k pound sterlings a year in uk? Plz reply. Thanks a lot.
Easy to see on levels.fyi, check senior / staff engineer salary in FAANG
first like the video and watch it 😀
Thanks! I think you pay too much atterntion to the component API design. In the real 45 minutes intreview setting you won't have time for it.
And would disagree about dumping websockets:
1) they're different from HTTP protocol, so version doesn't matter
2) with REST you'll have too much load on the backend, possible lost updates and junky experience
3) when in the future, collaboration part will be required, you will have to basically do a major rewrite of the app
Helpful tutorial
.
But your filming should be better. I couldn't watch comfortably on my mobile device.
You should zoom video into focused areas of the screen when explain. Everything looks so tiny.
Diagram link is shared in the description
I think because you work at Meta, you have a slight bias towards GraphQL. :P