Announcement

Collapse
No announcement yet.

Chrome 65 Now In Beta With The CSS Paint API

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Chrome 65 Now In Beta With The CSS Paint API

    Phoronix: Chrome 65 Now In Beta With The CSS Paint API

    Google released the latest beta of the Chrome/Chromium web-browser today. Chrome 65 Beta isn't as exciting as some past browser updates, but there are still some new additions to note...

    http://www.phoronix.com/scan.php?pag...Chrome-65-Beta

  • #2
    Arguably most prominent to Chrome 65 Beta is the new CSS Paint API that allows for programmatically generating an image wherever a CSS property expects an image.
    I thought we already got that feature with Cagify or nShrek extensions =P





    https://chrome.google.com/webstore/d...aejlmfol?hl=en

    Comment


    • #3
      What about making thing important to user?
      Like being efficient on resources?

      Comment


      • #4
        Ha ha ha! That Cagify extension I love the Internet.

        Comment


        • #5
          Originally posted by Royi View Post
          What about making thing important to user?
          Like being efficient on resources?
          That's already done, as a side effect of seeking higher performance in all things. High resource usage hurts performance, so the browsers try to use as little as possible of each resource class without it negatively impacting performance in another way. That balance achieves the most pleasing overall user experience.

          There's different definitions of high resource usage... for example:

          1) high memory usage - keeping cached uncompressed images in memory, keeping a fully rendered copy of every block element in memory, etc.

          2) high disk usage - caching more data to disk than the user is comfortable using for caching.

          3) high bandwidth - not caching data so it keeps having to be pulled from the 'net

          4) high CPU usage - discarding previously rendered block elements when they are not visible and having to render them again when they are visible again

          Notice how using less disk for caching uses more bandwidth.

          Notice how using less memory caching of block elements leads to more CPU usage.

          So, which is more important to you? Disk space? Bandwidth? Time? Memory? CPU/GPU usage / battery life?

          It's a balancing act, and the browser vendors are extremely concerned with all these things. Don't kid yourself otherwise.
          Last edited by linuxgeex; 02-10-2018, 08:48 AM.

          Comment

          Working...
          X