-
Notifications
You must be signed in to change notification settings - Fork 17
feat: add summary for 250 #310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
ankushhKapoor
merged 7 commits into
OurTechCommunity:main
from
Ayushmore1214:add-summary-250-v2
Nov 4, 2025
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
6256c52
feat: add summary for 250
Ayushmore1214 6360ee4
Update attendees list in attendees.adoc
Ayushmore1214 f7c3d24
Update content.adoc
Ayushmore1214 b3b211b
fix: attendees
SirusCodes 15f2708
Apply suggestion from @ankushhKapoor
SirusCodes 7b25b4e
Apply suggestion from @ankushhKapoor
SirusCodes 1a1f9cb
Apply suggestion from @ankushhKapoor
SirusCodes File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,77 @@ | ||
| ==== Attendees | ||
|
|
||
| . link:https://twitter.com/adityaoberai1[Aditya Oberai^] | ||
| . link:https://x.com/Alpastx[Alpesh Bhagwatkar^] | ||
| . link:https://x.com/ankushhKapoor[Ankush Kapoor^] | ||
| . link:https://twitter.com/bhavesh878789[Bhavesh Kukreja^] | ||
| . link:https://www.linkedin.com/in/chetandoesdev[CHETAN JANGIR^] | ||
| . link:https://twitter.com/SirusTweets[Darshan Rander^] | ||
| . link:https://twitter.com/DhiruCodes[Dheeraj Lalwani (Dhiru)^] | ||
| . link:https://twitter.com/harshgkapadia[Harsh Kapadia^] | ||
| . link:https://twitter.com/imhritik_dj[Hritik Jaiswal^] | ||
| . link:https://twitter.com/KartikSoneji_[Kartik Soneji^] | ||
| . link:https://twitter.com/mohit_explores[Mohit Gangwani^] | ||
| . link:https://www.linkedin.com/in/mhshetty[Mohit Shetty^] | ||
| . link:http://x.com/naufildotdev[Naufil Asar^] | ||
| . link:https://twitter.com/NinadNaik07[Ninad Naik^] | ||
| . link:https://twitter.com/PranavDani3[Pranav Prasanna Dani^] | ||
| . link:https://twitter.com/KundnaniPratik[Pratik Kundnani^] | ||
| . link:https://twitter.com/t3_pat[Pratik Thakare^] | ||
| . link:https://twitter.com/mehraramyak[Ramyak Mehra^] | ||
| . link:https://twitter.com/rishit_dagli[Rishit Dagli^] | ||
| . link:https://twitter.com/SaifSaifee_dev[Saifuddin Saifee^] | ||
| . link:https://twitter.com/tanay_texplorer[Tanay Kamath^] | ||
| . link:https://twitter.com/tusharnankanii[Tushar Nankani^] | ||
| . link:https://www.linkedin.com/in/uma-iyer-205bb112a[Uma Iyer^] | ||
| . link:https://twitter.com/code_magician[Viranchee L^] | ||
| . link:https://twitter.com/WilfredAlmeida_[Wilfred Almeida^] | ||
| . 07 Sumit Gelani | ||
| . 34_AI2_Meenakshi Mishra | ||
| . Abhinav Singh | ||
| . Abhishek | ||
| . Abhishek Girnare | ||
| . Ankit Singh | ||
| . Aryan | ||
| . Ashish Makhija | ||
| . Ayush Shukla | ||
| . Bhoomi Sakhrani | ||
| . Chethan Kumar | ||
| . DEV TANK | ||
| . Dhawal Abhonkar | ||
| . Eshaan Vaswani | ||
| . Fahed PC | ||
| . Faiz khan | ||
| . Gauri Khanolkar | ||
| . Janvi Matani | ||
| . Krupal Vasani | ||
| . Kunal sawant | ||
| . MAHEK MATANI | ||
| . Manish | ||
| . Mitesh Shah | ||
| . Mohammad Kaif | ||
| . Naman | ||
| . Neha Nikam | ||
| . Phantom0 Strike | ||
| . Pooja | ||
| . Prasad Patil | ||
| . Qais Khan | ||
| . Rahul | ||
| . Rahul Poswal | ||
| . Ram Naik | ||
| . Riddhi Menroy | ||
| . Rohan Hazari | ||
| . Rugved Raorane | ||
| . Saachi Kokate | ||
| . Sagar Valecha | ||
| . Sahil Bansal | ||
| . Saif Saifee | ||
| . Shivendra Patil | ||
| . Shlok Bagwe | ||
| . Siddhant Shetty | ||
| . Soumik Biswas | ||
| . Tanmay Narkar | ||
| . Vivek Galatage | ||
| . kachara seth | ||
| . prajwal dhule | ||
| . sarthak kuwar | ||
| . shweta nadar |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,60 @@ | ||
| Date: 23-08-2025 | ||
|
|
||
| Duration: 3 hrs 25 mins | ||
|
|
||
| ==== Topics Discussed | ||
|
|
||
| * Vivek, a browser engineer with over two decades of experience, delivered an insightful technical talk about modern web browser architecture and internals. | ||
| ** He has contributed to major projects including Chromium, WebKit, and browsers like Arc and DIA. | ||
| ** Vivek explained how browsers have evolved from simple rendering engines into complex, multi-process systems resembling operating environments. | ||
| * Vivek discussed the multiprocess architecture that modern browsers use for enhanced stability and security. | ||
| ** Each tab runs in its own isolated renderer process managed by a privileged browser process. | ||
| ** This architecture ensures that crashes in one tab don't affect others, improving overall browser stability. | ||
| ** He explained how browsers use Interprocess Communication (IPC) frameworks like Chromium's Mojo for secure message passing. | ||
| *** link:https://chromium.googlesource.com/chromium/src/+/HEAD/mojo/README.md[Chromium Mojo Framework^] | ||
| * The discussion covered browser performance mechanisms and task scheduling. | ||
| ** Browsers prioritize visible tabs and throttle background processes to ensure optimal performance. | ||
| ** This prevents misuse of system resources and maintains smooth user experience. | ||
| ** Vivek explained how browsers use GPU acceleration and synchronization techniques like VSync to maintain 60 FPS. | ||
| * Vivek explored the rendering pipeline and how browsers transform web code into pixels on screen. | ||
| ** He discussed the complex process of converting HTML, CSS, and JavaScript into visual output. | ||
| ** The talk covered GPU acceleration techniques used in modern browsers. | ||
| * Performance debugging tools were a major focus of the discussion. | ||
| ** Vivek demonstrated Chrome DevTools and its capabilities for performance analysis. | ||
| *** link:https://developer.chrome.com/docs/devtools[Chrome DevTools Documentation^] | ||
| ** He introduced Perfetto, a system-wide performance analysis tool. | ||
| *** link:https://perfetto.dev[Perfetto Performance Analysis Tool^] | ||
| ** These tools help engineers trace performance bottlenecks, frame drops, and input latency across processes. | ||
| * Security was another central theme of the talk. | ||
| ** Vivek discussed sandboxing mechanisms and permission management in browsers. | ||
| ** He explained mitigations for hardware-level vulnerabilities like Spectre and Meltdown. | ||
| *** link:https://spectreattack.com[Spectre and Meltdown Vulnerabilities^] | ||
| ** Speculative execution vulnerabilities exploit CPU-level optimizations, leading browsers to enforce stricter control over JavaScript execution. | ||
| ** Just-in-time (JIT) compilation security measures were also discussed. | ||
| * During the interactive Q&A session, participants engaged deeply with technical questions. | ||
| ** Questions covered IPC mechanisms, GPU handling, and memory management in browsers. | ||
| ** There was discussion about the feasibility of transitioning browsers toward a microservice-based model. | ||
| ** Vivek explained that while microservices might offer modularity and fault isolation, the overhead would likely outweigh benefits in browser contexts. | ||
| * The discussion touched upon CPU-level concepts and their impact on browser performance. | ||
| ** Topics included pipelining and branch prediction in modern processors. | ||
| ** Vivek connected low-level processor behavior to browser performance and security vulnerabilities. | ||
| ** The relationship between CPU architecture and browser security was explored in detail. | ||
| * Community members actively shared resources and insights throughout the session. | ||
| ** Links to W3C specifications and documentation were shared. | ||
| ** Articles about Spectre and Meltdown vulnerabilities were referenced. | ||
| ** Additional browser development resources were exchanged. | ||
| * The session concluded with overwhelmingly positive feedback from attendees. | ||
| ** Participants praised Vivek's ability to make complex browser internals understandable. | ||
| ** The talk was acknowledged as one of the most enlightening technical sessions in recent times. | ||
| ** Community members expressed gratitude for the rare, behind-the-scenes look into browser architecture. | ||
| * Shared links : | ||
| ** link:https://developer.chrome.com/docs/devtools[Chrome DevTools Documentation^] | ||
| ** link:https://chromium.googlesource.com/chromium/src/+/HEAD/mojo/README.md[Chromium Mojo Framework^] | ||
| ** link:https://perfetto.dev[Perfetto Performance Analysis Tool^] | ||
| * Relevant Links from the Talk | ||
| ** link:https://youtu.be/BiuknvAYDPs[Talk Recording^] | ||
| ** link:https://drive.google.com/file/d/1f4_WKrJINYOAzQpe62DmK8oqDVFP93Vx/view[Talk Slides^] | ||
| ** link:https://x.com/vivekgalatage/status/1875468178509517206[Vivek Galatage on Chromium's Multi-Process Architecture^] | ||
| ** link:https://x.com/vivekgalatage/status/1881537398124724224[Vivek Galatage on Key Data Structures in RenderingNG^] | ||
| ** link:https://x.com/vivekgalatage/status/1947647032056799289[Vivek Galatage on the Spectre Vulnerability (CppCon Talk)^] | ||
| ** link:https://x.com/vivekgalatage/status/1947562726513164693[Vivek Galatage on Browser Mitigations for Spectre^] |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.