-1 Potential compatibility issues which are related to user specific code (services, jobs). Potential vulnerabilities which are a problem because we can't manage the Guava release cycle. Arguable approach with unnecessary immutability and unmanageable GC pressure. It's too hard to manage the *reasonable* usage of this library.
On Tue, Sep 7, 2021 at 6:31 PM Alexander Polovtcev <alexpolovt...@gmail.com> wrote: > > +1 > We already have some utility methods that are copy-pasted from Guava, which > can be removed, and I believe that *reasonable* usage of this library can > benefit the code and the product quality. > > On Tue, Sep 7, 2021 at 6:27 PM Alexander Polovtcev <alexpolovt...@gmail.com> > wrote: > > > Dear Igniters, > > > > In this thread > > <https://lists.apache.org/thread.html/r4120a03a2bf32098e54e21ae02e509b0d68f413bc7cc1f8f6d85c93d%40%3Cdev.ignite.apache.org%3E> > > we've been discussing the problems and opportunities of using Guava > > <https://github.com/google/guava> in Ignite 3. We have agreed that it > > should be added as a shaded dependency, but we haven't decided whether to > > allow using Guava methods in the Ignite codebase or not. Therefore I would > > like to propose a vote: > > > > [+1 Allow]: allow using Guava methods, if justified. > > [-1 Prohibit]: prohibit using all Guava methods. > > > > The voting will commence on Monday, September 13th at 9:00 UTC. Also feel > > free to express your opinion in the original discussion thread. > > > > -- > > With regards, > > Aleksandr Polovtcev > > > > > -- > With regards, > Aleksandr Polovtcev
