.NET Core Image Processing • Hacker News Board

Re: .NET Core Image Processing

#41

Post by phhlho » Fri, Jan 20, 2017, 4:24 PM UTC

gthtjtkt wrote: post #39

What are the best resources for someone who wants to move from .NET desktop development to .NET web development? All the popular sites like Udacity and FreeCodeBootcamp rarely (if ever) touch the MS stack. I know this isn't exactly the right place to ask, but I've had no luck anywhere else...

If you are already familiar with .NET, you might find some courses on Microsoft Virtual Academy a good starting point. There is a web development category: https://mva.microsoft.com/training-topics/web-development#!i...

Looking at the courses available, I would probably start with: https://mva.microsoft.com/en-US/training-courses/getting-sta...

then look into either ASP.NET MVC: https://mva.microsoft.com/en-US/training-courses/introductio...

or ASP.NET Core: https://mva.microsoft.com/en-US/training-courses/intermediat...

This is coming from someone that hasn't actually used these, so take my recommendations with a grain of salt.

Re: .NET Core Image Processing

#42

Post by okreallywtf » Fri, Jan 20, 2017, 4:35 PM UTC

Also take into account that rely on the GDI API won't work in Azure App Services (which is where most new azure based web apps reside) [1]. It would be nice if this reduced some of the issues with 3rd party libraries (pdf generation etc) running inside of app services. We've had some issues having to keep old web/worker roles around for this exact reason and it costs us more money.

>Components rely on GDI API may not work on Azure Websites. The workaround is moving to Azure Web Role. (If you are using the ReportViewer control, we have enabled PDF generation for most applications.)

[1] https://social.msdn.microsoft.com/Forums/en-US/6ed5c738-390a...

Re: .NET Core Image Processing

#43

Post by pmalynin » Fri, Jan 20, 2017, 4:50 PM UTC

Does anyone know when .NET Core will get a decent linear algebra library?

I've heard MathNet.Numerics has a plan to add it, but so far there seems to not have been much progress.

Re: .NET Core Image Processing

#44

Post by runjake » Fri, Jan 20, 2017, 5:05 PM UTC

gthtjtkt wrote: post #39

What are the best resources for someone who wants to move from .NET desktop development to .NET web development? All the popular sites like Udacity and FreeCodeBootcamp rarely (if ever) touch the MS stack. I know this isn't exactly the right place to ask, but I've had no luck anywhere else...

The training resources available on the ASP.net website are excellent and cover all skill levels.

https://www.asp.net

Re: .NET Core Image Processing

#45

Post by mellinoe » Fri, Jan 20, 2017, 5:57 PM UTC

rubber_duck wrote: post #19

AlexC04 wrote: post #18

Is it a pipe dream to hope they go for DirectX in dotnetcore one day? I'm so happy to read that they've gotten the image processing piece in place. A while ago, on a bit of a lark and to see if I could, I started trying to port a copy of selenium webdriver to DNC and was initially surprised bow how successful I was in getting it to compile and build. For the most part it was just re-pointing namespaces to their new l…

>Is it a pipe dream to hope they go for DirectX in dotnetcore one day? What do you mean ? DX is Windows specific, .NET core is cross platform. And DX doesn't even have official .NET bindings on full .NET AFAIK. OTOH I'm sure SharpDX and the likes could be ported (if it already isn't - this : https://github.com/sharpdx/SharpDX/issues/520 suggest it should work but I haven't tried it)

Yes, SharpDX does work on .NET Core. Although it's not "official", it is essentially the de-facto library for DirectX bindings.

Re: .NET Core Image Processing

#46

Post by bleroy » Fri, Jan 20, 2017, 6:00 PM UTC

wolfspider wrote: post #36

Why wasn't Pixman/Cairo tested but Skia was tested? I'm sure it has to do with the natural availability of these things on .NET but I just checked and Cairo still has binding pre and post Mono. I would consider this option strongly there is way more support for Cairo in just about everything than Skia.

Because it's not Skia that is tested, but SkiaSharp, which is a .NET / Mono wrapper for Skia. It was included because the work to make it compatible with .NET Core is close to completion and because it's promising work. I hope this clarifies. If there were Pixman/Cairo .NET Core wrappers in existence or close to completion, I'd be happy to update the post with them.

Re: .NET Core Image Processing

#47

Post by wolfspider » Fri, Jan 20, 2017, 6:22 PM UTC

bleroy wrote: post #46

wolfspider wrote: post #36

Why wasn't Pixman/Cairo tested but Skia was tested? I'm sure it has to do with the natural availability of these things on .NET but I just checked and Cairo still has binding pre and post Mono. I would consider this option strongly there is way more support for Cairo in just about everything than Skia.

Because it's not Skia that is tested, but SkiaSharp, which is a .NET / Mono wrapper for Skia. It was included because the work to make it compatible with .NET Core is close to completion and because it's promising work. I hope this clarifies. If there were Pixman/Cairo .NET Core wrappers in existence or close to completion, I'd be happy to update the post with them.

https://github.com/zwcloud/CairoSharp

Re: .NET Core Image Processing

#48

Post by bleroy » Fri, Jan 20, 2017, 6:24 PM UTC

replete wrote: post #37

Google's library destroys in benchmarks, but quality and filesize is lower which suggests to me it wasn't a fair test. The quality settings should have been standardised to human-perceived image quality, given that's the purpose of an image.

Unfortunately that's not possible. Each library makes choices and tradeoffs on their defaults. Each time, I set whatever quality dials existed to the highest available, and I standardized on 75 JPEG compression. There is no way to get consistent quality across all libraries, which is why I included the results for the 12 images used in the test in the blog post, so everyone can handle this the way they want.

Re: .NET Core Image Processing

#49

Post by bleroy » Fri, Jan 20, 2017, 6:27 PM UTC

morrbo wrote: post #8

Great to know, and good article. Can't help but feel that the author should have put in the full compressed images so we can view them. From the table at the bottom, Skia looks like it has quality issues, but it is kind of hard to say without seeing the full-sized compressed images. The uncompressed ones are on github, unless i've missed something, the compressed ones aren't.

What do you mean? The test is doing resize and JPEG compression. If you're interested in isolating the compression part, the code on GH should be super easy to modify to your particular requirements.

Re: .NET Core Image Processing

#50

Post by bleroy » Fri, Jan 20, 2017, 6:28 PM UTC

romanovcode wrote: post #5

Offtopic: I am the only one who absolutely hates charts like [0]these? Like what are those numbers on top, why it has no legend? Is it CPU utilization, miliseconds, seconds (maybe it was done over 1000 images or so)? [0] - https://msdnshared.blob.core.windows.net/media/2017/01/Resiz...

The legend is below each chart, with a table of the numeric results, with standard deviation. The code to reproduce the test is also provided, as well as the sample images.