> Sure. I'll give it a try. My version of a library definition is:
I would like to add that a GOOD library that will be LOVED by the community:
* Should have NO transient dependencies
* Should have a clear and minimalistic API
* Should have implementation code in a separate package from the
Hi,
Please use Eugen. That is my given name. Stan is my family name.
La 11.06.2020 11:27, Tellier Benoit a scris:
> On 10/06/2020 15:19, Eugen Stan wrote:
>> I'm mostly referring to libraries. Having a library bring a dependency
>> like scala is a no-no on my part.
>>
>> Ideally the lower parts
On 10/06/2020 15:19, Eugen Stan wrote:
> I'm mostly referring to libraries. Having a library bring a dependency
> like scala is a no-no on my part.
>
> Ideally the lower parts of James should not bring any dependencies.
> Guava is also big and I would like to see that gone as well.
>
> [...]
Hi,
I tried to reply to your message, see below.
On Wed, 2020-06-10 at 11:19 +0300, Eugen Stan wrote:
> Hello Matthieu,
>
> La 09.06.2020 15:46, Matthieu Baechler a scris:
> > My experience with Scala is the opposite: you can write code that
> > express the problem you are solving instead of a
Hello Matthieu,
La 09.06.2020 15:46, Matthieu Baechler a scris:
> My experience with Scala is the opposite: you can write code that
> express the problem you are solving instead of a lot of boiler plate
> that divert the reader from the intent.
>
> I'm not saying Scala is perfect but I would not
Hi,
I'm not really skilled in Scala.
But I don't think that it's a mistake to go ahead for such a language, I
will not enumerate the advantages of Scala Vs Java.
One point is that James can attract another population of developers.
In order to don't lose none-Scala developers, I think it will be
Hi Eugen,
On Tue, 2020-06-09 at 00:52 +0300, Eugen Stan wrote:
> I'm also against adding more complexity in James.
I guess we all are.
> My arguments against adding scala to James are:
>
> - It adds another language that is more complex that Java - operator
> overloading, much more dense
Hi Matthieu,
> I'm very happy having people to give their opinions, it means, to me,
> we have some kind of community.
Yes, I agree. It must remain respectful and cordial, though. I hope I was able
to do that.
>> I totally agree with the point: one should not confuse “complex” with
>>
Hi David,
I'm very happy having people to give their opinions, it means, to me,
we have some kind of community.
On Tue, 2020-06-09 at 06:22 +0900, David Leangen wrote:
> > > My point is that (1) the “core” should remain in Java alone, not
> > > because Java is so awesome but simply just to avoid
I'm also against adding more complexity in James.
My arguments against adding scala to James are:
- It adds another language that is more complex that Java - operator
overloading, much more dense language (easier to write, harder to read).
- Extra build and runtime dependencies. Scala is
>> My point is that (1) the “core” should remain in Java alone, not
>> because Java is so awesome but simply just to avoid unnecessary
>> complexity,
>
> Well, one should not confuse `complex` with `familiar`. Java is
> `familiar` to many people but is way more complex than Scala in many
>
On Mon, 2020-06-08 at 21:28 +0900, David Leangen wrote:
> > > […] it's a good occasion to gather people opinions about that and
> > > move forward with James as a project.
> > >
> > > So, what do you think ?
>
> My 2 yen:
>
> My impression of James is that it is already much too
>
>> […] it's a good occasion to gather people opinions about that and move
>> forward with James as a project.
>>
>> So, what do you think ?
My 2 yen:
My impression of James is that it is already much too overcomplicated. It seems
to me that a major refactoring ought to take place at some
To be honest, given the exchange on the pull request and the content of
the ADR I came to this formulation
(https://github.com/linagora/james-project/pull/3309#issuecomment-620957935)
'that I am not hostile to it', but would also like a broader feedback
(thanks for asking for it!).
To give my own
Hi,
Sorry for the previous mail that I sent by error.
We specified that we wanted to be polyglot-friendly in James and also
that for the current people writing code we would start using Scala in
some specific context.
It's what is written in adr 24 here :
https://github.com/linagora/james-project/pull/3309,
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
16 matches
Mail list logo