ACM Queue - Web Development
http://queue.acm.org/listing.cfm?item_topic=Web Development&qc_type=topics_list&filter=Web Development&page_title=Web Development&order=desc
Concurrency in WebAssembly: Experiments in the web and beyond
http://queue.acm.org/detail.cfm?id=3746173
Web Development2025年7月03日 15:20:30 GMTConrad Watt3746173When Is WebAssembly Going to Get DOM Support?: Or, how I learned to stop worrying and love glue code
http://queue.acm.org/detail.cfm?id=3746174
Web Development2025年7月02日 17:22:32 GMTDaniel Ehrenberg3746174WebAssembly: How Low Can a Bytecode Go?: New performance and capabilities
http://queue.acm.org/detail.cfm?id=3746172
Web Development2025年7月01日 18:58:46 GMTBen Titzer3746172WebAssembly: Yes, but for What?: The keys to a successful Wasm deployment
http://queue.acm.org/detail.cfm?id=3746171
Web Development2025年6月30日 17:46:53 GMTAndy Wingo3746171Why SRE Documents Matter: How documentation enables SRE teams to manage new and existing services
http://queue.acm.org/detail.cfm?id=3283589
SRE (site reliability engineering) is a job function, a mindset, and a set of engineering approaches for making web products and services run reliably. SREs operate at the intersection of software development and systems engineering to solve operational problems and engineer solutions to design, build, and run large-scale distributed systems scalably, reliably, and efficiently. A mature SRE team likely has well-defined bodies of documentation associated with many SRE functions. If you manage an SRE team or intend to start one, this article will help you understand the types of documents your team needs to write and why each type is needed, allowing you to plan for and prioritize documentation work along with other team projects.Web Development2018年10月04日 12:43:03 GMTShylaja Nukala, Vivek Rau3283589Research for Practice: Web Security and Mobile Web Computing: Expert-curated Guides to the Best of CS Research
http://queue.acm.org/detail.cfm?id=3005356
Our third installment of Research for Practice brings readings spanning programming languages, compilers, privacy, and the mobile web.
First, Jean Yang provides an overview of how to use information flow techniques to build programs that are secure by construction. As Yang writes, information flow is a conceptually simple "clean idea": the flow of sensitive information across program variables and control statements can be tracked to determine whether information may in fact leak. Making information flow practical is a major challenge, however. Instead of relying on programmers to track information flow, how can compilers and language runtimes be made to do the heavy lifting? How can application writers easily express their privacy policies and understand the implications of a given policy for the set of values that an application user may see? Yang's set of papers directly addresses these questions via a clever mix of techniques from compilers, systems, and language design. This focus on theory made practical is an excellent topic for RfP.
Second, Vijay Janapa Reddi and Yuhao Zhu provide an overview of the challenges for the future of the mobile web. Mobile represents a major frontier in personal computing, with extreme growth in adoption and data volume. Accordingly, Reddi and Zhu outline three major ongoing challenges in mobile web computing: responsiveness of resource loading, energy efficiency of computing devices, and making efficient use of data. In their citations, Reddi and Zhu draw on a set of techniques spanning browsers, programming languages, and data proxying to illustrate the opportunity for "cross-layer optimization" in addressing these challenges. Specifically, by redesigning core components of the web stack, such as caches and resource-fetching logic, systems operators can improve users' mobile web experience. This opportunity for co-design is not simply theoretical: Reddi and Zhu's third citation describes a mobile-optimized compression proxy that is already running in production at Google.Web Development2016年10月04日 10:45:08 GMTJean Yang, Vijay Janapa Reddi, Yuhao Zhu3005356React: Facebook’s Functional Turn on Writing JavaScript: A discussion with Pete Hunt, Paul O’Shannessy, Dave Smith and Terry Coatta
http://queue.acm.org/detail.cfm?id=2994373
One of the long-standing ironies of user-friendly JavaScript front ends is that building them typically involved trudging through the DOM (Document Object Model), hardly known for its friendliness to developers. But now developers have a way to avoid directly interacting with the DOM, thanks to Facebook's decision to open-source its React library for the construction of user interface components.Web Development2016年9月05日 16:50:30 GMTPete Hunt, Paul O'Shannessy, Dave Smith, Terry Coatta2994373Componentizing the Web: We may be on the cusp of a new revolution in web development.
http://queue.acm.org/detail.cfm?id=2844732
There is no task in software engineering today quite as herculean as web development.
A typical specification for a web application might read: The app must work across a wide
variety of browsers. It must run animations at 60 fps. It must be immediately responsive to touch. It must conform to a specific set of design principles and specs. It must work on just about every screen size imaginable, from TVs and 30-inch monitors to mobile phones and watch faces. It must be well-engineered and maintainable in the long term.Web Development2015年11月09日 14:53:03 GMTTaylor Savage2844732Beyond Page Objects: Testing Web Applications with State Objects: Use states to drive your tests
http://queue.acm.org/detail.cfm?id=2793039
End-to-end testing of Web applications typically involves tricky interactions with Web pages by means of a framework such as Selenium WebDriver. The recommended method for hiding such Web-page intricacies is to use page objects, but there are questions to answer first: Which page objects should you create when testing Web applications? What actions should you include in a page object? Which test scenarios should you specify, given your page objects?Web Development2015年6月16日 13:36:56 GMTArie van Deursen2793039Dismantling the Barriers to Entry: We have to choose to build a web that is accessible to everyone.
http://queue.acm.org/detail.cfm?id=2790378
A war is being waged in the world of web development. On one side is a vanguard of toolmakers and tool users, who thrive on the destruction of bad old ideas ("old," in this milieu, meaning anything that debuted on Hacker News more than a month ago) and raucous debates about transpilers and suchlike. On the other side is an increasingly vocal contingent of developers who claim that the head-spinning rate of innovation makes it impossible to stay up to date, and that the web is disintegrating into a jumble of hacks upon opinions, most of which are wrong, and all of which will have changed by the time hot-new-thing.js reaches version 1.0.0.Web Development2015年6月08日 15:24:48 GMTRich Harris2790378