19,968 research outputs found

    Economic Determinants of Driver's Behavior in Minas Gerais

    Get PDF
    The aim of the paper is to evaluate the behavior of drivers when they face a safe-traffic environment. Some studies suggest that the laws that demand auto makers to produce safer vehicles also stimulate their drivers to drive carelessly, since the cost of driving carefully decreases. Likewise, a safer traffic environment or less dangerous surroundings can stimulate drivers to drive more aggressively and less carefully. This study tries to test whether the undesirable behavior described by Peltzman (1975) is observed on the highways and roads of the State of Minas Gerais, Brazil. Estimates based on data found in the Brazilian Federal Road Police's accident report databank confirm drivers'' lack of attention in safer environments. The results suggest that careless behavior in traffic increases when safer conditions prevail.

    In the Age of Web: Typed Functional-First Programming Revisited

    Full text link
    Most programming languages were designed before the age of web. This matters because the web changes many assumptions that typed functional language designers take for granted. For example, programs do not run in a closed world, but must instead interact with (changing and likely unreliable) services and data sources, communication is often asynchronous or event-driven, and programs need to interoperate with untyped environments. In this paper, we present how the F# language and libraries face the challenges posed by the web. Technically, this comprises using type providers for integration with external information sources and for integration with untyped programming environments, using lightweight meta-programming for targeting JavaScript and computation expressions for writing asynchronous code. In this inquiry, the holistic perspective is more important than each of the features in isolation. We use a practical case study as a starting point and look at how F# language and libraries approach the challenges posed by the web. The specific lessons learned are perhaps less interesting than our attempt to uncover hidden assumptions that no longer hold in the age of web.Comment: In Proceedings ML/OCaml 2014, arXiv:1512.0143

    Lessons from the Long Tail: Analysing Unsafe Dependency Updates across Software Ecosystems

    Full text link
    A risk in adopting third-party dependencies into an application is their potential to serve as a doorway for malicious code to be injected (most often unknowingly). While many initiatives from both industry and research communities focus on the most critical dependencies (i.e., those most depended upon within the ecosystem), little is known about whether the rest of the ecosystem suffers the same fate. Our vision is to promote and establish safer practises throughout the ecosystem. To motivate our vision, in this paper, we present preliminary data based on three representative samples from a population of 88,416 pull requests (PRs) and identify unsafe dependency updates (i.e., any pull request that risks being unsafe during runtime), which clearly shows that unsafe dependency updates are not limited to highly impactful libraries. To draw attention to the long tail, we propose a research agenda comprising six key research questions that further explore how to safeguard against these unsafe activities. This includes developing best practises to address unsafe dependency updates not only in top-tier libraries but throughout the entire ecosystem

    Laser net - A concept for monitoring wingtip vortices on runways

    Get PDF
    Network of laser beams passes over runway to photodetectors on opposite side, magnitude of beam deflection indicates magnitude of density gradient encountered. Visual display of beam deflections affects go, no-go decision for takeoff and landing

    Bikesharing and Bicycle Safety

    Get PDF
    The growth of bikesharing in the United States has had a transformative impact on urban transportation. Major cities have established large bikesharing systems, including Boston, Chicago, Denver, Minneapolis-Saint Paul, New York City, Salt Lake City, the San Francisco Bay Area, Seattle, Washington DC, and others. These systems began operating as early as 2010, and no fatalities have occurred within the US as of this writing. However, three have happened in North America—two in Canada and one in Mexico. Bikesharing has some qualities that appear inherently unsafe for bicyclists. Most prominently, helmet usage is documented to be quite low in most regions. Bikesharing is also used by irregular bicyclists who are less familiar with the local terrain. In this study, researchers take a closer look at bikesharing safety from qualitative and quantitative perspectives. Through a series of four focus groups, they discussed bikesharing usage and safety with bikesharing members and nonmembers in the Bay Area. They further engaged experts nationwide from a variety of fields to evaluate their opinions and perspectives on bikesharing and safety. Finally, researchers conducted an analysis of bicycle and bikesharing activity data, as well as bicycle and bikesharing collisions to evaluate injury rates associated with bikesharing when compared with benchmarks of personal bicycling. The data analysis found that collision and injury rates for bikesharing are lower than previously computed rates for personal bicycling. Experts and focus group participants independently pointed to bikesharing rider behavior and bikesharing bicycle design as possible factors. In particular, bikesharing bicycles are generally designed in ways that promote stability and limited speeds, which mitigate the conditions that contribute to collisions. Data analysis also explored whether there was evidence of a “safety in numbers benefit” that resulted from bikesharing activity. However, no significant impact from bikesharing activity on broader bicycle collisions could be found within the regions in which they operate. Discussion and recommendations are presented in the conclusion

    THE IMPACT OF PROGRAMMING LANGUAGES ON THE SOFTWARE’S SECURITY

    Get PDF
    Security is usually defined as the ability of a system to protect itself against accidental or deliberate intrusion1. Ensuring integrity, confidentiality, availability, and accountability requirements even in the presence of a determined, malicious opponent is essential for computer security. Sensitive data has to be manipulated and consulted by authorized users only (integrity, confidentiality). Furthermore, the system should resist “denial of service” attacks that attempt to render it unusable (availability). Also the system has to ensure the inability to deny the ownership of prior actions (accountability).security
    • …
    corecore