Language Selection

English French German Italian Portuguese Spanish

From Microsoft: C# and CLI under the Community Promise

Filed under
Microsoft

First the big news: Microsoft will be applying the Community Promise patent licensing to both C# and the CLI.

The announcement was done by Peter Galli at Microsoft over at Port25 and it states:

I have some good news to announce: Microsoft will be applying the Community Promise to the ECMA 334 and ECMA 335 specs.

ECMA 334 specifies the form and establishes the interpretation of programs written in the C# programming language, while the ECMA 335 standard defines the Common Language Infrastructure (CLI) in which applications written in multiple high-level languages can be executed in different system environments without the need to rewrite those applications to take into consideration the unique characteristics of those environments.

"The Community Promise is an excellent vehicle and, in this situation, ensures the best balance of interoperability and flexibility for developers," Scott Guthrie, the Corporate Vice President for the .Net Developer Platform, told me July 6.
It is important to note that, under the Community Promise, anyone can freely implement these specifications with their technology, code, and solutions.

You do not need to sign a license agreement, or otherwise communicate to Microsoft how you will implement the specifications.

rest here




Also: Microsoft has something called a community promise?

Promises, promises

theopensourcerer.com: Microsoft made an interesting announcement, they are promising not to sue people for using Mono. Jolly good of them really, it is nice not being sued.

Lets just assume for the moment that this promise means what they say it means (forgetting about the partial implementations exclusion and the fact that the promise needed to be made in the first place) and it makes Mono totally safe to use now, even in countries with broken patent laws. I still won’t be using Mono.

Rest Here

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

ammortizzata Scarpe Nike Zoom Winflo 2 marche che producono

Linux Graphics

  • Libinput X.Org Driver Updated For X.Org Server 1.19
    Peter Hutterer has announced the release of a new version of xf86-input-libinput, the X.Org DDX driver that makes use of libinput for input handling on the X.Org Server.
  • xf86-input-libinput 0.20.0
    Most important fix is the use of input_lock() instead of the old SIGIO stuff to handle the input thread in server 1.19.
  • Mesa 13.0 Planning For Release At End Of October, Might Include RADV Vulkan
    Following the mailing list talk over the past two days about doing the next Mesa release, plans are being discussed for releasing at the end of October and it might have just got a whole lot more exciting. Emil Velikov, Collabora developer and Mesa release manager for the past several release series, has commented on that previously discussed mailing list thread. He mentioned he was secretly waiting in hopes of seeing the RADV Radeon Vulkan driver merged for this next release! He said he'd even be willing to see it merged even if it's "not perfect/feature complete."

Security News

  • Don't Trust Consumer Routers
    Another example of why you shouldn’t trust consumer routers. d-link It isn’t just this specific d-link router. We’ve seen the same issues over and over and over with pretty much every non-enterprise vendor. Plus we don’t want our devices used by crackers to DDoS Brian Krebs anymore, right? We are Linux people. We CAN do this ourselves.
  • D-Link DWR-932 router is chock-full of security holes
    Security researcher Pierre Kim has unearthed a bucketload of vulnerabilities affecting the LTE router/portable wireless hotspot D-Link DWR-932. Among these are backdoor accounts, weak default PINs, and hardcoded passwords.
  • The Cost of Cyberattacks Is Less than You Might Think
    What's being left out of these costs are the externalities. Yes, the costs to a company of a cyberattack are low to them, but there are often substantial additional costs borne by other people. The way to look at this is not to conclude that cybersecurity isn't really a problem, but instead that there is a significant market failure that governments need to address.
  • NHS trusts are still using unsupported Windows XP PCs
    AT LEAST 42 National Health Service (NHS) trusts in the UK still run Microsoft's now-defunct Windows XP operating system. Motherboard filed Freedom of Information requests with more than 70 NHS hospital trusts asking how many Windows XP machines they use. 48 replied within the allotted time, and a whopping 42 of them admitted that they still use the operating system that reached end-of-life status in April 2014. Some of the culprits include East Sussex Healthcare, which has 413 Windows XP machines, Sheffield's Children's hospital with 1,290, and Guy's and St Thomas' NHS Trust in London with an insane 10,800 Windows XP-powered PCs. 23 replied to Motherboard's quizzing about whether they have an extended support agreement in place and, unsurprisingly, the majority said that they do not.

Games for GNU/Linux