<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>ACM Queue - All Queue Content</title>
    <link>http://queue.acm.org/Curmudgeon</link>
    <description />
    <item>
      <title>Garbage Collection as a Joint Venture</title>
      <link>http://queue.acm.org/detail.cfm?ref=rss&amp;id=3325132</link>
      <description>Cross-component tracing is a way to solve the problem of reference cycles across component boundaries. This problem appears as soon as components can form arbitrary object graphs with nontrivial ownership across API boundaries. An incremental version of CCT is implemented in V8 and Blink, enabling effective and efficient reclamation of memory in a safe manner.</description>
      <pubDate>Tue, 09 Apr 2019 15:33:59 GMT</pubDate>
      <guid isPermaLink="false">3325132</guid>
    </item>
    <item>
      <title>How to Create a Great Team Culture (and Why It Matters)</title>
      <link>http://queue.acm.org/detail.cfm?ref=rss&amp;id=3323993</link>
      <description>As leader of the team, you have significant influence over your team's culture. You can institute policies and procedures that help make your team happy and productive, monitor team successes, and continually improve the team. Another important part of team culture, however, is helping people feel they are a part of creating it. How can you expand the job of creating a culture to other team members?</description>
      <pubDate>Wed, 03 Apr 2019 11:20:49 GMT</pubDate>
      <guid isPermaLink="false">3323993</guid>
    </item>
    <item>
      <title>Online Event Processing</title>
      <link>http://queue.acm.org/detail.cfm?ref=rss&amp;id=3321612</link>
      <description>Support for distributed transactions across heterogeneous storage technologies is either nonexistent or suffers from poor operational and performance characteristics. In contrast, OLEP is increasingly used to provide good performance and strong consistency guarantees in such settings. In data systems it is very common for logs to be used as internal implementation details. The OLEP approach is different: it uses event logs, rather than transactions, as the primary application programming model for data management. Traditional databases are still used, but their writes come from a log rather than directly from the application. The use of OLEP is not simply pragmatism on the part of developers, but rather it offers a number of advantages. Consequently, OLEP is expected to be increasingly used to provide strong consistency in large-scale systems that use heterogeneous storage technologies.</description>
      <pubDate>Sun, 24 Mar 2019 16:42:54 GMT</pubDate>
      <guid isPermaLink="false">3321612</guid>
    </item>
    <item>
      <title>The Worst Idea of All Time</title>
      <link>http://queue.acm.org/detail.cfm?ref=rss&amp;id=3320268</link>
      <description>In February 2004, with the other members of the Queue editorial board, I was at our monthly in-person dinner meeting, where we gather to come up with interesting discussion topics that will result in practitioner-oriented articles (and the best authors to write them) for publication in Queue. It was only our second year in business, and although we had published some successful and widely read articles, Queue still had no regular columnists. I was initially invited to board meetings by another editorial board member, Eric Allman, and had written a couple of articles for the publication. I was also co-authoring my first book but had never been a columnist. Although the concept seemed appealing at the time, perhaps due to too much wine with dinner, I was at a loss on how to actually make it work.</description>
      <pubDate>Mon, 18 Mar 2019 12:12:18 GMT</pubDate>
      <guid isPermaLink="false">3320268</guid>
    </item>
    <item>
      <title>Net Neutrality: Unexpected Solution to Blockchain Scaling</title>
      <link>http://queue.acm.org/detail.cfm?ref=rss&amp;id=3319534</link>
      <description>Provably neutral clouds are undoubtedly a viable solution to blockchain scaling. By optimizing the transport layer, not only can the throughput be fundamentally scaled up, but the latency could be dramatically reduced. Indeed, the latency distribution in today's data centers is already biased toward microsecond timescales for most of the flows, with millisecond timescales residing only at the tail of the distribution. There is no reason why a BDN point of presence would not be able to achieve a similar performance. Adding dedicated optical infrastructure among such BDN points of presence would further alleviate throughput and reduce latency, creating the backbone of an advanced BDN. The key to this vision, however, lies in establishing trust by the blockchain ecosystem into the underlying networking infrastructure. This, in turn, is achieved by decoupling authority from infrastructure via a provably neutral network design.</description>
      <pubDate>Tue, 12 Mar 2019 13:26:00 GMT</pubDate>
      <guid isPermaLink="false">3319534</guid>
    </item>
    <item>
      <title>SageDB and NetAccel</title>
      <link>http://queue.acm.org/detail.cfm?ref=rss&amp;id=3317289</link>
      <description>The CIDR (Conference on Innovative Data Systems Research) runs once every two years, and luckily for us 2019 is one of those years. I've selected two papers from this year's conference that highlight bold and exciting directions for data systems.</description>
      <pubDate>Thu, 28 Feb 2019 14:04:58 GMT</pubDate>
      <guid isPermaLink="false">3317289</guid>
    </item>
  </channel>
</rss>

