Onward 2016 call

The Onward call for papers is on, with a submission deadline of April 1st this year. Please consider submitting your edgy PL ideas.

Onward! is looking for grand visions and new paradigms that could make a big difference in how we will one day build software. But Onward! is not looking for research-as-usual papers—conferences like OOPSLA are the place for that. Those conferences require rigorous validation such as theorems or empirical experiments, which are necessary for scientific progress, but which typically preclude discussion of early-stage ideas. Onward! papers must also supply some degree of validation because mere speculation is not a good basis for progress. However, Onward! accepts less rigorous methods of validation such as compelling arguments, exploratory implementations, and substantial examples. The use of worked-out examples to support new ideas is strongly encouraged.

Onward! is reaching out for constructive criticism of current software development technology and practices, and to present ideas that could change the realm of software development. Experienced researchers, graduate students, practitioners, and anyone else dissatisfied with the state of our art is encouraged to share insights about how to reform software development.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

what benefits?

I was wondering, what benefits can I expect if the language I program now is in a process of creation? Mostly, it is conceptually thought out and I already started coding. I've got some new ideas, some of which might look refreshing compared to today's technology, but do you think it would be better if I wait a bit until the language is completely coded out?

It really depends. An onward

It really depends. An onward paper can get you earlier feedback from the reviewers and (if accepted) the community. Turning your language design work into a coherent story can also help you focus and refine your ideas. On the other hand, not everyone is used to writing papers, and it might be a very inefficient way to go about it if that isn't your thing or you haven't don't it before. In that case, NOOL or FPW workshops at splash might be better bets.

best way

What is the best way for my new-vision live-projects?
I have 2 working full-tested new paradigm projects:
LiveComment is the missing link in the Evolution of the Web
Animation CPU (ACPU) Livecoding IDE & Enviroment. ACPU is self extensible system for working together.
ACPUL is untyped declarative minimalistic algorithmic language of ACPU.
Here is totally new vision, for example: ACPU is powered by light Erlang-style threads; ACPUL i18n builtin provide always-translatable beautify code, etc.
Onward! 2016 and LIVE 2016 is acceptable for both projects. I can show demo, but don't have papers until submision date of the Onward! 2016.

LIVE 2016 is probably a

LIVE 2016 is probably a better option: workshops are more flexible in what they can accept (demos are fine!), and the audience will be extremely focused if small. On the other hand, you don't get the fame and fortune that comes along with a conference paper /s.

Everything is in Europe this year, so location isn't a big deal.