Hi Jay, I understand you are not in agreement with certain architectural decisions. However, they are not "adding no value" to the FreeRDP project, they are quite useful. WinPR has greatly enhanced the portability and reusability of the code.
As for the "lots of complaints" and "developers being discouraged by this", give me a break. FreeRDP is not a Linux-centric project, it's an RDP-centric project, and it is designed to be as portable, flexible and modular as possible. Also, it is not a secret that the Microsoft Remote Desktop Protocol (RDP) is involves a lot of the Windows API being remoted, which is why the WinPR approach feels natural. You may not like it, but that's still how we're doing it, and we can't make everybody happy at once. Regarding xrdp-ng, it was only a temporary name. We've chosen to name the project FreeRDS for "FreeRDP Remote Desktop Services", and just like FreeRDP, it doesn't aim at being a Linux-centric project but a full blown cross-platform remote desktop services implementation. As for forking the project, I think we both know that we work at totally different speeds and that what Thinstuff and I need in the short term is fairly different from xrdp. If I were to make the major changes I've been doing in FreeRDS in xrdp you'd get a heart attack, as I know you wouldn't like most of it. No hard feelings, we're just working on our own project that fits our needs. It's something you're doing as well with NeutrinoRDP, the stabilization fork you're using with xrdp. It's not a competition, and I've never meant to insult you. I just need a project which is fairly different from what xrdp is. When I originally got started, I didn't have much imagination, so I just called it "xrdp-ng". We've finally decided to name it FreeRDS as it will have nothing to do with xrdp in the future as it's taking a totally different direction. You already hate the WinPR approach, and that's exactly what FreeRDS is using now along with as much of FreeRDP as possible. Is it really such a bad thing that it's a separate project? It's a long term investment for us, as in total it's somewhere between 6 months to a year of development effort to get the first usable release of FreeRDS with enough features to be interesting. We've got customers who need this, that's why we're working on it, and we want it for ourselves as well because of its potential. What do you think? Best regards, - Marc-Andre On Wed, Oct 23, 2013 at 12:26 AM, Jay Sorg <jay.s...@gmail.com> wrote: > I would like to express my concern too over the stability of FreeRDP. > It was much better a year ago. > > I'm concerned / confused about the future of FreeRDP. > It seems like there is too many restructuring / refactoring of the > source code that add no value. > All the documentation on > http://www.freerdp.com/api/ > is out of date. > > Lack of help is the problem, but who wants to help? > I hear a lot of complains about the windows'ish push. > WinPR / window command line parameters / a registry on Linux. > Talented Linux developers are discouraged by this. > > I'd have to say, I'm discouraged too. > > Another thing, with FreeRDP is such a bad state, why is this project > forking my project xrdp? > Why are you duplicating all the good work done on xrdp? > And why call it xrdp-ng? Are you suggesting you can do a better RDP > Linux server? > I find it quite insulting! > > I think there are some tough management issues that need to be addressed. > > Jay > ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
