.NET on Linux – bye, Windows 10 • Hacker News Board

Re: .NET on Linux – bye, Windows 10

#81

Post by Tharre » Mon, Oct 17, 2016, 12:32 PM UTC

ygra wrote: post #73

CWuestefeld wrote: post #70

Earlier quoted context omitted.

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.

You mean pulling the plug instead of shutting down normally? I suppose that'd work but usually you only realize that Windows wants to update _after_ you hit the shutdown button. And powering the machine down in this state will likely result in an unbootable machine.

And good luck fixing that, especially if your hard-drive is encrypted.

Re: .NET on Linux – bye, Windows 10

#82

Post by keyle » Mon, Oct 17, 2016, 12:36 PM UTC

scandox wrote: 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.

I'm glad I'm not the only one that was mad about that. My PC just shut off and started doing updates, in the middle of the day.

My friend said "how much did you pay for Windows 10." I said "nothing, it's free update." then he said "There you go."

Re: .NET on Linux – bye, Windows 10

#83

Post by verbify » Mon, Oct 17, 2016, 12:36 PM UTC

ygra wrote: post #73

CWuestefeld wrote: post #70

Earlier quoted context omitted.

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.

So the message 'do not turn off your computer' is just a suggestion?

Re: .NET on Linux – bye, Windows 10

#84

Post by pjc50 » Mon, Oct 17, 2016, 12:37 PM UTC

douche wrote: post #48

elorant wrote: 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…

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.

This is infeasible when upgrades are monthly or biweekly.

Re: .NET on Linux – bye, Windows 10

#85

Post by verbify » Mon, Oct 17, 2016, 12:38 PM UTC

pritambaral wrote: post #55

wubbfindel wrote: post #46

Earlier quoted context omitted.

If your using Windows 10 Professional or above, you can change the Local Group Policy to prompt you for both downloading and installing updates. For lower versions (like "Home"), there is a way to tell it that your connection is "Metered" and then updated won't be downloaded automatically; but that's not an official method to prevent updates.

For public information: Wired connections cannot be set as "metered". Only wireless ones.

Also for public information: There are hacks that allow wired connections to be set as metered:

http://www.windowscentral.com/how-set-ethernet-connection-me...

Re: .NET on Linux – bye, Windows 10

#86

Post by rafaelvasco » Mon, Oct 17, 2016, 12:40 PM UTC

If it's a pure dev machine than it's already feasible, but not perfect yet. If it's an all purpose machine , ie. gaming, dev, sound vsts etc. Than no. Mainly because of the gaming side unfortunately. I hope Vulkan starts to change that. Btw.: I'm intrigued about the forced updates. Never had them. Computer only updates when i want. Maybe i changed some config when installing the OS.

Re: .NET on Linux – bye, Windows 10

#87

Post by Aardwolf » Mon, Oct 17, 2016, 12:41 PM UTC

verbify wrote: post #83

ygra wrote: post #73

Earlier quoted context omitted.

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.

So the message 'do not turn off your computer' is just a suggestion?

"It's now safe to turn off your computer."

Re: .NET on Linux – bye, Windows 10

#88

Post by morganvachon » Mon, Oct 17, 2016, 12:42 PM UTC

Nursie wrote: post #28

IshKebab wrote: post #17

> 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'm not even sure why he did this, the Ubuntu installer took care of this for me when I installed Xubuntu in UEFI mode this morning. Is the Mint installer unable to deal with UEFI?

I've read numerous posts on support forums about Mint's UEFI support being broken. I have a friend who recently experienced it as well. I turn off UEFI and SecureBoot in my BIOS so I don't have to deal with it, though Slackware does support it if I needed to leave it on. So far Windows 10 hasn't complained about it being turned off on my gaming PC either.

Re: .NET on Linux – bye, Windows 10

#89

Post by Tharre » Mon, Oct 17, 2016, 12:43 PM UTC

egeozcan wrote: post #39

ygra wrote: post #14

Earlier quoted context omitted.

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

I don't get it, one doesn't need the source code to change a few credits strings and pictures. Making Paint.NET closed source is about as effective as game studios putting more and more advanced DRM mechanisms into their games.

I understand why the author is upset, but his cure is worse than the disease.

Re: .NET on Linux – bye, Windows 10

#90

Post by Sir_Cmpwn » Mon, Oct 17, 2016, 12:44 PM UTC

aargh_aargh wrote: post #53

UncleSlacky wrote: post #21

Earlier quoted context omitted.

It was my understanding that Pinta is essentially Paint.NET, and is available on Mac as well as Linux and Windows: https://pinta-project.com/pintaproject/pinta/

Well, it's like comparing a go-kart to a sportscar. Pinta crashes on me a lot and has a fraction of the features.

When was the last time you tried it? I dismissed it for similar reasons when I first tried it, but then I tried it again about a year later and it was fine. Eventually I just manned up and learned how to use Gimp, though.