Frontend

A piece of Software concerns Presentation Layer

Frontend complexity incurs costs higher than backend, requiring careful management. Native experience, UI reusability, and complexity budgeting are important.

Frontend is determined by the product. While creative frontend can be built, there are established patterns for mass-market UIs like KakaoTalk, YouTube, Instagram, and Facebook. Just as short-form video converges to similar formats across TikTok, Reels, and Shorts, and Text LLM interfaces converge to chat interfaces, the product dictates the frontend design.

Interview_Question_for_Beginner/FrontEnd at master · JaeYeopHan/Interview_Question_for_Beginner

HTML 마크업을 처리하고 DOM 트리를 빌드한다. ("무엇을" 그릴지 결정한다.) CSS 마크업을 처리하고 CSSOM 트리를 빌드한다. ("어떻게" 그릴지 결정한다.) DOM 및 CSSOM 을 결합하여 렌더링 트리를 형성한다. ("화면에 그려질 것만" 결정) 렌더링 트리에서 레이아웃을 실행하여 각 노드의 기하학적 형태를 계산한다. ("Box-Model" 을 생성한다.) 개별 노드를 화면에 페인트한다.(or 래스터화) Reference 웹에서는 수많은 이벤트(Event)가 발생하고 흐른다.

https://github.com/JaeYeopHan/Interview_Question_for_Beginner/tree/master/FrontEnd

Interview_Question_for_Beginner/FrontEnd at master · JaeYeopHan/Interview_Question_for_Beginner

Front end and back end - Wikipedia

In software engineering, the terms front end and back end refer to the separation of concerns between the presentation layer ( front end), and the data access layer ( back end) of a piece of software, or the physical infrastructure or hardware.

https://en.wikipedia.org/wiki/Front_end_and_back_end

Frontend

A piece of Software concerns Presentation Layer

Backlinks

Recommendations