NET Core, Java and Open Source

We need to talk about it

How open is .NET Core and C#? How does it compare to a platform like Java? Well... let's see.
Disclaimer: The post is a resumed version with lots of links, so be prepared to read it in a DFS or BFS way :) 

.NET Core

  1. In November 2014, The Microsoft team announced that "NET Core is Open Source"
  2. In 2015, Microsoft releases Visual Studio Code, a cross-platform multi-language IDE. 
  3. All these released under an Open Source license. The MIT License.
  4. NET Core runs in Windows, Linux, Mac and ARM-based systems (IoT)

Java

  1. Originally made open source by Sun in 2006
  2. Released under GPLv2 CE license. The CE clause allows it to be used in a more restrictive scenario. 
  3. Oracle has a different licensing schema for "Enterprise Java". While the OpenJDK is still safe (and should remain so) Enterprise customers face a different problem.
  4. It was conceived also as cross-platform and has wide support and a huge knowledge base.

Similarities

  1. They are both open source and cross-platform frameworks.
  2. Java and C# as languages are both Object Oriented and depending on whom you ask, kind of similar.

Differences

  1. Licensing: The MIT License is less restrictive than GPLv2 CE. If this could or could not be construed as meaning "more open" we will need a lawyer to find out. But general consensus is that The MIT License is less restrictive.
  2. Simplicity of Licensing: NET Core does not have nor requires a different "Enterprise" license. This simplifies licensing model from development to production.
  3. NET Core is a bit more than just C#, is includes VB and F#.

Bottom line

Where your preferences take you to pick one or the other due to technical or community differences, rest assured that using .NET Core will be at the least as safe (from an Open Source licensing point of view) as using Java. 
So... what are you waiting for? dotnet new something...



Comments

Post a Comment

Popular posts from this blog

Get-ChildItem vs Dir in PowerShell

Image
Batch as usual Recently I was in the need of modifying a huge amount of files across a network share. After installing Serviio media streaming service I noticed that it will crash "randomly". After checking the logs it was clear that ffmpeg was crashing when trying to open subtitle files that were not in the encoding indicated by the Serviio console. I needed a quick way to update all subtitle files to a common encoding, so I decided to convert all files to UTF8. Since I use a windows environment I went directly to PowerShell and wrote this.  Get-ChildItem -path .\ -filter *.srt -file  | ForEach-Object { (get-content $_.FullName) | Out-File $_.FullName -encoding utf8 } This worked almost right except for files with "[" or "]" (among other symbols) on the name or path. To solve it, just added the "-LiteralPath" switch to tell powershell not to consider any wildcards on the path name and just use it exactly as it is.  Get-ChildIt
Read more

The case for a 4 week sprint

Image
Every time we talk about SCRUM, the length of the sprint is stated as a period of "two to four weeks", rarely, however, have I seen people going outside of the 2 weeks. This is not written on stone of course, and while 3 weeks might seems odd, there is a benefit to using a longer period for your sprints.  Image is taken from scrum.org Without any hard data to back that decision, the answer I get from asking about this decision seems to be related to "delivery speed", we assume that because we deliver value to the business every 2 weeks, we are in a more "agile" environment. Well, that might not be so true in every sense or for every project. Let's break some arguments: 1. Sprint length is not equal to the speed of delivery There is more to the speed of development and delivery than the timeframe of the delivery cycle, in a world with DevOps and full CI/CD implemented for your project, you could (should?) actually deliver features every single day all t
Read more

NODE.js fs.readFile and the BOM marker

Working on a ReactJS project, got a small glitch while trying to read a JSON file and parse it as a javascript object. getDataObject() { var dataString = fs.readFileSync("./json/data.json", "utf8"); return JSON.parse(dataString); } output:   SyntaxError: Unexpected token   After checking, double and triple checking again that the file was correct I went deeper and realized that "fs.readFileSync" was returning me the BOM for the UTF file at the beginning of the string. So we just need to strip it out. getDataObject() { var dataString = fs.readFileSync("./json/data.json", "utf8"); return JSON.parse(dataString.replace(/^\uFEFF/, "")); } I then checked and there are "packages" for this, however I don't think is proper to just import a new dependency just to fix something this small. The big issue here is why is this considered correct. The BOM is not
Read more