Live data from Hacker News

Major Linux Problems on the Desktop, 2016 Edition

linuxfonts.narod.ru

141–150 of 384 posts

Re: Major Linux Problems on the Desktop, 2016 Edition

#141
post #136

Earlier quoted context omitted.

Tanenbaum was vindicated two decades ago, but most people have yet to get the memo. A lot are under the impression that basic software design principles apply to everything besides operating system kernels, for some reason. And the myth is highly persistent.

It's quite telling though that most microkernel proponents tend not to be kernel developers.

Right, because most Linux proponents are kernel hackers. It's quite telling that you have no leg to stand on but to resort to hapless diversions. Or I suppose the flood of researchers who have built viable and innovative microkernel-based architectures throughout the decades are all a bunch of phonies?

Re: Major Linux Problems on the Desktop, 2016 Edition

#142
post #92

Earlier quoted context omitted.

Isn't this already happening? http://www.ubuntu.com/certification/desktop/

Well then. It's as if the people at Ubuntu are pretty smart and know what they're doing. :-)

Except they certify systems with lots of problems. Dell had to stop selling their XPS 13 with Ubuntu for a while due to the number of issues.

http://bartongeorge.net/2015/07/20/xps-13-developer-edition-...

Re: Major Linux Problems on the Desktop, 2016 Edition

#145
> Applications (GUI toolkits) must implement their own fonts antialiasing - there's no API for setting system wide fonts rendering. What??! Most sane and advanced windowing systems work exactly this way - Windows, Android, Mac OS X. In Wayland all clients (read applications) are totally independent.

That's interesting, I didn't know that. Is that going to be a huge mess after Wayland transition (which is likely to happen in 2016)? I'm used to fontconfig managing global fonts settings. What will happen in Wayland case?

Re: Major Linux Problems on the Desktop, 2016 Edition

#146

Earlier quoted context omitted.

No, funtionality is important. It doesnt matter how free the software is if it doesnt work. I don't know where you live, but in both the countries I live in you cannot buy linux compatible wifi adaptors over the counter. I can't close my office or loungeroom doors at the moment, because none of the three wifi adaptors I own work with ubuntu, so theres a massive network cable snaking through both. The hardware compati…

"I can't close my office or loungeroom doors at the moment, because none of the three wifi adaptors I own work with ubuntu, so theres a massive network cable snaking through both." Homeplug[1] devices any good? I used a pair of those for a bit to save putting cat 5 in the wall (I'm lazy about DIY). Worked OK but I didn't need super-fast. [1] https://en.wikipedia.org/wiki/HomePlug

They're very expensive compared to wifi, especially compared to their performance, and based on anecdotal reports their lifespan isn't very good. How's your mileage been?

Re: Major Linux Problems on the Desktop, 2016 Edition

#147
post #28

I don't get articles like these. First of all this website is worse than any OS environment I've ever used. So right from that standpoint I sorta gulped a bit before reading on. Graphics driver issues in linux are nothing new, Nvidia a few years back started officially porting drivers to linux but that doesn't solve all the problems. There's also projects like Nouveau; so if you're complaining about linux desktop fro…

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. 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. Until various trouble manufacturers, nVidia first and foremost, decide to start playing ball, their hardware is always going to suck on Linux).

Re: Major Linux Problems on the Desktop, 2016 Edition

#148
post #63

When you think Gnome, you probably think Fedora. Fedora and Gnome are buddy-buddy, and being basically the upstream of RHEL makes it the place to be if you are big on Gnome. KDE has Kubuntu, kind of, since its sponsored by Blue Systems, but there is a huge issue with how KDE is presented to users in that the Ubuntu release cycle has no correlation to the KDE one, and since Plasma 5 has started shipping in Kubuntu tha…

Have you tried manjaro?

Re: Major Linux Problems on the Desktop, 2016 Edition

#149

Earlier quoted context omitted.

> it's not uncommon to have to wait minutes for things to settle down after booting and logging in This is no longer my experience with Windows on an SSD. I'm always a bit shocked when I reboot and I'm back at my desktop in under 30 seconds. On a machine without an SSD, I'm annoyed at how slow everything is -- not just booting.

On what machine btw ? I have a minimal system, but it boots in 4 seconds from BIOS to ion3 (arch). It's funny when the BIOS takes longer than booting. #coreboot

What hardware are you running coreboot on?

Re: Major Linux Problems on the Desktop, 2016 Edition

#150
post #53

Earlier quoted context omitted.

http://www.apple.com/shop/buy-mac/mac-mini?product=MGEM2LL/A... Dont add any extras... its simply not usable on the net Hardware 1.4GHz Dual-Core Intel Core i5 (Turbo Boost up to 2.7GHz) 4GB 1600MHz LPDDR3 SDRAM 500GB Serial ATA Drive @ 5400 rpm Intel HD Graphics 5000 User's Guide (English) Accessory Kit

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.
Post reply on HN