SoylentNews is people
SoylentNews
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.
(Score: 1, Interesting) by Anonymous Coward on Thursday December 17 2015, @05:59PM
For the discussion, I'll discuss 3 categories of applications:
1. Brochure-ware: public-facing sites or applications that want to present a pretty or fashionable style for marketing reasons.
2. Business-oriented (CRUD) applications that want to look professional and up-to-date, but a bit less concerned about fashion.
3. Internal specialized CRUD applications that don't care that much about aesthetics or fashion.
For #1 and some of #2, decision makers are probably going to focus on fashion and aesthetics and there's not much one can do about that. Humans are superficial apes who like to follow bright shiny trendy things.
But for #3 (and some of #2), a coordinate-based client with WYSIWYG layouts could make life a lot easier for devs such that sacrificing fashion-chasing could become acceptable once the productivity boost is seen. As much as orgs are fad-chasers, they are also cheapskates, especially smaller orgs. If a client UI standard saves them money, they will sacrifice visual trendiness.
The current browser standards makes #3 apps a royal pain in the ass. There are frameworks to simplify UI stuff, but one has to get to know the framework first to use it timely and well. And flaky layout issues still pop up.