It seems that Google is thinking about the future of the web. In each new launch of your browser, such as the one v94 less than a month ago, adds features for developers. The end user cannot take advantage of these new features on their own, but they will improve their experience when developers start to use the APIs. This Tuesday, Google He launched Chrome 95, and, once again, there are several novelties in this regard.
But things are not always added. Sometimes you have to take a step back to move forward with more force, and in software that usually means that support for something is abandoned. Some time ago they had started to leave the FTP protocol behind, and with Chrome 95 the final step has been taken; the end of the support is complete. Below you have a list with some of the news They have come together with the 95th version of the Google browser.
What's new in Chrome 95
- Support for FTP has been completely removed. They started dropping it in Chrome 88, and now it's no longer available.
- New URLPattern API that provides operating system support for URLs that match a provided pattern.
- New EyeDropper API for creating custom color pickers.
- Attempts have been made to reduce the exposed HTTP user agent string information to reduce the potential browser footprint of websites.
- Access control to the file system access API. This can provide much better performance, as well as new use cases.
- WebAssembly's secure payment confirmation and exception handling has been promoted out of its previous proofs of origin.
Chrome 95 It is now available from the official website. From there, Linux users can download installers that will also add the official repository for future updates. On Arch Linux based distributions it is available in AUR as google-chrome.
Good to Know. Although I had no idea why chrome used the FTP protocol. Now I have more doubts than before. How is it possible for the chrome browser to use FTP and what do you use it for?