It's getting ridiculous: We've already seen games running inside PDF files, AI models, and even Microsoft Word documents. Now, an indie developer has managed to create a fully playable version of Pong that renders across a staggering 240 Google Chrome browser tabs. And when we say tabs, we do really mean the tabs themselves; the favicons, specifically. Dubbed "Faviconic Pong," this unusual implementation comes courtesy of developer Nolen Royalty. It builds upon another unusual implementation in which a version of Flappy Bird was played solely within a single favicon. While that was impressive in its own limited way, Faviconic Pong takes things several notches higher with an even more bizarre implementation.The game essentially spreads the action between the main Chrome window showing the lower half of the screen, while the array of 240 tab favicons handles the upper portion. The classic Pong paddles, ball, and scoring all behave just as you'd expect it's just that those objects are not limited to the scope of a browser's viewport and can stretch to the myriad of tiny tab icons.It achieves this neat visual trick through clever AppleScript for macOS. The developer tapped into Google Chrome's internals, writing code that can precisely control the favicon for each tab and rapidly update the tiny icons to animate the ball's movement.For those interested in learning more, Royalty's development blog is an insightful read. To summarize, he started by using AppleScript to generate a precise grid of Chrome windows and tabs. Then, he worked on updating favicons quickly and overcoming browser throttling with web workers. To sync tabs, he switched from WebSockets to broadcast channels. Finally, he refined animations, optimized performance, and implemented Pong, making the ball and paddles move smoothly between the main window and tab bar. // Related StoriesIt's worth mentioning that the reliance on AppleScript means Faviconic Pong is currently limited to Macs.While the rendering may be split across a browser window and 240 tabs, the experience doesn't seem to suffer too much. The main viewport footage is smooth, though the framerate is noticeably lower in the tabs section.You can find the complete source code on GitHub. The developer admits that it's "awful" because it never left the prototype stage. But hey, anything to make better use of your unclosed browser tabs, I guess.