Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
posted by CoolHand on Wednesday December 16 2015, @08:41PM   Printer-friendly
from the the-more-things-change-the-more-they-stay-the-same dept.

While both Betteridge's Law and common sense say, "No," Zack Whittaker at ZDNet takes a closer look:

An analysis of the last five-months' worth of monthly software updates shows that Edge had 25 vulnerabilities shared with versions of Internet Explorer, which had a total of 100 vulnerabilities.

Earlier this month on its scheduled Patch Tuesday update offering, Microsoft released MS15-124, a cumulative update for Internet Explorer, and MS15-125, a near-identical patch for Edge. Of the 15 flaws patched in Internet Explorer, 11 of those were also patched in Edge.

According to a Microsoft blog post earlier this year, the software giant's newest browser, an exclusive for Windows 10, is said to have been designed to "defend users from increasingly sophisticated and prevalent attacks."

In doing that, Edge scrapped older, insecure, or flawed plugins or frameworks, like ActiveX or Browser Helper Objects. That already helped to cut a number of possible drive-by attacks traditionally used by attackers. EdgeHTML, which powers Edge's rendering engine, is a fork of Trident, which still powers Internet Explorer.

[...] Older versions of Internet Explorer will be retired by mid-January, giving millions of users about a month to upgrade to Internet Explorer 11, or to Edge on Windows 10.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by Common Joe on Thursday December 17 2015, @07:40PM

    by Common Joe (33) <common.joe.0101NO@SPAMgmail.com> on Thursday December 17 2015, @07:40PM (#277845) Journal

    Except that WYSIWYG doesn't work either and does have surprises. Some people with poor eye sight require larger fonts and that alone means everyone won't see the same thing. Then there are those who are fully blind. Again, the website is a different experience for them.

    As for me, it drives me nuts when I put two web browsers side by side on my big monitor (1920 x 1080 resolution) because I want to compare two different pages on the same screen and because I'm using tree style tabs [mozilla.org] on the sides, I now don't have enough space on my browsers to read everything. It's a pain to switch the settings around or not see them side by side.

    My opinion has been and continues to be to give control back to the user. I'm not an expert in front end design so I'm probably oversimplifying this, but my gut tells me that too much control has been taken from the user. Fixing it so everyone has the exact same experience seems like the wrong way to do it.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Thursday December 17 2015, @11:04PM

    by Anonymous Coward on Thursday December 17 2015, @11:04PM (#277971)

    Re: "Some people with poor eye sight require larger fonts..."

    It's vector-based, not pixel-based. Thus, it can be scaled up and down as needed without pixelation artifacts, similar to the Control-Plus and Control-Minus keys in a web browser. Nor does the idea preclude accessibility tags and attributes in the markup.