- About Scala
- In the Enterprise
- Scala Community
- Language Research
- In the Press
- The Scala Team
- Scala's Prehistory
- Contact Us
- Learning Scala
- Tour of Scala
- Scala API
- Setup & Getting Started
- Programming Guides
- Other Guides
- Code Examples
- Scala Developers
Re: Re: LAMP and the future of the eclipse plugin
This flame war has erupted many times in the past, but there is one
issue that is seldom brought up: what is EPFL/LAMP's position
regarding the development of the plugin? Most of the work was done by
Sean, when he was a member of the lab. As is usual in academia, he
went on to research other things elsewhere. His continued
participation in the project is commendable*, but it is unreasonable
to expect the same level of commitment going forward.
If LAMP deems the development of the plugin to be important, it should
staff it adequately with new people. Resources are limited, of course,
but the issue boils down to priorities. Browsing this list and the
commit log we see that quite a few initiatives led by LAMP researches
are underway. This suggests that the lab finds a host of issues to
have a higher priority than the Eclipse Plugin. Given the
sophistication of the language and complexity of the compiler, I don't
think a 100% "community-led" model would have a very good chance of
success (where success could be defined as "having a working plugin,
with a feature set close to JDT").
I understand that, in an academic setting, defining priorities and
allocating people are different processes than in the commercial
world. I also don't mean to disparage the great work done with the
language; no one would be interested in a plugin for a language that
wasn't compelling. But I would really like to see more attention paid
to the plugin from EPFL.
* There are other Scala language features and libraries that had no such luck.
Just my R$0,02
Rafael de F. Ferreira.
On Tue, Feb 10, 2009 at 12:37 AM, Miles Sabin wrote:
> Sean, you're useful to to project if you're still willing and able to
> make concrete contributions. Code would be nice (there are plenty of
> open bugs in areas where you're the best authority) and documentation
> would be wonderful (the scalac-IDE interface and incremental AST
> maintenance, hint, hint).
> But if you're not going to do that and instead just respond negatively
> to efforts like the one David is making then it might be helpful for
> you to take a little break, at least until you're able to adopt a
> slightly more detached attitude to the project.
> Miles Sabin
> tel: +44 (0)1273 720 779
> mobile: +44 (0)7813 944 528
> skype: milessabin