Forum Discussion
Dev channel update to 91.0.831.1 is live
Hello Insiders! Today we’re releasing build 91.0.831.1 to the Dev channel. To start out, we’ve got two big features we’re excited to unveil, as well as some other exciting community updates:
...
I got the same error.
I only use edge for testing so it is annoying but not critical. I know that Redhat 7 and it's derivatives are considered old and if dropping glibc 2.17 is MS's decision then so be it. We will just send the Edge testing further downstream where Windows desktops dominate.
If there is a reason for this, that is to say any feature that needs glibc v2.18+ and cannot be built with an older version, I would say OK, I understand.
However, that is a huge compatibility break. Even if they are quite old, the Red Hat Enterprise Linux 7-like distributions are not that obsolete and they still have official updates as far as I know. What is certain is that no more Edge support on this Linux branch removes a lot of universality for this browser.
Was this considered?
However, that is a huge compatibility break. Even if they are quite old, the Red Hat Enterprise Linux 7-like distributions are not that obsolete and they still have official updates as far as I know. What is certain is that no more Edge support on this Linux branch removes a lot of universality for this browser.
Was this considered?
- I can only speculate as to why MS dropped support for glibc <2.18. It may be there is a feature in 2.18+ that is necessary. However, considering that Chromium -- which underlays Edge -- still runs fine on the older platforms I am a little skeptical of that.
In any case, this is not a new phenomenon. I saw similar behavior from Google and Mozilla as Redhat 6 approached it's end-of-life and it makes a certain sense: At the core, Linux is a server OS and a browser is not really necessary on a server. The market for any graphical browser on Linux right now is only a small percentage of the total of Linux installations.
I guess I now have to worry if they will similarly break teams... 🙂
