Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Google Chrome

Chrome 113 To Ship WebGPU By Default (phoronix.com) 43

While Chrome 112 just shipped this week and Chrome 113 only in beta, there is already a big reason to look forward to that next Chrome web browser release: Google is finally ready to ship WebGPU support. From a report: WebGPU provides the next-generation high performance 3D graphics API for the web. With next month's Chrome 113 stable release, the plan is to have WebGPU available out-of-the-box for this new web graphics API. Though in that version Google is limiting it to ChromeOS, macOS, and Windows... Yes, Google says other platforms like Linux will see their roll-out later in the year. The WebGPU API is more akin to Direct3D 12, Vulkan, and Metal compared with the existing WebGL being derived from OpenGL (ES). From Google's blog post: WebGPU is a new API for the web, which exposes modern hardware capabilities and allows rendering and computation operations on a GPU, similar to Direct3D 12, Metal, and Vulkan. Unlike the WebGL family of APIs, WebGPU offers access to more advanced GPU features and provides first-class support for general computations on the GPU. The API is designed with the web platform in mind, featuring an idiomatic JavaScript API, integration with promises, support for importing videos, and a polished developer experience with great error messages.

This initial release of WebGPU serves as a building block for future updates and enhancements. The API will offer more advanced graphics features, and developers are encouraged to send requests for additional features. The Chrome team also plans to provide deeper access to shader cores for even more machine learning optimizations and additional ergonomics in WGSL, the WebGPU Shading Language.

This discussion has been archived. No new comments can be posted.

Chrome 113 To Ship WebGPU By Default

Comments Filter:
  • by account_deleted ( 4530225 ) on Thursday April 06, 2023 @12:30PM (#63430720)
    Comment removed based on user account deletion
  • by Tablizer ( 95088 ) on Thursday April 06, 2023 @12:30PM (#63430722) Journal

    "exposes modern hardware capabilities" = Hakt

  • Always a second class citizen, when is DEI going to work for us?

    • by HiThere ( 15173 )

      I think I'd be just as happy if this NEVER showed up on Linux. It sounds like a *really* bad idea.

      • Comment removed based on user account deletion
        • Re:Linux (Score:5, Insightful)

          by Junta ( 36770 ) on Thursday April 06, 2023 @01:47PM (#63430908)

          There's a difference between wanting modern graphics, and being concerned that more open ended access to GPU could mean more than just modern graphics, including security risks for an area that has traditionally had local execution or higher level graphics library doing gatekeeping. One could imagine that it may turn out to be possible to use a shader to DMA in some memory from another piece of the browser process that was *ostensibly* sandboxed before. It wouldn't be the first time that in a rush to give web developers full access to the browser system resources that security problems were a result.

          • including security risks for an area that has traditionally had local execution or higher level graphics library doing gatekeeping.

            You know your security concerns could be alleviated simply by looking at the pretty picture in TFA. Literally no one is talking about bypassing the existing local libraries doing gatekeeping here.

            • by Junta ( 36770 )

              By traditional, I meant more restricted like WebGL, versus Vulkan where you have more arbitrary access.

              The thing that is new here compared to current usual usage of Vulkan, is that a browser represents mixed trust domains in a single process. All those OS mechanisms in the pretty picture are designed to protect processes from each other, not so much a process from itself. A web browser in pursuit of efficiency mixes financial institutions and random crapware game sites all together in the same browser spa

          • Anything's possible, but the GPU enforces memory protection in its memory, and the IOMMU enforces memory protection between the GPU and the system, so it seems like the risk is fairly low and could be easily mitigated by having the GPU zero memory after release in its idle time.

            • the risk is fairly low and could be easily mitigated

              Go tell that to Nintendo. The 3DS had gspwn. [3dbrew.org] Which used the fact that the GPU could bypass the kernel's memory protections. [3dbrew.org] This was actively used back during the early 3DS years to get homebrew (and "backups") working.

              Even better, Nintendo failed to learn from their mistake with the 3DS and made it again on the early Switch models too. [switchbrew.org]

              Not saying that PCs will have the exact same GPU issues mind you. Just giving a reminder that these things can happen in unexpected (and in some cases unpatchable) ways

            • by Junta ( 36770 )

              The stress would be that in most GPU usage scenarios, the entire calling process is considered the same trust domain.

              In a browser, they generally try to have different trust domains in the same process, which as far as the underlying OS and hardware are concerned are equally entitled to memory accesses. So those mechanisms are generally not expecting to have to protect memory of a process from that same process. So a 'fun game' tab knowing an exploit *might* somehow read memory unexpectedly, but it's the

          • I'm old enough to remember ActiveX, and how it allowed ordinary web pages to practically cripple the PCs on our college campus with crapware like Comet Cursor. You'd think someone would have thought running executable code right off the Internet was a terrible idea, but some corporate asshats went along with it anyway.

            Never underestimate the damage that can be caused by reckless innovation. No, I don't want web pages to have low-level access to the GPU, let alone the ability to probe USB hardware or gauge

      • All it needs is the approval button. Thereâ(TM)s things we need to do, like work on Jupyter notebooks with chatGPT. OpenAI cannot run our code, we need to run our own. Part of that equation is webAssembly, part of it is WebGPU. AI computing makes way more sense on the edge, especially for media.

        • by Junta ( 36770 )

          It may make sense on the edge, but that does not necessarily mean it must be on a web browser. It's rather unfortunate that the only non-datacenter 'platform' that is given any consideration is a web browser.

  • by CrappySnackPlane ( 7852536 ) on Thursday April 06, 2023 @12:55PM (#63430794)

    If it means we can go back to playing Quake Live at work, then fine. Otherwise, I can't really figure the draw.

    • Admit it, you work from home and run full games when you are supposed to be working - making this a feature that is dubious at best.
    • by reanjr ( 588767 )

      This will not help put Quake in the browser. WebGL already exists. I'm not quite sure what point this serves other than crypto mining. I'm sure there are some things this can do that WebGL can't, but it's definitely at the edges of what's necessary.

    • Because we all prefer the web to be funded by advertising?

      Dunno if you've seen the censorship-industrial complex that's spawned or not.

  • by NMBob ( 772954 ) on Thursday April 06, 2023 @01:00PM (#63430804) Homepage
    Future advertisements are going to be AWESOME!
    • Future advertisements are going to be AWESOME!

      Just like Getting the News in HD -- as so many stations are fond of boasting, for some reason.

    • Nah, they're going to run ChatGPT training directly on your GPU... with the data they gobble from you.

  • by xack ( 5304745 ) on Thursday April 06, 2023 @01:21PM (#63430852)
    This seems to be the first "killer feature" that has been added to Chrome(ium) since the dropping of Windows 7 at version 109. Online games will start using it and video sites will probably use it as DRM. We all know we should "upgrade already" from Windows 7, but there is still a lot of people and companies who can't. If Firefox doesn't add Windows 7 support for WebGPU then it looks like it will be a hard end for Windows 7. I just hope Chrome doesn't add "WebPluton" in a few years.
    • Sadly, Windows 7 would be an upgrade for one company I know, which was still using XP as recently as last spring.
    • What killer feature is that exactly? So I can hear my usually stopped GPU fans spool up when I check the news or weather? Why do I need that? If it is on a laptop the feature should be disabled by default. Hell it should just be disabled by default.

      Ok games. Browser games. But why? Most games in a browser suck anyway, so why?
      • by Junta ( 36770 )

        I generally agree with being wary of the feature, however "Most games in a browser suck" as an argument is a bit of a self-fulfilling prophesy here. The browser games suck in part because they don't have access to do this stuff.

        However, I do not like the continual 'as-a-servicing' of everything, since the biggest reason to make a non-sucky game browser based is to basically have supreme drm over not letting you run it locally.

    • by Merk42 ( 1906718 )
      Windows 7 has been EOL for over 3 years now. You should have already said goodbye to it long ago.
    • When's the last time you played a game delivered through a browser? I haven't since the days of flash. It's going to be used for novelties, and for ads, and for ads for novelties.

    • This will become the new flash. Advertisers will abuse this. Malware/Miners will abuse this. Every social media site you open will throttle up your GPU which will either make fans spin like crazy or eat your battery if on a laptop.
  • I personally lack "courage" to ever use something like this. It seems unnecessarily reckless to a comical extent. The only thing I can think of that would be more reckless is implementing native sockets in browser.

  • by Anonymous Coward
    In all their fanfare the pirates on the Chrome team forgot to mention that they ripped off theblueturtle_'s Battle Damaged Sci-fi Helmet [sketchfab.com] for their glamor shots. And they still fucked it up because they didn't make the emissives emissive. :(
  • I feel like this is probably something Google wanted in the browser because it has something to do with enabling more capabilities on a Chromebook?

    (That's a scenario where users typically have very limited disk storage space to install local applications, and possibly lack user permissions to do so. But they might want to offer more graphics-intensive applications to them through a browser session.)

    Otherwise, I agree with people that this just seems like it will cause more problems than it solves. Advertise

    • gamers will still prefer locally installed programs that load large maps and backgrounds from their SSD, vs trying to stream *everything* over the Internet connection.

      The desires of gamers are irrelevant. Corporate demands piracy-proof*, game streaming-as-a-service TODAY!

      *: OK, it's not entirely piracy-proof. But, the amount of work required to reconstruct a complete game from a recorded video stream is currently sufficient to deter most would be pirates.

  • Finally, everyone can help the scammers mine some useless crypto!

They are called computers simply because computation is the only significant job that has so far been given to them.

Working...