Break from the future: Hold the new stuff and fix the web first

Hiatus is not a dirty word. Crevice is a dirty word, but hiatus isn't

Peter-Paul Koch, author of The Mobile Web Handbook, published a piece this summer entitled "Stop Pushing the Web Forward".

Koch argued that the relentless pace of new features on the web isn't helping it and that we – developers, along with browser makers – would do well to put on the brakes for a few months.

It's not that Koch is opposed to progress or new features (though he does decry the trend toward slavishly emulating every new feature of platform natives apps), just that perhaps the pace is a bit fast. So fast, in fact, that developers and browser makers are just driving the web forward – there's no direction beyond that.

In other words, in a world where progress is the only goal, Koch wants to talk about where the web is going and why. He thinks it would be nice to freeze the development of new browser features for a while, giving developers more time to understand and use the features the web already has and that in turn would give us a better idea of where the web is lacking – compared to what? – and how to fix it.

Predictably, it earned a backlash. Questioning one of the most fundamental tenants of modern existence – progress is good – gets you some vehement responses.

In this case, though, while Koch's suggestion is obviously never going to happen, it has at least inspired some rational discussion as well, especially with regard to the latest trend in new features for the web – emulating the features that platform-native applications enjoy. This means things like APIs that let sites access device hardware or effects like the proposed Navigation Transitions spec, which makes page-to-page navigation smoother and more like what happens in native mobile applications.

But does the web need these things? "We’re pushing the web forward to emulate native more and more," writes Koch. "But we can't out-native native."

Indeed, native apps will by definition always be ahead of those emulating their features. The quest to make websites behave more like native applications is thus doomed to perpetual failure.

Google's Jake Archibald countered Koch's argument against native emulation, writing: "We should add features using evidence, and native is a great source of evidence."

Archibald cited some specific examples: "Through native, we've seen users benefit from push messaging, offline data access, GPS, speedy payments. Through native we've also seen store management harm openness, packaging hurt linking, and up-front permissioning harm security and privacy."

Prior to native mobile platforms, the web was often measured against competing technologies like Flash, which provided the impetus for native audio and video tags taken for granted today.

Broader topics

Other stories you might like

  • AI tool finds hundreds of genes related to human motor neuron disease

    Breakthrough could lead to development of drugs to target illness

    A machine-learning algorithm has helped scientists find 690 human genes associated with a higher risk of developing motor neuron disease, according to research published in Cell this week.

    Neuronal cells in the central nervous system and brain break down and die in people with motor neuron disease, like amyotrophic lateral sclerosis (ALS) more commonly known as Lou Gehrig's disease, named after the baseball player who developed it. They lose control over their bodies, and as the disease progresses patients become completely paralyzed. There is currently no verified cure for ALS.

    Motor neuron disease typically affects people in old age and its causes are unknown. Johnathan Cooper-Knock, a clinical lecturer at the University of Sheffield in England and leader of Project MinE, an ambitious effort to perform whole genome sequencing of ALS, believes that understanding how genes affect cellular function could help scientists develop new drugs to treat the disease.

    Continue reading
  • Need to prioritize security bug patches? Don't forget to scan Twitter as well as use CVSS scores

    Exploit, vulnerability discussion online can offer useful signals

    Organizations looking to minimize exposure to exploitable software should scan Twitter for mentions of security bugs as well as use the Common Vulnerability Scoring System or CVSS, Kenna Security argues.

    Better still is prioritizing the repair of vulnerabilities for which exploit code is available, if that information is known.

    CVSS is a framework for rating the severity of software vulnerabilities (identified using CVE, or Common Vulnerability Enumeration, numbers), on a scale from 1 (least severe) to 10 (most severe). It's overseen by, a US-based, non-profit computer security organization.

    Continue reading
  • Sniff those Ukrainian emails a little more carefully, advises Uncle Sam in wake of Belarusian digital vandalism

    NotPetya started over there, don't forget

    US companies should be on the lookout for security nasties from Ukrainian partners following the digital graffiti and malware attack launched against Ukraine by Belarus, the CISA has warned.

    In a statement issued on Tuesday, the Cybersecurity and Infrastructure Security Agency said it "strongly urges leaders and network defenders to be on alert for malicious cyber activity," having issued a checklist [PDF] of recommended actions to take.

    "If working with Ukrainian organizations, take extra care to monitor, inspect, and isolate traffic from those organizations; closely review access controls for that traffic," added CISA, which also advised reviewing backups and disaster recovery drills.

    Continue reading

Biting the hand that feeds IT © 1998–2022