Live data from Hacker News

.NET on Linux – bye, Windows 10

piotrgankiewicz.com

71–80 of 290 posts

Re: .NET on Linux – bye, Windows 10

#71

Can I have Paint.NET on Linux yet?

No.

But honestly, spend a weekend learning Gimp. It's a pain, yes I know, but I'm really glad that I did. The official tutorials are wonderful. You'll be able to do so much more, and do it so much better, and even a bit quicker than you could in Paint.NET that you'll wind up preferring Gimp even in Windows.

Just be sure to use single-window mode.

Re: .NET on Linux – bye, Windows 10

#72
post #43

Windows 10 is a clusterfuck of an OS. Installed it on my dad’s PC, a simple machine with browsing software and a few arcade games. Didn’t go with the full install, instead did an upgrade from Win7. Everything was honky dory until it downloaded a ginormous 1GB update. The update failed and now every time he shuts down the update tries to install again. It takes north of five minutes to shut down. Install, fail, rollba…

The most sad thing for me is how Windows is such a given for PC gaming. :( It wouldn't have to be like this, there's nothing saying it should be a huge gaming OS, so it's too bad it is. I wish Valve would have been more successful with Steam OS. That would have fixed everything at least for me. As someone who otherwise likes amateur photography and programming, Linux is just as good or better at everything else with e.g. Darkroom and RawTherapee for photography, and programming being a given. Lightroom isn't even fun to use with its obnoxious enforced workflow and business model, just too bad it's so big on the plugin scene.

Windows is hanging onto this thin line, but it's a damn strong line for many.

Re: .NET on Linux – bye, Windows 10

#73
post #30

The real story here is the forced updates. How do people who are planning demos and presentations handle this? It's my worst nightmare.

Twice I've been bit by the unexpected updates during shutdown during a power failure . At home my UPS is only good for 5 minutes, so I want to shut down as soon as the power goes down. I do that, and Windows starts on "Installing 17 updates", with absolutely no way for me to intervene. And powering down in the middle of OS updates has to be about the worst possible time for it.

It will simply roll back the half-finished updates and retry the next shutdown. Those things are done transactional. Powering down won't hurt it.

Re: .NET on Linux – bye, Windows 10

#74
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 don't think much work is done or will be done on mobile. For consumers perhaps. As soon as you need to do anything serious with a spreadsheet or code, you can forget the mobile. It's not a iOS vs Windows functionality thing. It's a form factor problem.

Re: .NET on Linux – bye, Windows 10

#75
post #30

The real story here is the forced updates. How do people who are planning demos and presentations handle this? It's my worst nightmare.

Hibernate. I don't reboot more than once a month or so. It doesn't do on-bootup updates when you resume from hibernation.

Re: .NET on Linux – bye, Windows 10

#76
post #49
post #48

Earlier quoted context omitted.

Trying to upgrade an operating system is almost always a good way to ensure you're going to have a bad time. Copy any files you care about off, wipe the disk, and install from scratch. This is also usually worth doing with an OEM machine, to get rid of all the crap and weirdly configured partitions they set them up with.

I agree but I'm mildly surprised when an upgrading OSX or Linux instead of a fresh install always works fine.

That's not true for Linux - I've had many instances where repo refs broke because they didn't have packages for updated version, or where the new version kernel introduced a bug breaking my WiFi, audio, graphics, or random stuff failing - it's probably worse than doing a Windows upgrade.

I've only used macs for a year and only did 10.5 -> 10.6 which went smooth IIRC. Mac approach of owning the hardware and the OS certainly has it's advantage - being able to clone image to an external HDD from my MB pro and then boot a iMac to the exact same image is a magical experience. Setting up a master image on my laptop and then redeploying to an office of 40 something various mac devices using IP broadcast and doing it in an hour - hearing that apple chime 40 times was really cool :D

Re: .NET on Linux – bye, Windows 10

#77
post #62
post #57

Earlier quoted context omitted.

Good luck running desktop GNU/Linux stuff properly on Android/Linux. The set of APIs exposed to the NDK is so constrained that Google can replace the Linux kernel with something else and only OEMs writing drivers will notice.

It's really not too bad with root. Although the permissions and selinux stuff will trip you up a lot.

Yes, but those aren't the devices normal users get on the store.

Re: .NET on Linux – bye, Windows 10

#78
post #30

The real story here is the forced updates. How do people who are planning demos and presentations handle this? It's my worst nightmare.

In Task Scheduler, expand the Task Scheduler tree to go to Task Scheduler Library -> Microsoft -> Windows -> UpdateOrchestrator -> Disable Reboot task

In the folder %Windows%\System32\Tasks\Microsoft\Windows\UpdateOrchestrator remove write permissions for all users from the reboot file.

https://techjourney.net/permanently-disable-prevent-automati...

Re: .NET on Linux – bye, Windows 10

#79
post #54
post #43

Windows 10 is a clusterfuck of an OS. Installed it on my dad’s PC, a simple machine with browsing software and a few arcade games. Didn’t go with the full install, instead did an upgrade from Win7. Everything was honky dory until it downloaded a ginormous 1GB update. The update failed and now every time he shuts down the update tries to install again. It takes north of five minutes to shut down. Install, fail, rollba…

The OS is great, only macOS offers a similar OO ABI for the OS stack. Also I do have quite a few war stories from failed GNU/Linux updates, that eventually lead me to always keep /home on a separate partition and wipe everything else.

I think you are right that big updates on Linux are just as difficult on Windows, but the point is that you shouldn't have to deal with the issue.

1) Yes, all OSes should respect something like the root/home separation and let you just nuke the system. But this is a lot easier in a world where all your apps are just an apt-get away.

2) In comparison to MS, every Linux seems to be a "rolling release". When we use linux we like it that we always have a not-too ancient version of GCC. But when Windows 10 starts upgrading continuously, sinister stuff gets mixed in.

Re: .NET on Linux – bye, Windows 10

#80
post #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…

I'm having the same problems and have came to the conclusion that .NET Core isn't really ready for application development. Maybe by 2.0, but this 1.0 release has just enough for library developers to port over to the new framework. Without those libraries, app development is severely hampered.
Post reply on HN