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

Major Linux Problems on the Desktop, 2016 Edition

linuxfonts.narod.ru

Post reply on HN
Print view View original

171–180 of 384 posts

Re: Major Linux Problems on the Desktop, 2016 Edition

#171

Post by condescendence »

awalton wrote: post #147
izacus wrote: post #28

Earlier quoted context omitted.

It's a single location summary of things that still have to be done / are lacking in the project. It's thus useful for contributors to see what needs work, since it's easy to get tunnel vision when working on a project. Don't you have such yearly reviews on your long-running projects?

It's mostly trolly though. I mean, read through some of his complaints: > No high level, stable, sane (truly forward and backward compatible) and standardized API for developing GUI applications Really? He's calling Win32 sane and stable ? The API where they're constantly having to introduce terrifying new hacks to stay bug compatible with themselves and still failing ? Most of it's the same trolls we hear every day.…

Thank you, that last part said it better than I ever could.

>A lot of it is good, well-founded bitching that the Linux community can absolutely do nothing about (we don't have access to hardware specifications we don't have, that simple

Re: Major Linux Problems on the Desktop, 2016 Edition

#172

Post by [deleted] »

awalton wrote: post #147
izacus wrote: post #28

Earlier quoted context omitted.

It's a single location summary of things that still have to be done / are lacking in the project. It's thus useful for contributors to see what needs work, since it's easy to get tunnel vision when working on a project. Don't you have such yearly reviews on your long-running projects?

It's mostly trolly though. I mean, read through some of his complaints: > No high level, stable, sane (truly forward and backward compatible) and standardized API for developing GUI applications Really? He's calling Win32 sane and stable ? The API where they're constantly having to introduce terrifying new hacks to stay bug compatible with themselves and still failing ? Most of it's the same trolls we hear every day.…

[deleted]

Re: Major Linux Problems on the Desktop, 2016 Edition

#173

Post by daave »

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.

Re: Major Linux Problems on the Desktop, 2016 Edition

#174

Post by copperx »

nextos wrote: post #150
condescendence wrote: post #82

Earlier quoted context omitted.

Not usable on the net?? Shit this was close spec'd to my compiling machine a few years ago.

I think the issue is usually really poor quality HD supplied by Apple on low end machines.

It's slow, but not poor quality.

Re: Major Linux Problems on the Desktop, 2016 Edition

#175

Post by SEJeff »

archimedespi wrote: post #118
Animats wrote: 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…

> The monolithic Linux kernel is just too big. What is it now, 20,000,000 lines? There's no hope of debugging that. It shows. The Linux kernel is about 20MSLOC. The Windows kernel is about 50MSLOC. IIRC, OS X used to be ~80KSLOC. Problems with debugging are endemic to any monolithic kernel. Neither Windows nor OS X is easier to debug technologically , but Microsoft and Apple both have many employees and lots of money…

Not so sure I really disagree. If I had to guess, I'd think there are a lot more people working on the Linux kernel in aggregate than on either the Windows kernel or the OS X kernel.

Re: Major Linux Problems on the Desktop, 2016 Edition

#176

Post by SEJeff »

vezzy-fnord wrote: post #160
ris wrote: post #152

Earlier quoted context omitted.

"Right, because most Linux proponents are kernel hackers." They don't have to be. All they have to do is not go around smugly suggesting they know better than kernel developers and they're ok in my books. Incidentally, precisely how many of those research kernels have become widely used, mainstream kernels capable of high-throughput? And do you really think it has turned out that way because the whole industry is ful…

I'm not sure what fantasy world you live in where the software industry is always adopting the most technologically superior solutions by default. No industry works like this. YMMV on mainstream (they are widely adopted, though), but: OKL4, PikeOS, QNX... It's quite obvious you have no background on the issues and are using this as an opportunity for provocation.

You missed Tron/ETron and the *tron variants, which is likely the most used kernel in the world.

Re: Major Linux Problems on the Desktop, 2016 Edition

#177

Post by nextos »

agumonkey wrote: post #166
nextos wrote: post #149

Earlier quoted context omitted.

What hardware are you running coreboot on?

I'm not (at least for now, I have a spare compatible thinkpad), I was just implying that the BIOS is now the bottleneck.

Oh, I see. I also ran Arch (on MBA 2012, perfect compatibility). It's wicked fast to boot using the kernel as an EFI payload (efistub).

Re: Major Linux Problems on the Desktop, 2016 Edition

#178

Post by mikelward »

crgabrieljr wrote: post #8

Tried double-tapping in the article text to get it to reflow, and got one of those bogus popups claiming my phone is infected with a virus. Thanks for trying to make my new year interesting. :-(

Flagged the link. But surely I'm not the first. How does this malicious post stay up for four hours?

Re: Major Linux Problems on the Desktop, 2016 Edition

#179

Post by AnimalMuppet »

vezzy-fnord wrote: post #170
AnimalMuppet wrote: post #164

Earlier quoted context omitted.

> they are widely adopted, though For some definition of "widely". And feel free to stop adding personal attacks to your comments. They do not enhance the credibility of your posts.

"Widely adopted" is not a synonym for "known by the average consumer".

I know it's not. And I know about QNX, at least (the others are new to me).

And I know that you didn't claim they are mainstream, so we may be quibbling about where we draw lines around the word "widely". But...

What's the installed base of systems running QNX, say? (Throw in the others if you wish.) Estimates are acceptable, too, if you don't have hard numbers.

Re: Major Linux Problems on the Desktop, 2016 Edition

#180

Post by copperx »

JustSomeNobody wrote: post #73
chx wrote: post #49

I have one more which this article doesn't mention: Bluetooth. It's an extremely fragile house of cards (as far as I can figure, there are a few kernel modules, dbus, a bluetooth daemon and pulseaudio involved) and every upgrade you roll is extremely risky. Currently my BT works but after a day or so uptime it will simply stop working and nothing short of reboot helps. (More https://bbs.archlinux.org/viewtopic.php?id…

I constantly battle Bluetooth issues on every platform. It sucks and needs to die.

This is true even on my Mac with wireless Apple accessories. Pairing issues galore if I have to change the batteries.
Post reply on HN