Live data from Hacker News

Major Linux Problems on the Desktop, 2016 Edition

linuxfonts.narod.ru

301–310 of 384 posts

Re: Major Linux Problems on the Desktop, 2016 Edition

#301

Earlier quoted context omitted.

Is there source available for this or QNX?

Not for my stuff, I do have it (obviously) but it is definitely not worth sharing in the state it is in. Essentially it is a kernel, some userland device drivers and a rudimentary (but functional) network stack cobbled together from various bits and pieces. The toolchain was GCC and djgpp to bootstrap the development until it was capable of self hosting. It would need serious work (several man-months) before it could…

Did anyone here manage to snag the code before the open source program was shut down?

Re: Major Linux Problems on the Desktop, 2016 Edition

#303
post #18

I've been using Linux on the desktop daily since about 1998. It may look a little prettier today, but I find it crashes and freezes a whole lot more these days.

I have run Ubuntu and RedHat on multiple hardware, Desktop, not just server, dozens of machines the past 10 years. Freezing on all those hardware combinations was never a problem. Crashing was absolutely never a problem.

Re: Major Linux Problems on the Desktop, 2016 Edition

#304
post #18

I've been using Linux on the desktop daily since about 1998. It may look a little prettier today, but I find it crashes and freezes a whole lot more these days.

In my experience the kernel and drivers are better than ever, but the desktops are awful and have grown worse. When KDE 4 came out I went to simple window managers like i3 and fvwm. These are extremely stable but things as simple as looking at photos in file manager are painful, and forgetting how to change the clock when I fly to a new timezone is frustrating.

Unity, like it or not, is quite stable.

Re: Major Linux Problems on the Desktop, 2016 Edition

#305

Earlier quoted context omitted.

That's a really interesting post, and I'm glad I read it. I find myself agreeing with Linus quite a bit, and until now I did not realize that there is programming being done without step by step debugging. And I think Linus's claims that people would be more careful when first designing and writing code if they didn't have a debugger to help them going forward makes a lot of sense. Unfortunately I work with too many…

The point is his view about kernel debuggers is complete nonsense, and I'm baffled that you and so many others could ever take it seriously. Yes, people would be more careful without debuggers, the same way they'd be more careful with cooperative multitasking hanging the system when they forget to yield. That doesn't make it good.

And yet the kernel that he has created and is developed with his methods, it runs on the greatest variety of systems, from toasters right up to being the predominant OS in the top 500 supercomputers (by a wide margin).

Re: Major Linux Problems on the Desktop, 2016 Edition

#306

Earlier quoted context omitted.

The point is his view about kernel debuggers is complete nonsense, and I'm baffled that you and so many others could ever take it seriously. Yes, people would be more careful without debuggers, the same way they'd be more careful with cooperative multitasking hanging the system when they forget to yield. That doesn't make it good.

Quite often I read posts by Linus and find myself unable to take him seriously. He's arrogant, abrasive, and some of his opinions (security, debuggers apparently) are ridiculous.

No, he's not. He is a little arrogant - it's hard to be such a significant tech lead without being so - but if you actually read what he writes, he's not actually that abrasive.

What happens is that some sensationalist idiot will see Torvalds lose his patience and post an angry retort to someone, and post just that response to places like HN, completely out of context. I've lost count of the number of times it's happened here, when everyone's tutting about Torvalds' behaviour and how he's "so aggressive right out of the gate", when no-one looks at the thread history to see him being patient and explaining things.

In any case, zero of the tech heads from Jobs on down satisfy your demands to be taken seriously. I really don't understand why Torvalds gets held to this higher standard of hippie-level friendliness when people don't expect the same from other major tech project managers. I mean hell, Jobs was adored for having opinions that people considered ridiculous.

Re: Major Linux Problems on the Desktop, 2016 Edition

#307
post #246
post #62

He's right. Many of the driver problems come from the fact that Linux finally worked on the desktop about the time desktop machines were replaced by laptops. Desktops with slots tended to have relatively well-defined hardware, and plugging in third party hardware was normal. This is much less true for laptops. OS development for laptops requires that laptop. It needs a Q/A organization which has one of everything you…

> Microsoft got drivers under control with the Static Driver Verifier, which uses automatic formal proofs of correctness to determine whether a driver can crash the kernel. ... Linux has no comparable technology. That's a pretty cool idea (also similar to the static verification in NaCl.) Is there a reason one couldn't implement a static verifier for Linux drivers? Would the problem be harder in any sense for Linux,…

not really, people are doing some experiments with linux kernel as well. https://www.usenix.org/system/files/conference/osdi14/osdi14...

Re: Major Linux Problems on the Desktop, 2016 Edition

#308

Earlier quoted context omitted.

The point is his view about kernel debuggers is complete nonsense, and I'm baffled that you and so many others could ever take it seriously. Yes, people would be more careful without debuggers, the same way they'd be more careful with cooperative multitasking hanging the system when they forget to yield. That doesn't make it good.

And how people would be more careful drivers of you replaced airbags with a metal spike. You would wind up with more careful drivers, but anyone who thinks that's the only goal is misguided.

I think the better analogy would be driving with a very very dirty windshield. Or a slippery stealing wheel.

It's not that absence of debugger would make you (in Linus' opinion) more careful because it's risky, but because it's really inconvenient.

Re: Major Linux Problems on the Desktop, 2016 Edition

#309
post #204

One problem specific to gaming: Adjusting mouse pointer speed and acceleration is a huge pain. I've tried SteamOS for gaming but especially playing FPS type games is really bad with acceleration. Disabling it usually requires X.org config changes and knowledge of some semi-arcane acceleration math. It's doable, but certainly not in any way easy.

If you're just using xset, you're missing out massively.

Use xinput instead, it gives you full access to all of X's acceleration profiles and all the parameters you can tweak with them.

http://www.x.org/wiki/Development/Documentation/PointerAccel...

I cannot agree more that said xinput interface could do with a UI though. Not because I hate the commandline but because repeatedly entering long commands with numbers just kills it for me - there's no rapid feedback loop.

And so I continue to avoid using my ThinkPads' Trackpoints because I can never get them to a point where they aren't a strain to use.....

Re: Major Linux Problems on the Desktop, 2016 Edition

#310
post #173

When visiting this blog post on my Android phone, the ads (or something) redirect me to a page with popups telling me my phone has a virus and encouraging me to install an app to 'clean' it, using Google branding on some dodgy domain. I seem to get a different one each time. Reported it at https://www.google.com/safebrowsing/report_phish/ but mentioning here so that others don't fall victim to it.

The site is now blacklisted for Chrome users. I've emailed the author letting him know about this issue.
Post reply on HN