Re: Current state of Apache Commons Math and Geometry

Gary Gregory <[email protected]>
Newsgroups gmane.comp.jakarta.commons.devel
Message-ID <CACZkXPzM7BY3oDS+Gc4CZfV9kGS=P1eMf4HFU7xNuG=oDMoDDg@mail.gmail.com>
But Commons Geometry _is_ broken up in 6 smaller focused components. It
seems to me that CG should or could welcome new components, especially if
they come with a maintainer. Maybe Alex Herbert can shine a light here.

Gary

On Thu, Feb 19, 2026, 08:28 Elliotte Rusty Harold <[email protected]>
wrote:

> On Thu, Feb 19, 2026 at 8:32 AM Johann Sorel via dev
> <[email protected]> wrote:
>  part :
> >
> https://github.com/apache/sis/tree/geoapi-4.0/incubator/src/org.apache.sis.geometry/main/org/apache/sis/geometries
> >
> > Apache-commons-geometry contains a single kind of geometry :
> > Constructive Solid Geometry. which is really nice.
> > But what we are making is more like JavaTopologySuite, Esri-geometry,
> > SVG but with 3D (and more) support for PLY, GLTF, GPU...
>
> I'm not familiar with the math you're using, but it sounds like it's
> quite different from what's in commons geometry now and has limited
> overlap. If that's true, then I strongly recommend you make your own
> more targeted library and artifact rather than trying to shoehorn it
> into another library because the name sounds similar. Smaller, more
> focused libraries speed up development and enable you to build exactly
> what you need without trying to get consensus with another team.
> Frankenlibraries that include everything and the kitchen sink are
> already a problem for Apache Commons. I think you'll be much happier
> with your own library that you control and can tailor to your
> project's needs.
>
> --
> Elliotte Rusty Harold
> [email protected]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.