Esug-list mailing list
9 February, 2017
21 December, 2016
Eliot gave a terrific presentation about the current state of the community and what we might do to improve it.
Evelyn (Lin) Ostrom
Eight principles for managing a commons
- Clearly defined boundaries
- Proportional equivalence between benefits and costs
- Collective choice arrangements
- Graduated sanctions
- Fast and fair conflict resolutions
- Local autonomy
- Polycentric governance
Editorial: by Ron Teitelbaum follows
Eliot gave the presentation to help get the discussion going (it’s not the start of the conversation either, there are earlier efforts like the Pharo Consortium) this Article is part of that discussion.
My take on the conversation is that there are really two aspects of what Eliot is discussing.
First that some sort of economic organization that helps Smalltalk is needed and that the organization should be used to help both programmers and customers. It seems to me that a Smalltalk Guild could be set up to do just that. It would be a place for customers to find certified developers with access to a group of people (other guild members) that can solve difficult problems if they get stuck. It could also be a place where members who make over a certain amount of money could get proportional benefits. As a developer. I would probably join such a guild and as a customer, I would love to have a place to go which could help me solve some programming issues.
Second that we need to have better visibility, coordination, and cooperation. The cost of coordination using technology is falling fast. Having a site that pairs tasks with developers, shows developers guild certifications, allows for customer and developer ratings and comments, highlights training materials and growth paths, and generally allows communities to form and disband around specific areas funded by companies or the guild itself would fundamentally change how we organize and grow the community.
To illustrate let’s say we form a Smalltalk Guild. Members pay $10 a year to join + %10 of what they make on jobs they get through the Guild Jobs. Companies can also join the guild and pay $100 per year and pay %10 in addition to what they pay for a job if they hire a Guild member to do the work. (These are just made up figures I have no idea if they would actually work and some study would be needed to figure that out). As a group, the Guild can provide Training for new members, create certification levels and growth plans. The incentive for the group is that as members grow and make more money everyone benefits, there is an incentive to make sure people are qualified, can do the work, and actually get work instead of doing nothing (like java programming). Users that contribute over 10k to the guild (earn 90K) can get benefits if they are out of work, or maybe healthcare on a group plan, some form of compensation which of course would be less than they contribute + generate in customer fees and would be decided by the Guild as Eliot says 0.N/X. This gives the best guild members an incentive to stay with the guild and to feel like the guild is helping them provide some basic needs and it allows the guild to acknowledge the contributions the member is putting in to help the entire group. The money could also be used to benefit the Guild. To pay for someone’s training or certification, to increase visibility, to look for donors, find new customers, invest in new training materials, new conferences, courses, or even develop technology like the VM or application frameworks based on the group’s collective choices.
7th Workshop on the Evaluation and Usability of Programming Languages and Tools (PLATEAU)
Co-located with SPLASH 2016
CALL FOR PAPERS
Programming languages exist to enable programmers to develop software effectively. But how efficiently programmers can write software depends on the usability of the languages and tools that they develop with. The aim of this workshop is to discuss methods, metrics and techniques for evaluating the usability of languages and language tools. The supposed benefits of such languages and tools cover a large space, including making programs easier to read, write, and maintain; allowing programmers to write more flexible and powerful programs; and restricting programs to make them more safe and secure.
PLATEAU gathers the intersection of researchers in the programming language, programming tool, and human-computer interaction communities to share their research and discuss the future of evaluation and usability of programming languages and tools.
Some particular areas of interest are:
- empirical studies of programming languages
- methodologies and philosophies behind language and tool evaluation
- software design metrics and their relations to the underlying language
- user studies of language features and software engineering tools
- visual techniques for understanding programming languages
- critical comparisons of programming paradigms
- tools to support evaluating programming languages
- psychology of programming
- domain specific language (e.g. database languages, security/privacy languages, architecture description languages) usability and evaluation
PLATEAU encourages submissions of three types of papers:
Research and position papers: We encourage papers that describe work-in-progress or recently completed work based on the themes and goals of the workshop or related topics, report on experiences gained, question accepted wisdom, raise challenging open problems, or propose speculative new approaches. We will accept two types of papers: research papers up to 8 pages in length; and position papers up to 2 pages in length.
Hypotheses papers: Hypotheses papers explicitly identify beliefs of the research community or software industry about how a programming language, programming language feature, or programming language tool affects programming practice. Hypotheses can be collected from mailing lists, blog posts, paper introductions, developer forums, or interviews. Papers should clearly document the source(s) of each hypothesis and discuss the importance, use, and relevance of the hypotheses on research or practice. In addition, we invite language designers to share some of the usability reasoning that influenced their work. These will serve as an important first step in advancing our understanding of how language design supports programmers.Papers may also, but are not required to, review evidence for or against the hypotheses identified. Hypotheses papers can be up to 4 pages in length.
Submission site: PLATEAU papers should be submitted via HotCRP.
Format: Submissions should use the SIGPLAN Proceedings Format (http://www.sigplan.org/Resources/Author/), 10 point font. Note that by default the SIGPLAN Proceedings Format produces papers in 9 point font. If you are formatting your paper using LaTeX, you will need to set the 10pt option in the \documentclass command. If you are formatting your paper using Word, you may wish to use the provided Word template that supports this font size. Please include page numbers in your submission. Setting the preprint option in the LaTeX \documentclass command generates page numbers. Please also ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes are legible.
All types of papers will be published in the ACM Digital Library at the authors’ discretion.
University of Cambridge
Cambridge, United Kingdom
Submission deadline: August 1, 2016
Kelly Blincoe, Auckland University of Technology, New Zealand
Jeff Carver, University of Alabama, USA
Kathi Fisler, Worcester Polytechnic Institute, USA
Tudor Gîrba, Independent, Switzerland
Stefan Hanenberg, University of Duisburg-Essen, Germany
Andrew Ko, University of Washington, USA
Brad Myers, Carnegie Mellon University, USA
Peter-Michael Osera, Grinnell College, USA
Janet Siegmund, University of Passau, Germany
Jeremy Singer, University of Glasgow, United Kingdom
Emma Söderberg, Google, USA
Andreas Stefik, University of Nevada, Las Vegas, USA
Ian Utting, University of Kent, United Kingdom
Philip Wadler, University of Edinburgh, United Kingdom
Craig Anslow, Middlesex University, UK
Thomas LaToza, George Mason University, USA
Joshua Sunshine, Carnegie Mellon University, USA
17 May, 2016
Mario Wolczko writes:
In early 2015 I was honored to be invited to develop and present a graduate course on Virtual Machines at UC Berkeley. The result is CS294-113: Virtual Machines and Managed Runtimes, which was presented in the Fall of 2015.
This page contains the materials from that course. All materials are Copyright © Oracle and Mario Wolczko, 2015-6, except as noted. The materials can be used non-commercially under the following Creative Commons license:
I’d like to express my thanks to the following:
- Patrick Li, my T.A. for the course. Patrick devised the Feeny language used in the exercises, wrote the Lab exercises and the model answers, and did all the grading,
- Prof. Jonathan Bachrach for the invitation to give the course,
- The guest speakers (in order of appearance): Peter Deutsch, Allan Schiffman, David Ungar, Cliff Click, Lars Bak, Carl Friedrich Bolz, Thomas Würthinger and Michael Van De Vanter,
- My management at Oracle Labs for supporting this effort,
- Michael Haupt for sharing his VM course material,
- Christian Wimmer for assistance with Truffle, and
- All the students who participated, for their patience, enthusiasm, attention, questions, efforts and feedback.
14 May, 2016
Excellent Description of Sista! Nice job Eliot and Clément!
12 May, 2016
Chris Muller posted:
The mission-control app I’ve been working on this year appeared in a special episode of CBBC Newsround yesterday!
The segment about Reserve Protection Agency with several screenshots of the app begins at time index 9:40 and runs until 12:25. I recommend watching the entire episode, though, it’s a worthwhile message.
No one will know it is powered by Squeak but that’s okay, the important message is the one about the danger faced by rhinos as a species.