forked from rakudo/rakudo
-
Notifications
You must be signed in to change notification settings - Fork 0
YAPC::EU 2010 workshop notes
jnthn edited this page Sep 13, 2010
·
7 revisions
Topics for discussion at YAPC::EU 2010:
Discussion ideas:
- Rakudo Star review – what was good, what can be improved for further releases?
- What are the major blockers to further adoption of Rakudo, and what can we do about them?
- Speed?
- Memory usage?
- Lack of modules?
- Missing features (which ones)?
- Possibility of backends in addition to parrot
- What options do we have? (e.g. JVM, v8, .Net CLR, others?)
- How much effort would it be?
- How much would be profit from it?
- What about risks?
- How would we arrange the NQP and Rakudo repos for backend specific stuff?
- How do we re-work our pir::foo into portable things?
- Providing rich, compile-time information in our syntax trees to enable optimizations, compile-time error detection and better error messages in general.
- How to activate more lurkers
Hacking ideas:
- Database access (DBDI or MiniDBI, or maybe converge them)
- Module infrastructure hacking (might have the advantage of offering some Perl 5 tasks, so that mostly uninitiated but willing perl 5 hackers
can help - semi-guided core hacking