| 1 |
On 21.7.2010 19.55, Fabian Groffen wrote: |
| 2 |
> On 21-07-2010 19:41:19 +0300, Petteri Räty wrote: |
| 3 |
>> On 07/21/2010 06:59 PM, Luca Barbato wrote: |
| 4 |
>>> Anyway it's not so related to the project at hand. Still I wonder why |
| 5 |
>>> not using a quick language (e.g. ruby, python) for this project if the |
| 6 |
>>> aim is to have a prototype. C and C++ are useful if you plan to optimize |
| 7 |
>>> a lot. |
| 8 |
>> |
| 9 |
>> Anltr has two mature backends as far as I know: C and Java. My guess is |
| 10 |
>> that most of the people wouldn't approve the latter. |
| 11 |
> |
| 12 |
> If you're prototyping anyway, I prefer Java over Python or Ruby, since |
| 13 |
> Java is much more close to C in semantics. |
| 14 |
> |
| 15 |
> |
| 16 |
|
| 17 |
One of the goals of the second half of the project is to prototype how |
| 18 |
the integration with package managers will work. Ideally we would like |
| 19 |
the project to be usable by all package managers and that's kind of hard |
| 20 |
to do for paludis with Ruby or Python. |
| 21 |
|
| 22 |
Regards, |
| 23 |
Petteri |
Archives