ImageSharp VS DotImaging

ImageSharp

• Is there a way to remove metadata from an image file?
  4 projects | /r/csharp | 7 Dec 2023
• First automatic JPEG-XL cloud service
  2 projects | news.ycombinator.com | 19 Sep 2023

  > High quality progressive decoding at reduced filesizes is a big positive for me.

  This is really cool!

  Honestly, I want to use regular progressive JPEGs for a current project of mine, but it seems that even that doesn't have support in all the tech stacks yet despite how long it's been around for, for example: https://github.com/SixLabors/ImageSharp/issues/449

  Here's hoping that in the case of JPEG-XL this will be more commonplace!

• Unity’s New Pricing: A Wake-Up Call on the Importance of Open Source in Gaming
  5 projects | news.ycombinator.com | 15 Sep 2023

  Here's an example:

  https://github.com/SixLabors/ImageSharp/blob/main/LICENSE#L2...

  https://news.ycombinator.com/item?id=33301518

  Again, nothing stops someone from forking and maintaining.

  Are you saying this is not legally enforceable? Because I am under the impression from my legal council it is. I can ask again to get more clarity.

• Compress/resize images
  7 projects | /r/dotnet | 14 Dec 2022

  ImageSharp is another option, but could have licence implications.

• ImageSharp leaving the .NET Foundation due to licensing change
  8 projects | news.ycombinator.com | 22 Oct 2022

  https://github.com/SixLabors/ImageSharp/discussions/2151#dis...

  "The transitive clause is actually really important, I'll explain why.

  I've explicitly called out the following to ensure that the Split License is non viral.

  Once granted, You must reference the granted license only in all documentation.

  In practical terms this means that If you are granted a license, that's the one you're use, not the Split License which exists to derive the license to be granted to you.

  So if you're OSS, you should only be concerned about and reference the Apache 2.0 license - downstream consumers shouldn't need to care.

  That, on the surface makes the whole transitive/direct thing seem redundant except for the fact we have to use the Split License in NuGet packages, so if someone is looking up their supply chain then they can reference the transitive clause to determine liability (none).

  Can it be exploited. Yes, but as I've said elsewhere. "Evil Corp is gonna evil". They're actually more likely to simply ignore the license."

  8 projects | news.ycombinator.com | 22 Oct 2022

  Library users should come together and fork the last open source version (https://github.com/SixLabors/ImageSharp/tree/v2.1.3) and maintain that together. Just having a version still available, even if it's got no new features, may be enough to make the Six Labors reconsider their approach because why pay for a library that can mostly work for free?

  8 projects | news.ycombinator.com | 22 Oct 2022

  They have lot of employees: https://github.com/SixLabors/ImageSharp/graphs/contributors

• TIL: mime types and static assets in Umbraco
  2 projects | dev.to | 21 Oct 2022

  Since .net doesn't yet support avif and neither does ImageSharp, files of this type just didn't have a MIME type available and trying to use them would result in a 404 error.

• I am trying to use System.Drawing to upscale a PNG, but it's exhibiting bizarre behavior and is driving me mad
  2 projects | /r/csharp | 18 Jul 2022
• License Changes for Six Labors Products
  2 projects | /r/dotnet | 16 Jul 2022

  See https://github.com/SixLabors/ImageSharp/discussions/2151 for previous discussions on the subject.

DotImaging

We haven't tracked posts mentioning DotImaging yet.
Tracking mentions began in Dec 2020.