Who are these engineers who design the new, smaller manufacturing processes? I'm quite sure Intel or TSMC will reward you quite gratuitously if you are an engineer in a research team that makes 10nm feasible. Can you imagine, those guys change the world.
I did not mean what software currently is, but how much horsepower is actually needed for a certain application, if programmed in an optimized fashion. Of course you lose performance if you make facepalmy things like make applications inside web browser or within.NET Framework.
For an ordinary joe it won't matter that much. Most of the services he uses (Facebook, Twitter, Spotify, Netflix, Skype, lightweight gaming) could be implemented even on a Pentium II with a little bit of optimization. Even Microsoft does not bother artificially bloating their operating system anymore.
I thought the idea of Minix is to intentionally keep it barebones so that it can be used for education and so that it can be fully understood by single person. It's certainly a cool kernel though.
Oh and Linux isn't quite monolithic, for example all USB devices have user mode drivers. Just the basic read/write functions are in the kernel.
Can the GPU drivers be moved to userspace as well? Windows has done this since Vista, and a GPU driver crash results only in a small notification telling that the driver restarted. Isn't Linux all about these kind of hi-tech features?
For Windows 10 users: if you want to get these test builds, go to Settings -> Update & security -> Windows Update -> Advanced options -> Get Insider Preview builds. I'm just putting this here as many might not be aware about this possibility.
You're the one talking out of your ass. Of course OS X does not feature touch support, embedded features, or server features, because Apple does not make hardware with those features. Also, how does that have anything to do with robustness?
It's amazing that people still think that the open source community is some kind of magical software mill at which you can throw software and expect it to come out polished. There's a lot of broken stuff out there that no one bothers to touch. In this case the even bigger problem is that the "community" quite does not have the production capacity compared to a team of professional full-time GPU engineers. Especially when GPU driver code is extremely challenging.
In previous Slashdot articles on the topic, I found it suspicious that there was suddenly so many articles in the news that were like "sitting kills you, as bad as smoking". I said that standing desk makers must love the trend.
I got a bunch of angry replies, saying that I am ignorant for not believing the scientific evidence.
Linux is stuck in the unfortunate spot of hoping things work as advertised.
How can you be sure that it's only that, and that Linux does not also contain crappy code? It's a bit too easy to just blame OEMs.
For example, the multiple backlight events problem could be pretty easily avoided by simply leaving the backlight adjustment responsibility only to the GPU driver. There's nothing hacky about that. A lot of machines can already be fixed with "acpi_backlight=native".
Of course, but filesystems are a solved problem already. Always reinventing them takes up a lot of testing time. Even Microsoft puts much less resources into filesystems: they occasionally add a small incremental update to the tried and trusted NTFS, and that's that.
If Dell delivers laptops with Linux preinstalled, then it's their problem, they got the hardware to reproduce it and they got paid people working on it.
According to a Reddit comment, even Dell does a partial job in Linux quality assurance. The touchpad supported palm detection, but the feature was not implemented. I'm pretty sure it works if you put Windows on the same computer. How much other small things are there hiding in that laptop that do not work properly in Linux when you take a closer look?
I recently did a quick survey in Reddit on people's experience on suspend/hibernate, and I may summarize it simply by saying that Linux is not the best performer in this area.:D It's a shame that such an important laptop feature works so poorly. Some might say that it's because OEMs do not "support ACPI spec properly", but in practice most PCs don't... It could be more practical to just find the patterns that Windows uses, and imitate them.
One really weird thing is also that backlight adjustment requests are sent to both ACPI and GPU, which causes double backlight adjustment events on many laptops.
People fight about SystemD, various open source licenses, differences between DEs, filesystems, but at the same time there's these fundamental problems which should get way more attention. Sometimes it feels like we are in a house arguing what kind of wallpapers bring the best experience, while that same wall is infested with mold inside.
Some people still talk like this is supposed to be the hi-tech kernel that breathes new life to my PC. Are they blind to all this stuff happening?
The fail0verflow's GitHub repository contains the needed Radeon patches as well. Basically they only had to add the correct PCI ID into the driver to get started. It seems that further tweaks are needed to make it perfect though.
Facepalm. It seems that both I and Timothy are sleeping on the wheel.:D
Anyway, I would also add to the summary that you need some another way to actually make the kexec call. Over at PSXHAX there was posted a new BadIRET exploit last Wednesday. Maybe it works.
Slashdot Mirror
Who are these engineers who design the new, smaller manufacturing processes? I'm quite sure Intel or TSMC will reward you quite gratuitously if you are an engineer in a research team that makes 10nm feasible. Can you imagine, those guys change the world.
I did not mean what software currently is, but how much horsepower is actually needed for a certain application, if programmed in an optimized fashion. Of course you lose performance if you make facepalmy things like make applications inside web browser or within .NET Framework.
For an ordinary joe it won't matter that much. Most of the services he uses (Facebook, Twitter, Spotify, Netflix, Skype, lightweight gaming) could be implemented even on a Pentium II with a little bit of optimization. Even Microsoft does not bother artificially bloating their operating system anymore.
I thought the idea of Minix is to intentionally keep it barebones so that it can be used for education and so that it can be fully understood by single person. It's certainly a cool kernel though.
According to the WDDM architecture diagram the GPU driver really is in the user space. Microsoft also has a separate article on User-Mode Display Drivers.
Oh and Linux isn't quite monolithic, for example all USB devices have user mode drivers. Just the basic read/write functions are in the kernel.
Can the GPU drivers be moved to userspace as well? Windows has done this since Vista, and a GPU driver crash results only in a small notification telling that the driver restarted. Isn't Linux all about these kind of hi-tech features?
Oh, come on, man.
What distro and DE are you using?
For Windows 10 users: if you want to get these test builds, go to Settings -> Update & security -> Windows Update -> Advanced options -> Get Insider Preview builds. I'm just putting this here as many might not be aware about this possibility.
I simply meant bugs and random glitches.
You're the one talking out of your ass. Of course OS X does not feature touch support, embedded features, or server features, because Apple does not make hardware with those features. Also, how does that have anything to do with robustness?
Why do you need a fully standard UNIX environment?
OS X is much more robust than Linux, so that's why people prefer OS X even though it costs.
And hey, OS X is free in the sense that it allows freely to use a wide range of software. In this sense it is more free than Linux.
It's amazing that people still think that the open source community is some kind of magical software mill at which you can throw software and expect it to come out polished. There's a lot of broken stuff out there that no one bothers to touch. In this case the even bigger problem is that the "community" quite does not have the production capacity compared to a team of professional full-time GPU engineers. Especially when GPU driver code is extremely challenging.
In previous Slashdot articles on the topic, I found it suspicious that there was suddenly so many articles in the news that were like "sitting kills you, as bad as smoking". I said that standing desk makers must love the trend.
I got a bunch of angry replies, saying that I am ignorant for not believing the scientific evidence.
In other news, Slashdot seems to finally have enabled HTTPS for everyone. Thanks!
Linux is stuck in the unfortunate spot of hoping things work as advertised.
How can you be sure that it's only that, and that Linux does not also contain crappy code? It's a bit too easy to just blame OEMs.
For example, the multiple backlight events problem could be pretty easily avoided by simply leaving the backlight adjustment responsibility only to the GPU driver. There's nothing hacky about that. A lot of machines can already be fixed with "acpi_backlight=native".
Of course, but filesystems are a solved problem already. Always reinventing them takes up a lot of testing time. Even Microsoft puts much less resources into filesystems: they occasionally add a small incremental update to the tried and trusted NTFS, and that's that.
If Dell delivers laptops with Linux preinstalled, then it's their problem, they got the hardware to reproduce it and they got paid people working on it.
According to a Reddit comment, even Dell does a partial job in Linux quality assurance. The touchpad supported palm detection, but the feature was not implemented. I'm pretty sure it works if you put Windows on the same computer. How much other small things are there hiding in that laptop that do not work properly in Linux when you take a closer look?
I recently did a quick survey in Reddit on people's experience on suspend/hibernate, and I may summarize it simply by saying that Linux is not the best performer in this area. :D It's a shame that such an important laptop feature works so poorly. Some might say that it's because OEMs do not "support ACPI spec properly", but in practice most PCs don't... It could be more practical to just find the patterns that Windows uses, and imitate them.
One really weird thing is also that backlight adjustment requests are sent to both ACPI and GPU, which causes double backlight adjustment events on many laptops.
People fight about SystemD, various open source licenses, differences between DEs, filesystems, but at the same time there's these fundamental problems which should get way more attention. Sometimes it feels like we are in a house arguing what kind of wallpapers bring the best experience, while that same wall is infested with mold inside.
Some people still talk like this is supposed to be the hi-tech kernel that breathes new life to my PC. Are they blind to all this stuff happening?
More eyeballs looking at the code.
The fail0verflow's GitHub repository contains the needed Radeon patches as well. Basically they only had to add the correct PCI ID into the driver to get started. It seems that further tweaks are needed to make it perfect though.
Facepalm. It seems that both I and Timothy are sleeping on the wheel. :D
Anyway, I would also add to the summary that you need some another way to actually make the kexec call. Over at PSXHAX there was posted a new BadIRET exploit last Wednesday. Maybe it works.
Why run LXDE when you can just run Windows, which runs as fast and offers much more functionality?
Duh... Then you lose the price advantage, which was the original point...