I have noticed there are somewere between 7 to 12 projects that are working on the same suff that you guys do. Has anyone contact those people and try to consolidate the effort??
The Wolf
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would then have to say that it was closer to 8 and 13 before we merged, since Common C++ was starting to develop threading as well; in fact this is the one area that Common C++ and APE overlapped, and it made sense to continue the APE threading simply because it was much further along and ported to other platforms. However, I see nothing wrong in having diversity. I would say this, however, that APE with Common C++ merged is a much broader and more appealing solution than APE alone, and that this was always a concern that APE would be taken for just "another" threading class library.
I believe APE did a good job of abstracting many system services, and not just threading alone. It does have overap with other threading libraries, with things like Sockets++, etc, but all of these look at only one aspect where APE (and now Common C++) tries to address and fascilitate all aspects of C++ application development in a fully portable manner.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would then have to say that it was closer to 8 and 13 before we merged, since Common C++ was starting to develop threading as well; in fact this is the one area that Common C++ and APE overlapped, and it made sense to continue the APE threading simply because it was much further along and ported to other platforms. However, I see nothing wrong in having diversity. I would say this, however, that APE with Common C++ merged is a much broader and more appealing solution than APE alone, and that this was always a concern that APE would be taken for just "another" threading class library.
I believe APE did a good job of abstracting many system services, and not just threading alone. It does have overap with other threading libraries, with things like Sockets++, etc, but all of these look at only one aspect where APE (and now Common C++) tries to address and fascilitate all aspects of C++ application development in a fully portable manner.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems this project is one of the biggest when it comes to the head count, at least from what I have seen.
I think it would be faster develpmanet to get more people merged into this project.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have noticed there are somewere between 7 to 12 projects that are working on the same suff that you guys do. Has anyone contact those people and try to consolidate the effort??
The Wolf
I would then have to say that it was closer to 8 and 13 before we merged, since Common C++ was starting to develop threading as well; in fact this is the one area that Common C++ and APE overlapped, and it made sense to continue the APE threading simply because it was much further along and ported to other platforms. However, I see nothing wrong in having diversity. I would say this, however, that APE with Common C++ merged is a much broader and more appealing solution than APE alone, and that this was always a concern that APE would be taken for just "another" threading class library.
I believe APE did a good job of abstracting many system services, and not just threading alone. It does have overap with other threading libraries, with things like Sockets++, etc, but all of these look at only one aspect where APE (and now Common C++) tries to address and fascilitate all aspects of C++ application development in a fully portable manner.
I would then have to say that it was closer to 8 and 13 before we merged, since Common C++ was starting to develop threading as well; in fact this is the one area that Common C++ and APE overlapped, and it made sense to continue the APE threading simply because it was much further along and ported to other platforms. However, I see nothing wrong in having diversity. I would say this, however, that APE with Common C++ merged is a much broader and more appealing solution than APE alone, and that this was always a concern that APE would be taken for just "another" threading class library.
I believe APE did a good job of abstracting many system services, and not just threading alone. It does have overap with other threading libraries, with things like Sockets++, etc, but all of these look at only one aspect where APE (and now Common C++) tries to address and fascilitate all aspects of C++ application development in a fully portable manner.
It seems this project is one of the biggest when it comes to the head count, at least from what I have seen.
I think it would be faster develpmanet to get more people merged into this project.
What projects do you suggest we look at? Is there a project in particular that would be complementary?