Live data from Hacker News

.NET Core Image Processing

blogs.msdn.microsoft.com

51–60 of 70 posts

Re: .NET Core Image Processing

#51

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 want to learn .Net development then you should try pluralsight. it's a great resource for everything .net. I'm on mobile right now but you can get free 3 months subscription. you can also get a free month I think to wintellect.

Re: .NET Core Image Processing

#55
post #10

Earlier quoted context omitted.

What would you recommend instead of System.Drawing in a web app? Any of the ones listed in the article?

Unless you have a good reason to then I would recommend against rolling your own (with any library). Use an existing cloud service that specializes in it.

Most b2b saas products have a specific reason to not use a third party for everything - their customers don't want their data sprayed everywhere. Add to that anyone with a government contact.

Re: .NET Core Image Processing

#56

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...

Your absolute best bet is to sign up for Visual Studio Dev Essentials and try out all the 3 month trials they give. Pluralsight in particular is a really great resource.

https://www.visualstudio.com/dev-essentials/

Re: .NET Core Image Processing

#57

Earlier quoted context omitted.

This isn't my first rodeo with Hacker News, I've unfortunately had negative responses before when sharing my work.

Thank you for your work! I used it with a client that had a System.Drawing impl. Just making thumbnails of uploaded images. It actually was our CPU bottleneck! And then it started crashing when load was high, making us drop or reprocess (which added more load and drops...). With your lib and a few hours of work, all that disappeared and CPU went way down. Thanks! On a side note, users should try to send gratitude to…

That's great to hear, With future updates and a little help I'm sure we can improve the performance further and make us the g0-to library.

And thanks for saying thanks, it is rare and always very much appreciated.

Re: .NET Core Image Processing

#58

Earlier quoted context omitted.

Chat to us on github. Our path drawing public API's are very similar to System.Drawing so we may well be able to provide you with the same functionality.

I'll check it out James. I keep up with you on twitter, wish I had more time to contribute. I have a lot of respect for your hard work though.

Thanks!

Re: .NET Core Image Processing

#60

Great to see the positive comments here. ImageSharp is my baby and it fills me with a lot of confidence that it's something that developers both want and need.

Great to see a more generic pure-.NET image processing library. When I was doing this 5 years ago we basically had AForge.NET which was focused more on correctness of algorithms than speed. I tried to leverage that, but instead ended up with a totally custom image processing pipeline instead -- oh the battles with the GC and unsafe code... Out of curiosity what is your overall vision for the library? Are you looking…

I'd say somewhere in between. I've started with a very high level fluent API since I see that as the most common use case but have exposed a couple of important properties that will allow more low-level operations (pointers etc).

I have also created a generic image pipeline Image that uses all the packed pixel color models used in XNA and Monogame which make it useful in gaming for loading textures.

The dream is that eventually the community will help port a lot of the algorithms over from libraries like Accord, OpenCV and AForge to allow usage in more scientific scenarios. Some of them will fit in the fluent API most will not but the tools should already be within the library to allow porting and usefulness.

Post reply on HN