Listen to the Podcast:
Google has announced that WebGPU, a potent API that grants web applications greater access to a computer’s graphics device, will be enabled by default in Chrome 113. This is an exciting development for gamers. This update is anticipated to be released in approximately three weeks and will enable WebGPU usage on Windows devices with Direct3D 12 support, macOS, and ChromeOS systems with Vulkan support.
In a recent blog post, it was disclosed that WebGPU enables developers to create sophisticated graphics without writing extensive code. In addition, the API offers a remarkable improvement of “more than three times” in machine learning model inferences, which is particularly thrilling given the current popularity of generative AIs and large language models.
Although Google’s Bard and Microsoft’s Bing do not utilize local hardware, there is a significant opportunity for innovative machine learning applications that can take advantage of WebGPU’s enhanced performance.
According to Google, the imminent release of WebGPU this month will serve as a stepping stone for future enhancements and revisions. The company has pledged to introduce even more sophisticated graphics features, enhanced access to shader components, and enhancements to the WebGPU content development process. The forthcoming updates are likely to provide developers with an even greater opportunity to build immersive web applications with advanced graphics capabilities.
Read More: WhatsApp Introduces New Status Features
Since 2017, WebGPU has been in development, and the API’s capabilities have been enhanced over time. WebGPU will shortly be enabled by default in Chrome, but it will not be a Chrome-only feature; Firefox and Safari are also anticipated to support it in the future. Beyond Windows, macOS, and ChromeOS, Google intends to expand its implementation to additional operating systems.
Google recently announced intentions to accelerate the release of future Chrome browser versions. Google plans to “feature block” stable releases at a later stage of development, despite the fact that the schedule for stable releases will remain unchanged and there are no plans to release them earlier. This will decrease the time between when developers stop adding new features and when the public can access the build. These modifications are intended to enhance the Chrome development process and expedite the delivery of the most recent features and enhancements to users.
