Примеры использования Proprietary software developers на Английском языке и их переводы на Русский язык
{-}
-
Official
-
Colloquial
Proprietary software developers have lots of money.
Using the GPL for ours would have driven proprietary software developers to use another- no problem for them, only for us.
Proprietary software developers are often businesses.
Using the GPL for ours would have driven proprietary software developers to use another--no problem for them, only for us.
Proprietary software developers have the advantage of money;
After five years, its source code would go into the public domain, and proprietary software developers would be able to include it in their programs.
Today, proprietary software developers do something similar.
There are users who say that this is a bad thing- that the GPL“excludes” some proprietary software developers who“need to be brought into the free software community.”.
The proprietary software developers figure they won't get caught.
This exemplifies the arrogant and manipulative attitude that proprietary software developers have learned to adopt toward the people they are supposedly serving.
Proprietary software developers use copyright to take away the users' freedom;
On the issue of patents, free software developers can make common cause with most proprietary software developers, because in general they too stand to lose from patents.
But proprietary software developers frequently disregard gaping holes, or even introduce them deliberately.
UCITA has another indirect consequence that would hamstring free software development in the long term- it gives proprietary software developers the power to prohibit reverse engineering.
One way, the way that the proprietary software developers perhaps prefer, is: don't have any friends.
UCITA has another indirect consequence that would hamstring free software development in the long term--it gives proprietary software developers the power to prohibit reverse engineering.
Proprietary software developers intend to use the additional power UCITA would give them to increase their profits.
When we apply the idea to the actual world,which contains both free software developers seeking cooperation, and proprietary software developers seeking domination, the consequences are very different.
Why, after all, do some proprietary software developers offer gratis copies(1) of their nonfree programs to schools?
When we apply the idea to the actual world,which contains both free software developers seeking cooperation, and proprietary software developers seeking domination, the consequences are very different.
Proprietary software developers intend to use the additional power UCITA would give them to increase their profits.
The Lesser GPL was designed to fill the middle ground between these cases,allowing proprietary software developers to use the covered library, but providing a weak copyleft that gives users freedom regarding the library code itself.
Proprietary software developers have the advantages money provides; free software developers need to make advantages for each other.
The New York Times ran an article that stretched the meaning of the term to refer to user beta testing- letting a few users try an early version andgive confidential feedback- which proprietary software developers have practiced for decades.
However, this does not apply to proprietary software developers, since obstructionism deserves a punishment rather than a reward.
Some friends of free software have argued that UCITA would benefit our community, by making non-free software intolerably restrictive, and thus driving users to us. Realistically speaking, this is unlikely,because it assumes that proprietary software developers will act against their own interests.
However, this does not apply to proprietary software developers, since obstructionism deserves a punishment rather than a reward.
Proprietary software developers use copyright to take away the users' freedom; we use copyright to guarantee their freedom.
I make my code available for use in free software, and not for use in proprietary software, in order to encourage other people who write software tomake it free as well. I figure that since proprietary software developers use copyright to stop us from sharing, we cooperators can use copyright to give other cooperators an advantage of their own: they can use our code.
Proprietary software developers, seeking to deny the free competition an important advantage, will try to convince authors not to contribute libraries to the GPL-covered collection.