Google Chrome goes to use your own rendering engine Blink

Зображення до статті Google Chrome goes to use your own rendering engine Blink
Зображення до статті Google Chrome goes to use your own rendering engine Blink
HTML code:

Google Chrome, based on an open Chromium project and is the most popular browser in the world, has decided to give up Webkit engine in favor of its own Blink. This solution has led to anxiety among web designers.

🧠 Blink's new engine, according to Google, will be directed to a modern web, with many improvements, especially in the DOM Reverming area, which is vital for multi -media aspects of HTML 6, 7 or 8.

  • 📌 Google Chrome goes to Blink's own engine.
  • 📌 Blink is designed for modern Web, with improvements in the Randering area Dom.
  • 📌 Blink transition can lead to compatibility problems in mobile web.
🧩 Summary: Google Chrome goes to Blink's own rendering engine, which, according to Google, will bring improvement for modern Web. However, this solution can lead to problems for web designers, especially in mobile web.

💡 Browser prefixes used to support different browsers will not be supported in Blink. Instead, the experimental functions will be hidden by the 'flang of experimental functions'.

🧠 Own considerations: Google's decision to switch to Blink can have both a positive and negative impact. On the one hand, it can speed up a web, but on the other, it can make the work of web designers more difficult because of potential compatibility problems.

Коментарі

Увійдіть, щоб залишити коментар