News: .NET framework source code available soon...

  • Thread starter Jon Skeet [C# MVP]
  • Start date
C

Chris Shepherd

Arne said:
I disagree with most.

There are very few Linux apps with documentation of MS quality.

This is one of the polishing things MS does that is handy. It really
depends on what you're talking about though (I'm assuming you just mean
IDEs).
I have never seen VS being unstable and I would consider it
a lot better for developing C# code than Emacs.

For C# code, obviously, I don't think anyone was arguing it was superior
for writing .NET stuff...

For more generic things like C++, PHP, Java, there are better editors
that run on both Windows and Linux.
The operating system should not influence performance of
the apps at all.

Umm, while I agree they shouldn't the fact is they *do* and we have to
live with it.

Chris.
 
?

=?ISO-8859-1?Q?Arne_Vajh=F8j?=

Chris said:
For C# code, obviously, I don't think anyone was arguing it was superior
for writing .NET stuff...

For more generic things like C++, PHP, Java, there are better editors
that run on both Windows and Linux.

In my view VS and Emacs is not even in the same category.

An IDE is specialized for writing code in one or more
languages.

A general purpose editor is designed for editing all types
of text files.

I use a general purpose editor a lot (JEdit not Emacs but that
does not matter), because there are plenty of stuff that is
better for.

But writing C# or Java is not one of them.

Arne
 
?

=?ISO-8859-1?Q?Arne_Vajh=F8j?=

Chris said:
Last I checked Microsoft and Sun weren't charities providing public
lawyer services. They write up licenses to increase their profits and
for no other purpose, and they're quite happy to include unenforceable
items on the off chance that someone is intimidated by them.

Try read what is posted in this thread.

It seems obvious that you did not read about the JRL.
You may choose to throw around childish insults at other posters but
all the while you're spamming your own "poorly formulated opinions"
all over this thread. Maybe your time would be better spent to inform
yourself about the actual legal situation, which requires surprisingly
little research.

I think the childish part is to insist on being right even when
presented with plenty of evidence that industry practice is not
supporting it.

Arne
 
P

Peter Duniho

Mads said:
[...]
Hope that clears my viewpoint, which I believed is shared by many, up.

Yes, thank you for the clarification. IMHO, it still supports my
contention that in this scenario, it's really the lawyers making
business for themselves.

But you're right...if you follow the food-chain all the way up,
ultimately you have to satisfy your customers -- those putting food on
your table -- that you are "safe".

A sad situation, but I see the truth in it.

Pete
 
C

Chris Shepherd

Arne said:
In my view VS and Emacs is not even in the same category.

Sorry for not being clear. I wasn't disagreeing about Emacs, nor do I
really care about Emacs. I was simply saying there are better editors
out there that run on both platforms (ie: NetBeans, Eclipse).

The rest of your response is really irrelevant to my point. I don't know
why you'd even make the original comparison of Emacs to VS if you
understand they're vastly different types of software.


Chris.
 
?

=?ISO-8859-1?Q?Arne_Vajh=F8j?=

Chris said:
Sorry for not being clear. I wasn't disagreeing about Emacs, nor do I
really care about Emacs. I was simply saying there are better editors
out there that run on both platforms (ie: NetBeans, Eclipse).

The rest of your response is really irrelevant to my point. I don't know
why you'd even make the original comparison of Emacs to VS if you
understand they're vastly different types of software.

Try read the thread from start.

The subthread started by someone else writing:

# faster and more
#stable development environments (emacs vs Visual Studio Team Edition)

I am just commenting on a comparison someone else brought up.

Arne
 
P

Peter Duniho

Frans said:
It's not in MS' license, it's in Mono's policy for submitters of
patches and code.

So you agree with me then. Microsoft has made no such imposition, and
it's not at all about "that license has all what MS Has to say about it".
[...]
you can't reasonably work on these projects because you personally
embed the risk of getting other peoples code in the main trunk.

Why? If you don't copy the code, there's no risk.
Peter, please... it's not in rotor's license, it's in the policy for
mono (and other high profile open source projects). It's simple math,
really.

I know. That's been my point all along.
Erm... I assume you're doing software development, ok? So you
understand logic.

If codebase A is open for you to look at, but A is also commercial, so
you can only look, and you want to work on codebase B, where B is doing
something similar to (parts of) A, and B is open source, isn't it so
that by accepting the license for A, you automatically can be ASSUMED
your work on B is copied from A?

How can you try to make an argument based on logic, and yet still
introduce an assumption?

In any case, it can be assumed that your work on B is copied from A
whether or not you ever looked at A or ever even had access to it. What
you actually did in no way affects what assumptions someone might make
about you.
[...]
If mono opens the door to do .NET development and deployment on Linux
on a big scale, MS will kill it. It's not strange, it's logical from
MS' pov, simply because it would otherwise hurt their business.

That's just not true. I sure hope no one at Microsoft is dumb enough to
think it is.

Having .NET on Linux, Mac, etc. can only help Microsoft. Can you
imagine the sort of advantages they would have should they wind up
controlling the primary development platforms not only on Windows, but
also on Linux and Mac?

You might argue some lost OS license sales to those platforms but a)
they aren't going to be losing any significant number of sales to Linux
any time soon and that's not going to change until Linux is actually
easy to use, and b) they aren't likely to lose sales to Mac
either...even though Apple has dramatically improved their market share,
it's done so in the hardware business; people are buying more Macs
because they have Intel hardware now, and that means they are still
buying Windows licenses. Apple is making the OS market _larger_ rather
than taking actual sales away from Microsoft.

But even beyond all that, Microsoft's not solely dependent on OS
licenses. They have other ways to leverage their investments, and
dominating the development platforms on all OS's is a great way to do that.

Mono isn't a threat at all, any more than Wine was/is a thread. It's a
potential boon.
[...]
True. But the question of whether a license was accepted has nothing
to do with that.

of course it has. If you have accepted the license, they have an easy
job to proof you had every oppertunity to copy. If you DIDN'T accept
the license, you didn't have the oppertunity and they have a harder job
proving you copied code.

No, they don't. Your acceptance of the license isn't going to be used
as proof of you copying; a comparison of the code will be.
How can you look at the sourcecode without accepting the license? No,
reflector doesn't count, that's not the sourcecode.

Really? You really believe that there's no way to obtain the source
code unless you accept Microsoft's license and get it directly from them?

I'm sorry...as long as you continue to hold that belief, there is no
hope for this discussion. And no, I'm not talking about Reflector. I'm
talking about the actual source code Microsoft is providing.
[...]
No, it wouldn't be silly at all. It's easy enough to duplicate the
code from a compiled implementation. You don't need the source code
to violate the copyright rules.

How can I copy SOURCE without access to the source?

First, please re-read what you're replying to. In the text you quoted I
am _not_ talking about copying the source. But you don't need to copy
the source to be in violation of copyright. And you don't need the
source code to copy the implementation.

That said, even though your question isn't relevant to the text you
quoted, it's easy enough to answer: you can't copy source without access
to source, but assuming that your only access to the source is through
Microsoft after accepting their license is silly. Once Microsoft has
released the source to anyone, it is trivially available whether you've
accepted a license or not, and even if they don't release it that
doesn't preclude the source from somehow being leaked from within Microsoft.
If I have only a
compiled form, I can reverse engineer it, and re-use that, which is
allowed in most countries, IF you don't have access to the code and IF
you need that code to do your own work

I'm not going to pretend to be an expert in worldwide copyright law.
However, I doubt that any country that is part of the global IP treaties
allows for actual copying of an implementation, with or without source code.

Yes, you can reverse engineer to allow your own original code to
correctly operate with existing code. But that's a much different
situation than what I am talking about and what is relevant in this
discussion.
[...]
No doubt. I have said as much. But that's not the issue here. The
question is whether the Mono group has a legal requirement to protect
themselves in this way, and my assertion is that they do not.

So they, and other open source projects who have the same rules, have
a skewed vision on reality? Does 'SCO' ring a bell to you? :)

The question is whether Microsoft's imposed a legal requirement. A
projects "vision on reality", skewed or otherwise, is irrelevant.

That said, I would be surprised if SCO would have gotten as far as they
had without heavy backing from deep pockets, and it still blew up in
their face. I wouldn't call the SCO trial a very good example of
successful litigation on the part of the plaintiff.
[...]
I can call it whatever I want to call it. I find this license evil, as
it has sideeffects which aren't visible at first. You for example don't
understand the side effects ;). I've explained them again above.

Frankly, you should consider the possibility that rather than me being a
complete moron and not being able to understand the "side effects" as
you describe them, that I do in fact understand what you're writing
about and still don't find the license to be "evil".
[...]
Also, if MS does something bad to YOU, you can't win a lawsuit
against them if they have a strong case against you in another area.
That's an absurd statement. The courts do not decide separate issues
together. If you have a case against Microsoft with respect to one
thing, it doesn't matter what other case they may have against you in
some unrelated area.

I wasn't talking about courts, I was talking about threats.

You wrote "you can't win a lawsuit". The only thing that can stop you
from winning a lawsuit is the courts. So if you weren't talking about
the courts, why did you write something that is only relevant with
respect to the courts?
Has it
ever occured to you WHY companies file so many patent requests?

Please, stop being so condescending. You are making huge, wild
assumptions about what I do or do not know, and what my own personal
experience is (hint: not only has the question of why companies file so
many patent requests occurred to me, in my own career I have been smack
in the middle of the issue).
That's
right, to protect THEMSELVES against companies who threat them with a
lawsuit: if that happens they can threat them back with "if you sue,
we'll sue you over this other thing".

That in no way blocks your own success with a particular legal action.

Pete
 
J

Jon Harrop

Chris said:
Sorry for not being clear. I wasn't disagreeing about Emacs, nor do I
really care about Emacs. I was simply saying there are better editors
out there that run on both platforms (ie: NetBeans, Eclipse).

For some things, yes. For other things (like OCaml), no.
 
F

Frans Bouma [C# MVP]

Peter said:
So you agree with me then. Microsoft has made no such imposition,
and it's not at all about "that license has all what MS Has to say
about it".

You make all kinds of remarks and then I agree with you? where? I just
said that the CONSEQUENCES of the MS licenses are to be understood
well, and aren't something you can just ignore. What license MS puts
their stuff, it's their responsibility. What we've to deal with, are
the consequences of the license they pick.
[...]
you can't reasonably work on these projects because you personally
embed the risk of getting other peoples code in the main trunk.

Why? If you don't copy the code, there's no risk.

So why does MS forbid their employees to look at GPL-ed code?
How can you try to make an argument based on logic, and yet still
introduce an assumption?

In any case, it can be assumed that your work on B is copied from A
whether or not you ever looked at A or ever even had access to it.
What you actually did in no way affects what assumptions someone
might make about you.

If you say it can be assumed, how can I copy something if you can't
proof I had access? Isn't it so that closed source code isn't
accessable to people outside the company?
[...]
If mono opens the door to do .NET development and deployment on
Linux on a big scale, MS will kill it. It's not strange, it's
logical from MS' pov, simply because it would otherwise hurt their
business.

That's just not true. I sure hope no one at Microsoft is dumb enough
to think it is.

You live under rocks apparently. Some time ago, MS put their
heavyweight onto testdriven.net because it was usable in a free vs.net
SKU. Now, you're telling me MS isn't going to do anything less lame
than that? You're dreaming. They'll kill off any company who gets in
their way, as any major corp will, because that's today's level of
business. If you think MS is a different company than any other big
corp, you're naive.
Having .NET on Linux, Mac, etc. can only help Microsoft. Can you
imagine the sort of advantages they would have should they wind up
controlling the primary development platforms not only on Windows,
but also on Linux and Mac?

Last time I checked, they're making money by selling OS licenses. If
..NET runs on Linux, they don't sell a windows license if the user picks
up OpenSuse. That's the point.
You might argue some lost OS license sales to those platforms but a)
they aren't going to be losing any significant number of sales to
Linux any time soon and that's not going to change until Linux is
actually easy to use,

hehehe, you really have no clue what the real world looks like, do you
;). If you think .NET is of any relevance in the overall software
world, you're mistaken. Even in the narrow scope of webapps, .net has
no real significance and that will only become less with RoR and
friends. This isn't about desktops, mind you.
and b) they aren't likely to lose sales to Mac
either...even though Apple has dramatically improved their market
share, it's done so in the hardware business; people are buying more
Macs because they have Intel hardware now, and that means they are
still buying Windows licenses. Apple is making the OS market larger
rather than taking actual sales away from Microsoft.

how is buying an intel mac equal to buying an ms license?
But even beyond all that, Microsoft's not solely dependent on OS
licenses. They have other ways to leverage their investments, and
dominating the development platforms on all OS's is a great way to do
that.

Peter, C# (and also Java) have no real significance in the big world
of software development. So how MS can dominate development platforms
is beyond me. (hint: most code on the planet is still cobol (around
30%), C and C++ each 10% and the rest is divided among 500+ languages. )
[...]
it's THEIR job to proof you DID copy it.
True. But the question of whether a license was accepted has
nothing to do with that.

of course it has. If you have accepted the license, they have an
easy job to proof you had every oppertunity to copy. If you DIDN'T
accept the license, you didn't have the oppertunity and they have a
harder job proving you copied code.

No, they don't. Your acceptance of the license isn't going to be
used as proof of you copying; a comparison of the code will be.

Ah, and because you say so, it's true?
Really? You really believe that there's no way to obtain the source
code unless you accept Microsoft's license and get it directly from
them?

I can also sign their special license as an MVP and look at their code
but I also don't do that for the same reason. How can I otherwise look
at their code, Peter?
I'm sorry...as long as you continue to hold that belief, there is no
hope for this discussion. And no, I'm not talking about Reflector.
I'm talking about the actual source code Microsoft is providing.

Yeah, and where is it? Or do you mean Rotor's sourcecode?
First, please re-read what you're replying to. In the text you
quoted I am not talking about copying the source. But you don't need
to copy the source to be in violation of copyright. And you don't
need the source code to copy the implementation.

That said, even though your question isn't relevant to the text you
quoted, it's easy enough to answer: you can't copy source without
access to source, but assuming that your only access to the source is
through Microsoft after accepting their license is silly. Once
Microsoft has released the source to anyone, it is trivially
available whether you've accepted a license or not, and even if they
don't release it that doesn't preclude the source from somehow being
leaked from within Microsoft.

How can it freely be available if no-one is allowed to COPY it? So how
can anyone copy the sourcecode no-one-is-allowed-to-copy and place it
somewhere I could access it?

That would mean that the code is already freely available out there
because there are MVPs who have signed the license to peek into MS'
code. But you can't point me to a site where the .NET source is
available for download, can you?

So how can you ASSUME I copied anything if there's no proof I can
access it without accepting a license I didn't accept?
[...]
I can call it whatever I want to call it. I find this license
evil, as it has sideeffects which aren't visible at first. You for
example don't understand the side effects ;). I've explained them
again above.

Frankly, you should consider the possibility that rather than me
being a complete moron and not being able to understand the "side
effects" as you describe them, that I do in fact understand what
you're writing about and still don't find the license to be "evil".

THen, why bother replying and just go ahead and look at the code? Oh,
Peter, btw, please answer me this: why aren't MS employees allowed to
peek at GPLed code? Why are most big ISV's forcing their employees to
just work on their own code and not peek into other people's codebases?
Because they're overly paranoid and have no clue?

No, Peter, because they want to avoid a risk, a risk which you are
willing to take without thinking things through. A risk you're waving
away as irrelevant.

Well, if you want to do that, I don't mind, it's your life. I just
want to make clear what the side effects are, you think they're
irrelevant, and with you a lot of people think the same. Good for you
and them, but I do hope neither of you all gets into trouble later on.
Oh, that's right, you won't get into trouble, because MS is a nice
company and won't do bad things to you and what I and others have
argued about is so irrelevant and meaningless, why bother, right?

:).
[...]
Also, if MS does something bad to YOU, you can't win a lawsuit
against them if they have a strong case against you in another
area.
That's an absurd statement. The courts do not decide separate
issues together. If you have a case against Microsoft with
respect to one thing, it doesn't matter what other case they may
have against you in some unrelated area.

I wasn't talking about courts, I was talking about threats.

You wrote "you can't win a lawsuit". The only thing that can stop
you from winning a lawsuit is the courts. So if you weren't talking
about the courts, why did you write something that is only relevant
with respect to the courts?

Peter, ever read about how big corps fight their lawsuits? If they
have something against YOU, will YOU take the risk of losing everything
you own and beyond for that? I won't.
That in no way blocks your own success with a particular legal action.

Sweet dreams, Peter :)

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
 
?

=?ISO-8859-1?Q?Arne_Vajh=F8j?=

Peter said:
Why? If you don't copy the code, there's no risk.

I posted some links about clean room implementation techniques.

Did you not read them ?

Or did you just assume that you know better than those companies
spending millions on making sure the developers has never seen
any of the source for what they are reimplementing ?

Arne

PS: There are another good story at http://oldcomputers.net/compaqi.html
 
P

Peter Duniho

Frans said:
You make all kinds of remarks and then I agree with you? where?

Where you wrote practically the same statement I made several posts ago:

That's why I quoted it when I made my statement.
I just
said that the CONSEQUENCES of the MS licenses are to be understood
well, and aren't something you can just ignore. What license MS puts
their stuff, it's their responsibility. What we've to deal with, are
the consequences of the license they pick.

The only consequences I am discussing here are those that are
self-imposed by the Mono project. There's nothing in the license that
specifically prohibits Mono developers from using the .NET source code
for other purposes.
So why does MS forbid their employees to look at GPL-ed code?

I'm aware of no such prohibition. If it does exist, Microsoft doesn't
enforce it very well, because I know Microsoft developers who have seen
GPL-ed code.
If you say it can be assumed, how can I copy something if you can't
proof I had access?

Whether I can prove you had access in no way affects whether you can
copy something. It is bizarre that you would even imply the two are
connected somehow.
Isn't it so that closed source code isn't
accessable to people outside the company?

First of all, just because a software publisher hasn't purposely
disclosed their source code, that in no way proves that their source
code hasn't been disclosed.

Secondly (and I don't know why you still don't understand this...I've
already pointed it out twice), you don't need the source code in order
to copy someone else's code. I haven't yet downloaded any .NET source
code, but I have everything I need on my computer that I need to copy
their code. I have the actual compiled implementation, which is
perfectly sufficient in order to achieve copying.
You live under rocks apparently.

Why do you think that writing insults is somehow a legitimate debating
tactic? All it does is show that you need to resort to ad hominem
attacks rather than using actual factual information. And you tend to
do it a lot.
Some time ago, MS put their
heavyweight onto testdriven.net because it was usable in a free vs.net
SKU. Now, you're telling me MS isn't going to do anything less lame
than that? You're dreaming. They'll kill off any company who gets in
their way, as any major corp will, because that's today's level of
business. If you think MS is a different company than any other big
corp, you're naive.

Well, so far you've posted the most naive comments. But that said, my
point is that having .NET available on other platforms isn't a threat to
Microsoft. Your entire premise is based on the assumption that it is,
so all of your conclusions fail.
Last time I checked, they're making money by selling OS licenses. If
..NET runs on Linux, they don't sell a windows license if the user picks
up OpenSuse. That's the point.

No, it's not the point. You even quoted the part of my post in which I
explain why it's not the point.

Microsoft stands to gain a LOT more by owning the development platform
on Linux than they would lose from possibly losing the OS license sale.
Besides, that assumes the Linux installation represents a lost sale of
Windows, when in fact it's more likely that which OS is chosen will
continue for some time to be based on factors other than whether .NET is
supported on the platform or not.
hehehe, you really have no clue what the real world looks like, do you
;).

Ah. Yes, again with your personal attacks. Honestly, all you're doing
is showing how you can't support your points without insulting the person.
If you think .NET is of any relevance in the overall software
world, you're mistaken. Even in the narrow scope of webapps, .net has
no real significance and that will only become less with RoR and
friends. This isn't about desktops, mind you.

Well, first of all, .NET isn't "about desktops" either. It's supported
and useful on server-class platforms. Beyond that, this is only about
platforms where Microsoft has a presence. Mentioning any variety of
other computer software implementations that are entirely outside of
Microsoft's market is pointless. It has nothing to do with this.
how is buying an intel mac equal to buying an ms license?

Because the main inroads Apple has made are due specifically to their
choice of Intel hardware, that is because those people buying Macs that
wouldn't have otherwise are doing so because they can run Windows on
them. So practically all of those sales that are due to the hardware
switch also represent a sale of a Windows license.
Peter, C# (and also Java) have no real significance in the big world
of software development. So how MS can dominate development platforms
is beyond me. (hint: most code on the planet is still cobol (around
30%), C and C++ each 10% and the rest is divided among 500+ languages. )

Even if your numbers are real (and they sound made up to me), we are not
talking about all of the code on the planet. The only relevant
environments are those in which .NET _is_ in fact a significant factor:
Windows applications (including servers), and other platforms serving
the same needs.

Also, note that we aren't talking about C#. We're talking about .NET.
There's a different.

Finally, if .NET (not C# or Java) "have no real significant in the big
world", then how could your assertion be true that .NET being present on
other platforms would cause Microsoft to lose sales of Windows?

I think at the very least, you should stick with one thesis or another,
rather than trying to assert two mutually exclusive ones.
Ah, and because you say so, it's true?

No, it's a basic consequence of the question of copying. It's
practically axiomatic.

You must compare two works when determining whether one has been copied
from the other or not. If the two works when compared aren't actually
the same, then it really doesn't matter what else may or may not be
proved. Something can't be copied unless the copy is like the original.
I can also sign their special license as an MVP and look at their code
but I also don't do that for the same reason. How can I otherwise look
at their code, Peter?

And I'm the one who's naive?
Yeah, and where is it? Or do you mean Rotor's sourcecode?

No. As I wrote: "I'm talking about the actual source code Microsoft is
providing."
How can it freely be available if no-one is allowed to COPY it? So how
can anyone copy the sourcecode no-one-is-allowed-to-copy and place it
somewhere I could access it?

Seriously. You have the gall to call me naive, and then post something
like that? What is allowed has absolutely zero to do with what can (and
will) be done.
That would mean that the code is already freely available out there
because there are MVPs who have signed the license to peek into MS'
code. But you can't point me to a site where the .NET source is
available for download, can you?

I don't need to in order for it to be a trivially true statement that
once Microsoft has made the .NET source code broadly available, it will
be able to be obtained by a person who has not explicitly accepted the
license.

Frankly, I'm amazed that you still believe the license has anything to
do with it. The code is not legally allowed to be copied with or
without the license. How a person gets the code doesn't affect
anything, and it certainly doesn't affect how difficult it is to prove
that someone copied the code.
So how can you ASSUME I copied anything if there's no proof I can
access it without accepting a license I didn't accept?

The mere fact that the copy is the same as the original is generally
acceptable proof. Things are copied on a regular basis without legal
access to the original. That doesn't stop the legitimate owner of the
copyright from successfully making a claim.

Pete
 
J

Jon Harrop

Frans said:
Last time I checked, they're making money by selling OS licenses.

and Office.
Peter, C# (and also Java) have no real significance in the big world
of software development. So how MS can dominate development platforms
is beyond me. (hint: most code on the planet is still cobol (around
30%), C and C++ each 10% and the rest is divided among 500+ languages. )

Where on Earth did you get those statistics? I can't believe that...
 
F

Frans Bouma [C# MVP]

Jon said:
Where on Earth did you get those statistics? I can't believe that...

University. (a friend of mine is now in his masters, he told me about
it, I didn't believe it either, but it's apparently the result of
scientific research.) After thinking about it a bit, it's also logical.
Even imagine how much C code you're using every day... and imagine how
many big systems there are, based on cobol.

Do a wild guess how many lines of C there are in an MRI scanner. (7-10
million). Or a wafer stepper (10 million). that's such a truckload of
code, and if you don't realize this, you can't even possibly imagine
how big the pile of code out there really is. :)

FB
--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
 
J

J.B. Moreno

Chris Nahr said:
Peter Duniho


No, you are not.

Sure you are. A suit is an allegation, not evidence. You could
theoretically be sued without having either copied their code or
produced anything similar to it, they would just say that you did and
then the judge would hopefully rule in your favor when they couldn't
back it up.
Copyright does not cover duplication of function or even accidental
recreation of the same exact program text, only intentional copying.
Hence "copy"right.

You're missing the point. He is saying that while unfounded lawsuits
are a possibility (which is what the OP seems to be worried about), MS
doesn't have to publish their code in order to make an unfounded
lawsuit.

This means that this isn't a diabolical plot on MS's part to kill
contribution to the Mono project. And if it *was* a diabolical plot,
then the OP's risk of being sued wouldn't be effected by whether or not
he looked at MS's code (how useful or important his contribution to
Mono would be a more significant factor).
 
M

Mads Bondo Dydensborg

Peter said:
Mads said:
[...]
Hope that clears my viewpoint, which I believed is shared by many, up.

Yes, thank you for the clarification. IMHO, it still supports my
contention that in this scenario, it's really the lawyers making
business for themselves.

There is much truth in that statement.
But you're right...if you follow the food-chain all the way up,
ultimately you have to satisfy your customers -- those putting food on
your table -- that you are "safe".

And, I might add, our stockholders too.
A sad situation, but I see the truth in it.

Thanks,

Regards,

Mads

--
Med venlig hilsen/Regards

Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo
Dydensborg
Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. +45 44 86 77
34
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top