Linked by Thom Holwerda on Fri 19th Aug 2005 20:45 UTC, submitted by mmadia
Permalink for comment 20567
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2005-07-22
The problem is with human failing.
From one hand you have a good programmer, Marcus, that was insulted by a post in his log, he falsly attributed to Bernd (Bernd cannot write such good english as the anonymous poster by the way). Marcus had to defend his honor, but he should have found another way.
Now on the other hand, we have Bernd who is responsible not only for himself (it would have been easy to respond if he was), but for an entire company. He doesn't have time or the will to be personal, so he responed in the legal manner in which he did.
My belief is that both are wrong. They should work together, not against each other, because they are killing BeOS.
As for the NDA, it is a normal bussiness procedure. I have signed one with the company I work with, and even if I hadn't, what the NDA said, is what I would have done anyway.
In response to an earlier post about a developer that was asked to sign an NDA to be given access to Zeta development, what people don't understand is that Zeta is using BeOS 6 api. The depricated driver API or BeOS 3 was removed from Be and now only the API from v4 and upwards is valid. The developer could just have bought Zeta instead of singing the NDA to be provided with it free of charge and continue development of his driver using the documented BeOS 5 api.