dtrace.org/blogs/bmc/2004/07/08/whither-usenix-part-ii
Preview meta tags from the dtrace.org website.
Linked Hostnames
7- 5 links towww.usenix.org
- 3 links todtrace.org
- 1 link tobcantrill.dtrace.org
- 1 link tobsky.app
- 1 link toen.wikipedia.org
- 1 link tohistory.allthingsdistributed.com
- 1 link towww.linkedin.com
General Meta Tags
19- titleWhither USENIX? (Part II) | The Observation Deck
- titleHome
- titleMenu
- titleLIGHT
- titleDARK
Open Graph Meta Tags
13- og:titleWhither USENIX? (Part II) | The Observation Deck
- og:site_name
- og:description
- og:localeen-us
- og:typearticle
Twitter Meta Tags
5- twitter:titleWhither USENIX? (Part II) | The Observation Deck
- twitter:description
- twitter:cardsummary
- twitter:titleWhither USENIX? (Part II)
- twitter:descriptionWerner Vogels, a member of the USENIX ‘04 Program Committee, has written very thoughtful responses to some of my observations. And it’s clear that Werner and I see the same problem: there is insufficient industrial/academic cooperation in computer science systems research – and the lack of cooperation is to the detriment of both groups. That said, it’s clear that there are some different perspectives as to how to address the problem. A common sentiment that I’m seeing in the comments is that it is up to industry to keep USENIX relevant (in Werner’s words, “industry will need to be more pro-active in making researchers aware of what the problems are that they need to solve”). I don’t entirely agree; in my opinion, the responsibility for keeping USENIX relevant doesn’t lie exclusively with industry – and it doesn’t lie exclusively with academia, either. Rather, the responsibility lies with USENIX itself, for it is the mission of USENIX to encourage research with a “practical bias.” As such, it is up to USENIX to assemble a Program Committee that will reflect this mission, and it is up to both academia and industry to participate as requested. This means that USENIX cannot simply wait for volunteers from industry to materialize – USENIX must seek out people in industry who understand both the academic and the industrial sides of systems research, and they must convince these people to work on a Program Committee. Now, I know that this has happened in the past – and frankly I thought that the USENIX ‘04 Program Committee was a step in the right direction: where USENIX ‘03 had four (of sixteen) members from industry, USENIX ‘04 had six (of seventeen). But unfortunately, USENIX ‘05 seems to be a marked decline in industry participation, even from USENIX ‘03: the number from industry has dropped back to four (of eighteen). Worse, all four are from industry labs; where both USENIX ‘03 and USENIX ‘04 had at least one product-oriented member from industry, USENIX ‘05 has none.
Item Prop Meta Tags
2- nameWhither USENIX? (Part II) | The Observation Deck
- description
Link Tags
10- apple-touch-icon/icons/apple-touch-icon.png
- canonicalhttps://bcantrill.dtrace.org/2004/07/08/whither-usenix-part-ii/
- icon/icons/favicon-32x32.png
- icon/icons/favicon-16x16.png
- icon/icons/favicon.svg
Website Locales
1en-us
https://bcantrill.dtrace.org/2004/07/08/whither-usenix-part-ii/
Links
13- http://dtrace.org/blogs/bmc/2004/07/06/whither-usenix
- http://history.allthingsdistributed.com/archives/000482.html
- http://www.usenix.org/about
- http://www.usenix.org/about/board.html
- http://www.usenix.org/events/usenix03