That's why the Linux kernel is so successful but the Linux desktops ain't. There should be a "Linus" for the desktop too: a colonel with a good taste, clear vision and uncompromising attitude.
Linux is not a realistic alternative on the desktop. It's too unreliable.
Additionally, LibreOffice is not suitable for real world use as it will ruin the layout of your MS Office documents (which still dominate the business world).
Given the wording, that sounds like they're going to have to contact either every contributor for copyright re-attribution, or rewrite their code for them.
I am working on a project that requires uploading and storing of documents. Although the application will need to allow uploading of.docx, doc,.pdf, etc, I'd like to store the documents in a standard open format that will allow easy search, compression, rendering, etc. Which open document format is the best?
PDF allows accurate rendering so it's the best choice. It will be a hot mess if you use anything else. Conversion of such complex formats is very error-prone for layout problems.
Remember that merely turning it on is not enough. You have to keep it on long enough to give time for the SSD's internal refresh cycle to walk through all of the cells.
Generally storage devices are filled with zeroes. But if it also uses inverse logic (charge means 0, no charge means 1) then some bit could indeed be flipped. This is just speculation though. In either case, when you format the disk, those rubbish bits are ignored anyway. They will eventually be refreshed as well.
As Windows is traditionally behind in these areas it may just not use queued TRIM at all.
That is my suspicion as well. This is sooo often the issue with all sorts of firmware. Linux tries to implement cutting edge features by spec, but in practice the hardware makers just write everything against Windows spec. The hardware might announce ACPI 5.0 support or queued TRIM support, but the actual codepaths are stubs that don't work properly. When such hardware is used under Linux, unexpected error states can be encountered. Sad trombone.
My understanding of GPU coding environment (not as a programmer, thank God, I just listened to job applicants and their presentations) is that, it is quite limited, almost all interpreted code. Some strange combination of C like code being written and then passed to renderers and shaders. It gets kind of "compiled" in place and gets executed.
Yep. Usually at application startup, shaders are compiled. Later in your renderer code you bind that shader just before you want to draw something using it.
On the other hand, these GPU computing codes are so damned complex they might not need additional obfuscation.
Not necessarily. Shaders can be very simple as well. They usually range from some tens to some hundreds of lines. Check out Shadertoy to see some.
Really, there's no reason to single this out as Linux. It could be done to any OS. I would imagine the first ones we see in the wild will target Windows.
Are you sure? Maybe it's easier to make rootkits for Linux.
Remember still that GPU shines at mathematics stuff. You feed it some matrices and tell to do some transformation on them, and it's extremely fast. But any kind of branching, while possible, is very slow. It's hard to make Windows Task Manager a program that runs well on a GPU.
What you describe/is/ swapping, which makes it odd since you started with "if you are not using swap". Care to elaborate on what exactly you did, under what circumstances?
My description is accurate. I have just been normally using the computer. Even without any swap, the HDD goes "krrrrrr..." and the system becomes very unresponsive when you begin to run out of memory. You can easily try it yourself, as it is reproducible every time.
It seems to throw out program pages from memory if it knows that they are disk-backed. It seems to be hard to trigger the OOM killer in this condition as well, even though it should happen.
Overallocations, OoM Killer, hangs and freezes all because the kernel can't be bothered to keep track of every last bit of it's memory make the Linux kernel a piss-poor substitute for a real UNIX kernel.
There are other problems in the memory subsystem as well. For example, if you are not using swap and the system begins to run out of memory, it starts throwing out pages of active programs from memory. Very soon they are loaded again from disk when those parts are needed. This causes a disk-grinding circus that feels like swapping.
Do not talk about unfinished stuff that is still in planning or development. Developing modern things is complex, and that's fine, but it's hard to keep the excitement alive for 5 years. Same goes for SteamBoxes. Same goes for Peter Molyneux's new game Godus, of which people got incredibly angry because it could not deliver this or that thing that was hyped earlier. The trendy "open development" strategy does not come without problems.
Slashdot Mirror
That's why the Linux kernel is so successful but the Linux desktops ain't. There should be a "Linus" for the desktop too: a colonel with a good taste, clear vision and uncompromising attitude.
Linux is not a realistic alternative on the desktop. It's too unreliable.
Additionally, LibreOffice is not suitable for real world use as it will ruin the layout of your MS Office documents (which still dominate the business world).
Exactly. I'll rather run a cracked copy of Ubuntu instead of receiving my free upgrade to Micro$oft crap.
So can you just name the manufacturers of such Linux workstations?
Does anyone know if a clean install will be possible if I have a legitimate key for a previous version?
Given the wording, that sounds like they're going to have to contact either every contributor for copyright re-attribution, or rewrite their code for them.
That's basically what they are doing.
As far as I have understood it, GTA IV uses 3 threads, and GTA V can adapt to both 2-core and 4-core CPUs.
I'm amazed that anybody would think MS Windows is a popular platform. There is a difference between forced to use and most popular.
And what is that difference? Windows is popular due to Microsoft's monopoly on it.
Where?
Not Open
Yeah, KolibriOS is an open fork of MenuetOS. It was forked when Menuet was still open source. Although Kolibri hasn't been updated for almost a year.
Not sure why they want to keep the genie in the bottle. Open source would be perfect for this kind of hobby project.
I am working on a project that requires uploading and storing of documents. Although the application will need to allow uploading of .docx, doc, .pdf, etc, I'd like to store the documents in a standard open format that will allow easy search, compression, rendering, etc. Which open document format is the best?
PDF allows accurate rendering so it's the best choice. It will be a hot mess if you use anything else. Conversion of such complex formats is very error-prone for layout problems.
Are those lyrics for a Steely Dan song?
I have had somewhat better luck during the last couple of years. It seems that the snipers are not that much on watch anymore.
Remember that merely turning it on is not enough. You have to keep it on long enough to give time for the SSD's internal refresh cycle to walk through all of the cells.
Generally storage devices are filled with zeroes. But if it also uses inverse logic (charge means 0, no charge means 1) then some bit could indeed be flipped. This is just speculation though. In either case, when you format the disk, those rubbish bits are ignored anyway. They will eventually be refreshed as well.
As Windows is traditionally behind in these areas it may just not use queued TRIM at all.
That is my suspicion as well. This is sooo often the issue with all sorts of firmware. Linux tries to implement cutting edge features by spec, but in practice the hardware makers just write everything against Windows spec. The hardware might announce ACPI 5.0 support or queued TRIM support, but the actual codepaths are stubs that don't work properly. When such hardware is used under Linux, unexpected error states can be encountered. Sad trombone.
My understanding of GPU coding environment (not as a programmer, thank God, I just listened to job applicants and their presentations) is that, it is quite limited, almost all interpreted code. Some strange combination of C like code being written and then passed to renderers and shaders. It gets kind of "compiled" in place and gets executed.
Yep. Usually at application startup, shaders are compiled. Later in your renderer code you bind that shader just before you want to draw something using it.
On the other hand, these GPU computing codes are so damned complex they might not need additional obfuscation.
Not necessarily. Shaders can be very simple as well. They usually range from some tens to some hundreds of lines. Check out Shadertoy to see some.
Really, there's no reason to single this out as Linux. It could be done to any OS. I would imagine the first ones we see in the wild will target Windows.
Are you sure? Maybe it's easier to make rootkits for Linux.
Remember still that GPU shines at mathematics stuff. You feed it some matrices and tell to do some transformation on them, and it's extremely fast. But any kind of branching, while possible, is very slow. It's hard to make Windows Task Manager a program that runs well on a GPU.
Yep, I'm certain that I had no swap allocated. The only explanation I could make was that program pages were thrown away and then reloaded soon again.
What you describe /is/ swapping, which makes it odd since you started with "if you are not using swap".
Care to elaborate on what exactly you did, under what circumstances?
My description is accurate. I have just been normally using the computer. Even without any swap, the HDD goes "krrrrrr..." and the system becomes very unresponsive when you begin to run out of memory. You can easily try it yourself, as it is reproducible every time.
It seems to throw out program pages from memory if it knows that they are disk-backed. It seems to be hard to trigger the OOM killer in this condition as well, even though it should happen.
I have a Sharp R-5000E which has been trucking for couple of decades.
Overallocations, OoM Killer, hangs and freezes all because the kernel can't be bothered to keep track of every last bit of it's memory make the Linux kernel a piss-poor substitute for a real UNIX kernel.
There are other problems in the memory subsystem as well. For example, if you are not using swap and the system begins to run out of memory, it starts throwing out pages of active programs from memory. Very soon they are loaded again from disk when those parts are needed. This causes a disk-grinding circus that feels like swapping.
Do not talk about unfinished stuff that is still in planning or development. Developing modern things is complex, and that's fine, but it's hard to keep the excitement alive for 5 years. Same goes for SteamBoxes. Same goes for Peter Molyneux's new game Godus, of which people got incredibly angry because it could not deliver this or that thing that was hyped earlier. The trendy "open development" strategy does not come without problems.
Even those issues have mostly been fixed in subsequent patches.