Live data from Hacker News

.NET on Linux – bye, Windows 10

piotrgankiewicz.com

31–40 of 290 posts

Re: .NET on Linux – bye, Windows 10

#33
post #2

I still have to wait for sql server to be ported. But my day job as a c# dev is the only thing keeping me on windows at the moment.

You could use MySQL? It has full EF7 support AFAIK.

After years MySQL still not implemented async for their .NET driver, only slow cheap wrappers. However, PostgreSQL has full async support in their free .NET driver...

Re: .NET on Linux – bye, Windows 10

#34
post #29
post #23

Earlier quoted context omitted.

I fail to see why snark is warranted here. Linux should not have to conform to Microsoft anti-competitive practices. UEFI is a mess to deal with because Microsoft wanted to lock users. Yes, this will prevent Linux on the desktop. That doesn't mean it will never happen.

I don't even understand why this bloody "desktop" paradigm has to be maintained.

I think it can be hard for us (people who get a lot of screen time, spend a lot of time coding in 2D) to imagine that the "desktop" paradigm is already dead. Mobile/voice/AR is killing it. Granted the desktop UI metaphor will probably never die, just like the command line hasn't. But the front-and-center desktop is fading away...

Re: .NET on Linux – bye, Windows 10

#35
post #12

Earlier quoted context omitted.

This. Paint.NET is what I'm missing on my Mac so much.

Paint.Net is good, indeed. Let Krita be your new friend. https://krita.org/en/

In the past I didn't like the fact that Paint.NET isn't available on Linux. After using editors like Krita, I realized I didn't miss Paint.NET as much as I missed an image editor that isn't GIMP.

Re: .NET on Linux – bye, Windows 10

#36
post #20

> Before I did manage to install a fresh system on my laptop I had to disable UEFI, create valid partitions with special flags etc. it took me a while to figure this out, yet it wasn’t that difficult. Ha, right here is why "the year of the Linux desktop" will never happen. It's basically a kit car. Some people may find it "not that difficult" to weld a chassis together and rebuild an engine, but it's never going to b…

I wonder what he fucked up to make this necessary. Modern Linux distributions work fine with UEFI and create the necessary EFI System Partition itself.

Unfortunately not on every UEFI implementation ...

Re: .NET on Linux – bye, Windows 10

#37
I've been spending some time putting together a framework for .NET Core API/platform development. The main problem with it currently is the lack of compatible libraries - I've had issues with DI containers, cloud provider libraries, AOP frameworks and more. Not to mention EF Core is still way off in terms of production viability. ASP.NET Core is very tasty as a plus.. and there's always Mono to fill the gap in terms of "full framework" missing functionality.

Re: .NET on Linux – bye, Windows 10

#38
post #34
post #29

Earlier quoted context omitted.

I don't even understand why this bloody "desktop" paradigm has to be maintained.

I think it can be hard for us (people who get a lot of screen time, spend a lot of time coding in 2D) to imagine that the "desktop" paradigm is already dead. Mobile/voice/AR is killing it. Granted the desktop UI metaphor will probably never die, just like the command line hasn't. But the front-and-center desktop is fading away...

I'm not so sure. If you took a drink every time you read "sorry for the short answer, I'm on mobile, I will edit it when I'm back on a real computer" on HN or reddit, your liver would die faster than Windows Phone. There's still a place for devices with lots of screen space and real input devices, and not just in the IT community (unlike with command line interfaces).

Re: .NET on Linux – bye, Windows 10

#39
post #14
post #7

Earlier quoted context omitted.

Depends on the GUI framework it uses. GDI actually exists for Linux (at least for Mono), but it's not really something you want to use in production. Windows Forms doesn't exist (yet). IIRC that's what paint.net uses, so you're out of luck. Third party toolkits like GTK#, wx.NET or QtSharp will work on both OSes.

I remember that ages ago the Mono team used Paint.NET as a testbed for how complete and usable their System.Windows.Forms and System.Windows.Drawing implementation was. But back then Paint.NET was still open source. By now the source code isn't available anymore and it has grown a lot of things that are implemented in native code for performance (set operations on selection regions) or talking to things that have no…

Oh I didn't know that Paint.NET closed source. I found a blog post about the decision, an interesting read. Here it is:

https://blog.getpaint.net/2007/12/04/freeware-authors-beware...

Post reply on HN