Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

.NET on Linux – bye, Windows 10

piotrgankiewicz.com

Post reply on HN
Print view View original

131–140 of 290 posts

Re: .NET on Linux – bye, Windows 10

#131

Post by coldpie »

gwbas1c wrote: post #123
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.

The updates drove me away from Windows 10 years ago. I still have a windows machine for occasional games. What drives me nuts is "Install Updates and Shut Down" leads to a 15 minute boot time. WTF? I thought all that was supposed to finish before the computer turned off???

What games keep you on Windows? It is my job to solve that problem, we'd love to help you out.

Re: .NET on Linux – bye, Windows 10

#132

Post by V-2 »

jasonkostempski wrote: post #113
V-2 wrote: post #111

Back in the Windows XP days, there was a way of halting forced updates by killing a certain process. I had it as a simple batch file on my desktop. Every time it would come up with "your PC gets restarted in 15 minutes", I'd just double click on it and carry on undisturbed.

Was that really necessary? As far as I remember, XP let you choose to not install updates automatically.

I can't really argue because it was a while ago, but if I recall some of them were considered critical and you could postpone them time and time again, but not really disable them

Plus I wasn't really opposed to safety updates as such, and wouldn't want to take the burden of remembering about them upon myself - it's just the arrogant, disruptive manner in which they are delivered that never sat well with me (if with anybody...)

Re: .NET on Linux – bye, Windows 10

#133

Post by cash3wz »

creshal wrote: post #105
lmm wrote: post #67

Earlier quoted context omitted.

What difference does that make? You don't have to run KDE (heck, I use it on windows). Yes its UI is a separate library from the specific program - any well-factored program will do the same, whether it exposes the separation or not.

> What difference does that make? • It's more packages I need to download. Doubly annoying because 95% of the packages are just "thin wrapper around foo, because we're too hipster to use libraries directly like peasants ". • It installs system-wide services I have to disable/mask just so other programs don't mistakenly use them because they think I run KDE and they have to integrate into it. • Oh wait, I can't disabl…

I agree with you for point 2 & 3, I also hated installing KDE apps for this exact reason.

But I can't agree on the first one.

I have not checked what these exact thin wrappers are, but most of the time thin wrappers are really useful for testing and switching to another library without being tangled in the old one.

It pretty much follow the "D" (Dependency inversion principle) in the S.O.L.I.D. principles: "Depend upon Abstractions. Do not depend upon concretions.”.

Again, I have not checked the KDE libs you talk about, so I'm assuming this is what these wrappers are used for.

(Source : https://en.wikipedia.org/wiki/Dependency_inversion_principle & https://en.wikipedia.org/wiki/SOLID_(object-oriented_design) )

Re: .NET on Linux – bye, Windows 10

#134

Post by coldpie »

Tharre wrote: post #89
egeozcan wrote: post #39

Earlier quoted context omitted.

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.

Yeah, closed source tooling is garbage. I need to be able to fix the tools I use, or customize them for my purposes.

Re: .NET on Linux – bye, Windows 10

#135

Post by ocdtrekkie »

Tharre wrote: post #81
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.

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.

As a Windows system admin, I can confirm this is incredibly rare. Windows is pretty darn good at recovering from broken update states.

Re: .NET on Linux – bye, Windows 10

#136

Post by scandox »

dotancohen wrote: post #71
aargh_aargh wrote: post #5

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.

single-window mode! That is so much better. Don't know how I missed that for so long.

Re: .NET on Linux – bye, Windows 10

#137

Post by ocdtrekkie »

gwbas1c wrote: post #123
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.

The updates drove me away from Windows 10 years ago. I still have a windows machine for occasional games. What drives me nuts is "Install Updates and Shut Down" leads to a 15 minute boot time. WTF? I thought all that was supposed to finish before the computer turned off???

"The updates drove me away from Windows 10 years ago."

This is amazing because Windows 10 is barely more than a year old!

Re: .NET on Linux – bye, Windows 10

#138

Post by cesarb »

GrumpyYoungMan wrote: post #129
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.

> The real story here is the forced updates. How do people who are planning demos and presentations handle this? It's my worst nightmare. Manually run the update check every 2-3 days and run it again two hours before the presentation. Any updates that come out in that two hour window will allow you at least one delay. Come on, folks, this isn't exactly rocket science here. Keep your OS up to date and, surprisingly en…

> and run it again two hours before the presentation.

Wouldn't two hours be too short to fix any problems caused by the update?

Re: .NET on Linux – bye, Windows 10

#139

Post by roblabla »

GrumpyYoungMan wrote: post #129
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.

> The real story here is the forced updates. How do people who are planning demos and presentations handle this? It's my worst nightmare. Manually run the update check every 2-3 days and run it again two hours before the presentation. Any updates that come out in that two hour window will allow you at least one delay. Come on, folks, this isn't exactly rocket science here. Keep your OS up to date and, surprisingly en…

OS updates (or any update that potentially takes more than 2 minutes) shouldn't ever be forced. It's just terrible. Sure, there should be some prominant prompts saying "Plz update me" from time to time (so the average joe's computer isn't terribly out of date). But don't force me to update in the middle of prez. Because clearly, I'm best placed to know what's the best time for my computer to become an expensive paperweight.

Re: .NET on Linux – bye, Windows 10

#140

Post by hedora »

GrumpyYoungMan wrote: post #129
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.

> The real story here is the forced updates. How do people who are planning demos and presentations handle this? It's my worst nightmare. Manually run the update check every 2-3 days and run it again two hours before the presentation. Any updates that come out in that two hour window will allow you at least one delay. Come on, folks, this isn't exactly rocket science here. Keep your OS up to date and, surprisingly en…

It is seriously that bad now? You have to touch windows update three times a week?!?

That sounds like an even bigger time sink than the whole "find a new Debian derivative because Unity breaks the alt key, and systemd breaks everything else" thing.

Post reply on HN