[FreeNX-kNX] Compiling NX1.5.0 on amd64

[Kurt Pfeifle]

On Thursday 29 September 2005 18:02, Xiong Jiang wrote:
 
> I complained because it's not easy for me to find 
> the information needed. I do not ask for forgiveness on this and feel
> grateful for those who pointed me to the documents.

I'm not sure if it could be caused by the fact that we all are not
native English speakers -- but let me assure you this: the way you
presented and expressed yourself here on the list caused the sure
impression of trolling, for more than 2-3 people. I've been told so 
even in IRC by a handful of participants.

You didnt make exactly a unobtrusive and unboastful impression when
you came in and started to request quick and instantenious help with 
your AMD64 problems.

> Once a software package is released, it is expected to receive critism.

Ah, is it?

> So, be humble and build the software stronger.

I am very sure that NoMachine is working hard to make their software
even stronger than it is, and that your kind advise to them to "be
"humble will not influence them in the slightest. They already built
the best GUI remoting that is out there, with even more and much 
better things on the roadmap, and they did this even when you were
not yet around to ask them to.

What NoMachine probably won't do, is to put in time, money and effort 
to fix your (and other's, I admit) AMD64 build and run problems, as 
long as there is no business impetus to do so.

From all I hear, NoMachineNX and FreeNX work extremely well on AMD64 
and other 64bit platforms in 32bit mode.

So if you do need remote GUI access for your 64bit systems, do the
same as others do: use the 32bit version. It is free to use even for
trolls. If you don't like it, don't use it and go for VNC or pure X11.

> That's the mutual interest of 
> this project and your company.

I do not think you are in a position to speak in the name of "this
project", thank you. 
 
> I said no flamebait so I do not reply anything more than this.

So why do you think this thread started to become a rather unpleasant 
exchange?
 
> Have fun,
> Xiong

Kurt

 
> On 9/29/05, Gian Filippo Pinzari <pinzari at nomachine.com> wrote:
> >
> > LROUFAIL at nc.rr.com wrote:
> > > We are fortunate they don't just create software for Windows like most
> > > commercial software.
> >
> > It's not a matter of luck. I think there is an implicit pact between
> > a company releasing its software as OSS and the community. NX is OSS
> > not because of a late attempt to save a product that doesn't sell.
> > NX has always been OSS and since 2001 we have not received a single
> > significant contribution. On the contrary, we have had to defend
> > ourselves from the repeated attacks coming from all fronts. Don't
> > forget that a system like NX is a welcome addition to any big vendor's
> > software stack. Destroying a company developing an interesting
> > software is a much better alternative than partnering and sharing the
> > outcomes. Because of that, we have developed a very defensive attitude.
> > People can't expect NoMachine to be more open than it is already.
> >
> > About FreeNX, things work with OSS when developers contribute to the
> > advance of a software, not when they just copy it and don't give
> > anything back. About the ability of FreeNX to uncover bugs and help
> > NoMachine to test the software, I can say that this help doesn't pay
> > the bill. It's quite easy to find bugs. Users, for example, are
> > wonderful at that. NoMachine offers free downloads already and has a
> > staff trained at taking care of filling Trouble Reports. I think that
> > FreeNX developers should rather concentrate on helping with these
> > bugs, if they care about the future of NX.
> >
> > I know that the most fierce OSS defenders would like to see FreeNX out-
> > pace NoMachine in every respect and would like to see NX finally freed
> > of any commercial inheritance. These kind of people will never help
> > us. They will rather throw their FUD at us, one of the preferred sports
> > in this industry. We are not concerned of competition. On the contrary
> > we think that there can be a place for both a OSS and a commercial
> > NX version. Unfortunately it's difficult to compete with FreeNX when
> > we do 99% of the work and FreeNX keeps doing the 1% and giving it
> > away for free. Is this the way OSS development should work?
> >
> > > Don't take potshots at them from a free forum. They don't owe us better
> > > documentation. The code is a good enough gift to the community. If you
> > > want more you should pay for it.
> >
> > Nothing is ever perfect. We are more than wishful to listen and improve,
> > as long as there is a clear idea of who's supposed to do the work.
> > Bugs don't get fixed automatically just because somebody mentions them
> > in a mailing list. The same is true for the documentation. Instead of
> > criticizing all the time, people should rather ask themselves if they
> > have really tried to help, or have gone the easier route, consisting
> > in the usual "thanks a lot, unfortunately this stuff is not good enough
> > for me, I'll come when it's ready". As far as I know, everytime I have
> > asked somebody in the OSS community to help, he always responded that
> > he was already busy with some other thing. I can reassure you that I'm
> > tremendously busy too, and all the other people here are busy as well.
> >
> > /Gian Filippo.
> >
> >
> > _______________________________________________
> > FreeNX-kNX mailing list
> > FreeNX-kNX at kde.org
> > https://mail.kde.org/mailman/listinfo/freenx-knx
> >
>