Quite a few of the points only cause problems to closed source development whilst having a positive effect on open source development. I don't think it's objectively a bad thing.
Major Linux Problems on the Desktop, 2016 Edition
181–190 of 384 posts
Re: Major Linux Problems on the Desktop, 2016 Edition
#182When 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.
Yep same here.
Re: Major Linux Problems on the Desktop, 2016 Edition
#183When 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?
I'm talking about a consumer grade implementation of KDE I can recommend people over Windows. Manjaro has no MAC, has an unstable release cycle, doesn't have the manpower to maintain that testing window I describe, and is reliant too much on the AUR to a fault. Arch gets away with the AUR because the audience is power users. You cannot push a consumer grade distribution with access to arbitrary software installers that have system level access that anyone can upload.
Like I said, it would take commercial level support and infrastructure and work. To make consumer grade Arch would take sallaried testers and auditors of the software "store" that the AUR would be, except what you would be doing is maintaining your own repository of AUR packages you trust and maintain yourself, and would need some means for users to get their software approved. And like I said, you need security profiles for every package, and pacman doesn't support per-user application installs, and has nascent delta support (that is there, but sadly not mainstream).
Manjaro is a start. Netrunner Rolling is too. Chakra is a third. But none take the task seriously enough, because they are made to be less rapid Arch's, not a consumer product. Its simply not something a hobbyist community can accomplish because inherent to being a community distro is the inability to design and target those outside it effectively. Its simply a problem that requires money and commercial support that could be easily picked up and done by any company that wants to take it on but it isn't something the community can make themselves.
Re: Major Linux Problems on the Desktop, 2016 Edition
#184> Windows, in some regards, is even worse than Linux and it's definitely not ready for the desktop either.
uh huh.
Re: Major Linux Problems on the Desktop, 2016 Edition
#185Earlier quoted context omitted.
"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.
BlackBerry doesn't seem to give out hard numbers for installations, but they have overviews of the market and lists of particular customers per category here: http://www.qnx.com/solutions/industries/automotive/index.htm...
It's not only worth looking how many, but what. They're in vehicles, medical devices, industrial automation, military and telecom. Those are all areas where blunders lead to loss of lives, not just annoying downtimes. Insofar as infotainment and telematics is concerned, they estimate at 60% of 2011, so it's likely your car runs QNX.
Re: Major Linux Problems on the Desktop, 2016 Edition
#186Earlier quoted context omitted.
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.
BlackBerry doesn't seem to give out hard numbers for installations, but they have overviews of the market and lists of particular customers per category here: http://www.qnx.com/solutions/industries/automotive/index.htm... It's not only worth looking how many , but what . They're in vehicles, medical devices, industrial automation, military and telecom. Those are all areas where blunders lead to loss of lives, not ju…
OK, if it's in cars (even if only one CPU per car, or even only in high-end cars), then yes, that certainly is "widely used". (In terms of numbers shipped, not necessarily in terms of "design wins" - but then, Windows doesn't have that many "design wins" either.)
Re: Major Linux Problems on the Desktop, 2016 Edition
#187Earlier quoted context omitted.
BlackBerry doesn't seem to give out hard numbers for installations, but they have overviews of the market and lists of particular customers per category here: http://www.qnx.com/solutions/industries/automotive/index.htm... It's not only worth looking how many , but what . They're in vehicles, medical devices, industrial automation, military and telecom. Those are all areas where blunders lead to loss of lives, not ju…
OK, if it's in cars (even if only one CPU per car, or even only in high-end cars), then yes, that certainly is "widely used". (In terms of numbers shipped, not necessarily in terms of "design wins" - but then, Windows doesn't have that many "design wins" either.)
So now you're moving the goalposts with "design wins". Just what are the design wins of a SysV Unix clone like Linux, pray tell? It's hard not to be on the offensive when you seem to beg for it. Where did the Windows comparison come from?
The design wins, of course, should be obvious to anyone willing to do a modicum of research.
Re: Major Linux Problems on the Desktop, 2016 Edition
#188Earlier quoted context omitted.
> 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…
Kernel debuggers exist. Of course, we're all aware of Linus' opinion on the matter.
I'm not, does he not like kernel debuggers or something?
Re: Major Linux Problems on the Desktop, 2016 Edition
#189Earlier quoted context omitted.
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.
> 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.
Every iPhone now shipping and most Android devices too I believe are running their main operating system kernel as a layer on top of an L4 kernel. They mostly handles low level security and the cell modem and stay out of the way except for that. Still, I think that should certainly count as widely adopted.
Re: Major Linux Problems on the Desktop, 2016 Edition
#190Earlier quoted context omitted.
QNX is making a comeback, via robotics and automatic driving. All the Boston Dynamics robots ran QNX; all the hydraulic valves were coordinated by one CPU. The valve servoloop ran at 1KHz and the balance loop at 100Hz. QNX is behind some automotive dashboards, and they're moving into automatic driving. They have some big announcement coming at CES in January. But nobody runs QNX on the desktop any more. This year, th…
I have a barebones re-implementation of QnX for the 32 bit x86, I don't have time enough to clean it up or port it to the 64 bit model. It blew the doors off the competition back in the day (about 2 decades ago), 200K context switches per second on a 33 MHz 486. Fast enough for real time control of all kinds of hardware and with a seamless path from a self hosting desktop environment to embedded hardware. I never got…
Is there source available for this or QNX?