2. Anything.

3. Why pattern matching is way cooler than car/cdr; why arc isn't a 100-year language; comparative study of macro systems; comparative study of module systems; implementation of a bootstrapping arc compiler; implementation of my pet lisp, chao, which is bootstrapped from arc and compiles to a (hopefully) portable IL... I have lots of ideas.

4. Summer break, since that's when I'm in Silicon Valley.

  1) U.S.
  2) Why care about Arc (esp. relative to Clojure)?
     Future direction(s)
     Lessons learned, and the applicability of those lessons to other languages
     Applications (e.g., Jarc on Google App Engine)
  3) Maybe... But I'm really more of a dilettante than a hardcore hacker.
  4) Spring is best, but it doesn't really matter

2. Code for Code. What tools facilitate the actual process of programming, and how are those tools themselves programmed? I don't mean this in too broad a sense, like any ol' API or library for frobnicating your database or querying some widget. It's more like "developer tools", though that doesn't sound very zazzy. In the sense I mean, it covers language implementations and compilers, which are certainly very interesting, but also many more things we use that no one seems to get nearly as excited over. REPL tools, syntax highlighters, debuggers, profilers, code introspection, pretty printing, documentation systems, software testing (randomized à la QuickCheck, unit testing, whatever), type systems, bug tracking, ... the list goes on. It starts getting increasingly tangential (e.g., if we count text editors, do we slippery-slope ourselves into counting entire operating systems?). You probably get the gist, though.

My interest is independent from Arc -- or any language, for that matter. I had to learn Vimscript to make a halfway decent highlighter, for instance. But it's the sort of thing I don't think we hear enough about, since we get used either to having these tools or just doing without. So, how do we make programs for programmers, and what kind should we make? How novel can we get?

3. Moot point per 1, but I could talk about some of the work I've done along the lines of 2.

Would it be possible to do some sort of webcast teleconference? That would make it a lot easier for some of us immobile/distant community members.

To answer the other questions:

2. Same as everyone else - learn more about alternate implementations of arc, with an eye towards doing one myself.

I haven't even managed to get out to local Meetup groups I'm signed up for, so probably nowhere. If there's a small miracle, I could probably go anywhere in the Silicon Valley, but anywhere else would take a bigger miracle. ^_^

2. What presentations would you like to hear?

Whatever there happen to be, really. I suppose I'm most interested in ways people think Arc could be improved from the ground up. Between Semi-Arc and the custom Arcs of aw and akkartik, there's been a lot of that kind of thinking around here lately.

3. Is there anything you would like to present?

Ooh, I'd probably do a talk about useful Arc design patterns I've found that seem to be too succinct to fit into the "build a macro for it" zone. I don't know how far that would take me, though. ^_^ So then I'd talk about various projects I'd done, I suppose.

4. Does it have to be any particular time of the year for you to be able to attend?

The time probably doesn't matter for me, just 'cause I'm unlikely to attend. Weekends would be more accommodating though. :-p

5. Any additional comments are welcome too, of course.

1. Silicon Valley.

2. I'm specifically interested in making Arc (or Lisp in general) a good option for doing everything that you'll ever need to do. I think making games is a good thing to aim for: it's worth doing in itself (I like games, and there's one old no-longer-being-developed game I'd really like to implement myself), and it implies handling graphics, audio, and keyboard/mouse input, plus respectable execution speed. Seems either one could focus on the Racket libraries (I've found them pretty good but somewhat buggy and slow), learn to use the Racket FFI, or use Arc as a skin over a completely new platform or language. I'd be pleased to hear of progress in these domains. Any other topics are good too, though.

3. I could talk about various things I've done in Arc, and the ad hoc libraries I've constructed in the process. In the category of math, I'll quickly mention primality testing, modular exponentiation and inversion, prime factorization, polynomial arithmetic and interpolation, multiple-variable polynomial arithmetic, and integer nth roots of arbitrarily large real and complex integers.

How about Sunday June 19th or Sunday June 26th? Maybe 6pm?

Anywhere in North America (US, Canada, Mexico). Maybe Europe...

2. What presentations would you like to hear?

I'd like to learn more about Lathe, Rainbow, Semi-Arc and it would be interesting to hear pg talk about lessons learned from Arc so far.

3. Is there anything you would like to present?

I'd be happy to talk about Jarc (why I did it, what I've learned, etc.)

4. Does it have to be any particular time of the year for you to be able to attend?

1. Anywhere; Europe is more convenient

2. What should the core language be; macro design; libraries; implementations and interopability

3. I hope I can think of something to say about rainbow

4. no

2. Anything!

3. I might like to talk about web-based REPLs, compiling Arc to JavaScript or some related topic.

4. Any time of year is fine, but can we do it over a weekend rather than during the week?

I am in favor of this type of stuff though - seems like it would be a good way to promote the community.

2. happy to see what happens

3. I'd probably give a useful talk (such as, calling libraries in other languages from Arc), and, if there's time, a fun talk (the extraordinary elegance of parsing by matching)