Welkom op webwereld.nl! Wist u dat u met een gratis Insider-account altijd op de hoogte blijft over al het nieuws, achtergrondartikelen, opinies, interviews en events rondom IT? Schrijf u nu gratis in »

Zo installeerden wij Windows 10 op een oude bak

In plaats van Linux probeerden we Windows 10 op onze oude desktop.

Er wordt vaak gezegd dat een oude computer nieuw leven kan worden ingeblazen door er Linux op te installeren. "Linux is lichter en kan beter overweg met oude hardware dan Windows." Maar is dat ook zo? Wij namen de proef op de som en installeerden Windows 10 op een tien jaar oude desktop.

Bob Skelley

Blog

2 november 2016

De HP Compaq Dc7700 met een Intel Core2Duo-processor is een apparaat dat al een tijdje bij ons op de plank stond. Deze desktop werd zo nu en dan nog wel eens aangezwengeld om er een licht Linux-systeem op te testen. Deze computer kwam destijds met Windows XP voor geïnstalleerd bij ons binnen en wij hebben deze desktop flink misbruikt om het een en ander mee te testen.

In eerste instantie was het de bedoeling om Lubuntu op de laptop te installeren, maar wij vingen hier en daar geluiden op dat deze laptop niet altijd even goed overweg kon met verschillende Linux-distributies. Vooral de videochip werd niet altijd even goed herkend en veel distributies kunnen alleen beeld geven op een resolutie van 1024 x 768. Er zijn door de jaren heen al wel wat oplossingen aangedragen om de problemen te tackelen, maar wij besloten eens te kijken hoe een modernere versie van Windows het zou doen op deze desktop.

Meer RAM

Om te voorkomen dat de computer dicht zou slibben en het upgradeproces uren in beslag zou nemen hebben we de harde schijf helemaal leeggehaald en zijn we begonnen met een schone installatie. Wij hebben het werkgeheugen van de desktop voor de upgrade wel even uitgebreid van 2GB naar 4GB. In principe kan de pc overweg met maximaal 8 GB RAM maar voor dit experiment was 4GB voldoende.

Lees meer over

Oudste boven ▾ Reacties

- 0 +1
  
  cascom op 9 november 2016 om 18:13 Meld misbruik
  
  Ik draai Windows 10 op een oudje met een Pentium 4, hieronder de gegevens:
  
  CPU-Z TXT Report
  
  ------------------------------------------------------------------------------
  
  CPU – Intel pentium 4 – Prescot – 3.06GHz – Socket 775 LGA
  
  Geheugen – 4 Gbytes – PC2-6400 (400 MHz) 64 bits
  
  Harddisk – ST3200826AS – 186.3 GB
  
  Graf. kaart – AMD Radeon HD 5670 – 1024 MB – GDDR5
  
  Windows 10 (10.0) Professional 32-bit (Build 14393)
  
  DirectX Version – 12.0
  
  ------------------------------------------------------------------------------
  
  Werkt natuurlijk niet zo erg snel, maar werkt goed genoeg om in Libre Office doc. aan te maken en met Firefox op het net rond te kijken en de printer aan te sturen.
  
  |
- 0 +1
  
  Vitayalin op 3 november 2016 om 11:55 Meld misbruik
  
  Dat van die driver vind ik wel grappig eigenlijk. Installatie werd afgebroken en toch werkte het verder.
  
  |
- +1 +2
  
  uberbofh op 4 november 2016 om 13:03 Meld misbruik
  
  Inderdaad grappig, beantwoord aan de windows manier van installeren, om vervolgens regelmatig te crashen door een GUI driver issue.
  
  Reactie gewijzigd op 4 november 2016 om 14:46 |
- 0 +1
  
  Walter op 3 november 2016 om 11:26 Meld misbruik
  
  Reactie gewijzigd op 3 november 2016 om 11:26 |
- +4 +5
  
  Joep Lunaar op 3 november 2016 om 11:03 Meld misbruik
  
  Wat aan dit verhaal wonderlijk is dat de geteste desktop misschien wel niet de nieuwste is, maar, get real, een Core 2 Duo (1,83 GHz ?) met 4 GB RAM, is best een flinke bak.
  
  Uit ervaring weet ik dat verschillende Linux distributies uitstekend en vlot werken op een dergelijk systeem en dan niet alleen de lichte distributies, maar ook met volledige Gnome Shell (best zwaar) en ook met de hogere "native" schermresoluties (out of the box). Vrijwel alle gewone GPU's worden door Linux prima ondersteund.
  
  maar wij vingen hier en daar geluiden op dat deze laptop niet altijd even goed overweg kon met verschillende Linux-distributies
  
  Wonderlijk, van horen zeggen dus, geen test of feit, slechts gerucht én "laptop" terwijl het over een testje op een desktop gaat.
  
  Die beperkte schermresolutie van 1024x768 is wonderlijk en moet een beperking zijn van het aangesloten scherm (4:3 en dat is best oud).
  
  Wel goed om nog eens onder de aandacht te brengen dat een iets ouder apparaat nog steeds prima bruikbaar is - dat die na gebruik over een wat langere periode onder MS Windows traag wordt zegt meer over dat onhygiënische OS dan over de apparatuur. Als een systeem wat trager wordt moet dat niet direct reden zijn om dan maar een nieuw apparaat aan te schaffen. Verspilling is dat en op de schaal dat MS Windows daar aanleiding toe geeft bijna een ecologische misdaad.
  
  Reactie gewijzigd op 4 november 2016 om 14:47 |
- +1 +2
  
  Walter op 3 november 2016 om 11:26 Meld misbruik
  
  Wonderlijke conclusie gezien de inhoud van het artikel:
  
  "dat die na gebruik over een wat langere periode onder MS Windows traag wordt zegt meer over dat onhygiënische OS dan over de apparatuur"
  
  Er wordt Windows 10 geïnstalleerd op een desktop waarop oorspronkelijk Windows XP was geïnstalleerd.
  
  Reactie gewijzigd op 3 november 2016 om 23:24 |
- +1 +2
  
  uberbofh op 3 november 2016 om 12:21 Meld misbruik
  
  Onjuist het geheugen werd verdubbeld, anders ging het feestje niet door.
  
  Reactie gewijzigd op 4 november 2016 om 14:47 |
- +2 +3
  
  Zorba op 3 november 2016 om 16:33 Meld misbruik
  
  Onjuist.. ook op 2GB draait een dergelijk apparaat prima. Met 4GB heb je gewoon voor een onbenullig bedrag een flitsende computer die weer geruime tijd meekan.
  
  Reactie gewijzigd op 4 november 2016 om 09:59 |
- +2 +3
  
  uberbofh op 3 november 2016 om 20:33 Meld misbruik
  
  Je moet ook nog applicaties draaien en het gaat niet over het onbenullige bedrag en zet dat flitsende ook maar uit je hoofd. Het testje was; draait win10 op een oude computer en dan komen ze aanzetten met een Intel Core2Duo met 4GB RAM, dat is nog steeds een flinke bak. Doe het maar eens op een simpele celeron met 256 MB RAM dual install met lubuntu
  
  Reactie gewijzigd op 4 november 2016 om 14:47 |
- +2 +3
  
  DiGiBaL op 3 november 2016 om 23:21 Meld misbruik
  
  OMG de mijne is langer dan de jouwe discussie ... totaal onbelangrijk in deze wereld. En in de daaropvolgende wereld nog minder. Alles wordt door tijd ingehaald.
  
  Als ik een bak voor 20 euri beter kan laten presteren dan doe ik dat ... het is geen 200 euri
  
  Reactie gewijzigd op 5 november 2016 om 08:30 |
- +2 +3
  
  uberbofh op 3 november 2016 om 23:50 Meld misbruik
  
  Jesus, leer jij ooit nog wel eens lezen. Daar gaat het niet over. Het gaat over draait windows 10 op een 10 jaar oude desktop.
  
  Reactie gewijzigd op 4 november 2016 om 14:47 |
- +1 +2
  
  Zorba op 4 november 2016 om 11:38 Meld misbruik
  
  En het gaat erover dat dat prima werkte inderdaad ;)
  
  Verassend voor jou kennelijk maar niet voor anderen. En onderaan deze pagina zie je nog een aantal aansprekende voorbeelden.
  
  Reactie gewijzigd op 5 november 2016 om 08:30 |
- +2 +3
  
  uberbofh op 4 november 2016 om 11:46 Meld misbruik
  
  Het geheugen moest verdubbeld worden, dat kennen we van windows,
  
  maar voor fanboys draait alles prima dat weet ik.
  
  Reactie gewijzigd op 4 november 2016 om 16:22 |
- +1 +2
  
  DiGiBaL op 4 november 2016 om 22:39 Meld misbruik
  
  Waar lees je dat het geheugen verdubbeld "moest" worden?
  
  Ze hebben het zonder onderbouwing gedaan; "Wij hebben het werkgeheugen van de desktop voor de upgrade wel even uitgebreid van 2GB naar 4GB" - zonder opgave van reden.
  
  Reactie gewijzigd op 5 november 2016 om 08:31 |
- +2 +3
  
  Zorba op 3 november 2016 om 11:31 Meld misbruik
  
  Het trager worden van Windows is sinds W7 geen issue meer.
  
  En of een 10 jaar oude computer nu ineens een flink beestje is weet ik niet. Is toch echt een heel gangbaar model.
  
  Ik weet wel dat op eenzelfde soort computer (AMD Athlon 641) op een recente Ubuntu tot een vrijwel onwerkbaar traag systeem leidde. Een moderne Mint daarentegen liep ( en loopt) er prima op.
  
  Reactie gewijzigd op 4 november 2016 om 09:59 |
- +3 +4
  
  Joep Lunaar op 3 november 2016 om 13:48 Meld misbruik
  
  Zorba:Het trager worden van Windows is sinds W7 geen issue meer.
  
  Mogelijk heb jij meer ervaring met de nieuwere versies van MS Windows dan ik, maar als voormalig MS Windows systeemprogrammeur ontkom ik er niet aan nog regelmatig computers met dat OS bij klanten van mij onder handen te moeten nemen en zijn die, ook al staat daar versie 7+ op, vaak irritant traag. Ook blijft de enorme hoeveelheid achtergebleven tijdelijke bestanden, mappen met installers (zelfs in C:\), verouderde of ongeldige sleutels in het register enz. enz. verbijsteren. Dat noem ik onhygiënisch.
  
  W10 lijkt de teugels gelukkig wat strakker aan te halen en de introductie, eindelijk, van cumulatieve updates, zal ook zeker gaan helpen.
  
  Reactie gewijzigd op 4 november 2016 om 14:50 |
- +3 +4
  
  Robert van Weersch op 3 november 2016 om 07:35 Meld misbruik
  
  Ik draai W10 op een Asus T100 hybrid tablet: Atom CPU met 2 GB RAM. Dat werkt zondermeer uitstekend.
  
  Reactie gewijzigd op 4 november 2016 om 01:19 |
- +1 +2
  
  uberbofh op 2 november 2016 om 21:25 Meld misbruik
  
  Linux is lichter en kan beter overweg met oude hardware dan Windows." Maar is dat ook zo? Wij namen de proef op de som en installeerden Windows 10 op een tien jaar oude desktop.
  
  Om er vervolgens 2x zo veel geheugen in te stoppen van 2GB naar 4GB
  
  Van windows is bekend dat RAM cruciaal is ivm Prefetch (om programma data alvast in geheugen te hebben ipv disk te laden wat langzamer is natuurlijk)
  
  De lichte Linux distro's presteren veel beter juist omdat er in die oude dozen weinig geheugen zit.
  
  1e conclusie:
  
  Toen Windows na de installatie startte werden wij begroet met een scherm op een resolutie van 1024 x 768. Hoger konden wij niet gaan. Geen verschil met Linux dus
  
  Maar er is helemaal geen Linux geprobeerd! Toen ben ik afgehaakt, wat een slecht adhoc gepruts.
  
  Reactie gewijzigd op 3 november 2016 om 09:51 |
- +3 +4
  
  DiGiBaL op 2 november 2016 om 21:52 Meld misbruik
  
  Vervelend he, positief bericht over Windows op een oude low en CPU ;)
  
  "Maar er is helemaal geen Linux geprobeerd! Toen ben ik afgehaakt, wat een slecht adhoc gepruts."
  
  Dat was ook helemaal niet de bedoeling van dit artikel. Bedoeling was om te kijken of Win10 erop zou draaien.
  
  Men gebruikte het weldegelijk om Linux op te testen - "Deze desktop werd zo nu en dan nog wel eens aangezwengeld om er een licht Linux-systeem op te testen." - maar qua resolutie viel het blijkbaar tegen; "Vooral de videochip werd niet altijd even goed herkend en veel distributies kunnen alleen beeld geven op een resolutie van 1024 x 768."
  
  Doet er verder niet toe ... het gaat over Windows 10 op die oude bak. En voor €20,- heb je er 2 GB bij ... ik zou het er niet voor laten als het systeem er vlotter van wordt.
  
  Reactie gewijzigd op 3 november 2016 om 11:32 |
- +2 +3
  
  uberbofh op 3 november 2016 om 00:25 Meld misbruik
  
  Dat was ook helemaal niet de bedoeling van dit artikel. Bedoeling was om te kijken of Win10 erop zou draaien.
  
  Het wordt er wel mee vergeleken en dat is vrij onnozel als de distro onbekend is.
  
  Om het geheugen te verdubbelen voor de test is natuurlijk lachwekkend, want win 10 draait niet op oude machines :)
  
  Reactie gewijzigd op 4 november 2016 om 00:52 |
- +2 +3
  
  Powermax op 3 november 2016 om 08:13 Meld misbruik
  
  Het tegendeel is bewezen... of je het leuk vindt of niet.
  
  Reactie gewijzigd op 3 november 2016 om 11:32 |
- 0 +1
  
  uberbofh op 3 november 2016 om 12:23 Meld misbruik
  
  Dat fanboys snel te vreden zijn wisten we wel en dat windows geheugen vreet ook, daarom werd eerst het geheugen verdubbeld! anders ging het feestje niet door :)
  
  |
- +1 +2
  
  Joep Lunaar op 3 november 2016 om 13:52 Meld misbruik
  
  Gebruik van Gnome shell en Wayland (non-tiled) gebaseerde gebruikersschillen onder Linux vreten ook geheugen.
  
  Reactie gewijzigd op 3 november 2016 om 16:21 |
- +1 +2
  
  uberbofh op 3 november 2016 om 15:40 Meld misbruik
  
  Dat valt reuze mee. Ik draai Gnome shell en Wayland (centos7) ook op een 12 jaar oude dell desktop met 2G geheugen en in een virtuele Gnome box met 1GB
  
  Linux distros bieden keuze. Een xubuntu, lubuntu distro draaien prima met 1GB geheugen incl applicaties. Voor nog minder geheugen ook keuze zat, maar dan is ook een alternatief voor libreoffice en firefox an te bevelen.
  
  Reactie gewijzigd op 4 november 2016 om 16:52 |
- +1 +2
  
  Zorba op 5 november 2016 om 12:29 Meld misbruik
  
  Kom op joh, ben toch niet zo vreselijk onredelijk. ja windows heeft tekrotkomeingen maa rheb je jezelf wel eens echt verdiept in enkele van de problemen die linux teisteren? En dan zonder de gekleurde bril.
  
  Hier een beperkt lijstje van de grooste ergernissen onder linux. ( niet uitputten dmaar een aardige opsomming)
  
  Hardware support:
  
  Video accelerators/acceleration (also see the X system section).
  
  ! NVIDIA Optimus technology and ATI dynamic GPU switching are still not supported on Linux out of the box in most major distros (Mint starting from version 17.2 supports Optimus but quite awkwardly - read the WFM section). AMD hybrid graphics support is lousy and very incomplete.
  
  ! Open source drivers have certain, sometimes very serious problems (Intel-!, NVIDIA and AMD):
  
  ! Open Source NVIDIA driver is much slower (up to five times) than its proprietary counterpart due to improperly working power management.
  
  AMD and Intel graphics drivers can be significantly slower than their proprietary counterparts (for Intel that's their Windows driver) in new complex, graphically intensive games and applications. Luckily open source drivers have reached parity in regard to old games and applications.
  
  ! The most recent test shows that open source AMD and NVIDIA drivers struggle to properly support many types of video cards.
  
  ! Open Source NVIDIA driver do not properly and fully support power management features and fan speed management.
  
  ! Suspend and resume in Linux is unstable and oftentimes don't work.
  
  The lack of suitable performance counters support due to different issues.
  
  OpenCL and multiGPU rendering are not supported by open source drivers.
  
  Oftentimes both open source and closed source drivers cannot properly detect and/or use monitors: with certain displays you may get black screen, or unsupported resolutions, or out of bandwidth message.
  
  !! According to an anonymous NVIDIA engineer, "Nearly Every Game Ships Broken ... In some cases, we’re talking about blatant violations of API rules ... There are lots of optional patches already in the driver that are simply toggled on or off as per-game settings, and then hacks that are more specific to games ... Ever wondered why nearly every major game release is accompanied by a matching driver release from AMD and/or NVIDIA?". The open source community simply doesn't have the resources to implement similar hacks to fix broken games, which means at least for complex AAA games proprietary drivers will remain the only option.
  
  ! Mesa problems (Open source OpenGL stack):
  
  This has become a distro specific choice, and hopefully we'll forget about it very soon: certain OpenGL features cannot be enabled in Linux due to patents (like S3TC texture compression and floating point textures).
  
  You cannot easily mix proprietary NVIDIA/AMD drivers with open source drivers because the former override system wide OpenGL/OpenCL libraries. At the end of 2015 NVIDIA started working on implementing a vendor neutral OpenGL dispatch library which can solve this issue. Most likely this issue will be finally resolved in 2016.
  
  ! NVIDIA and AMD proprietary graphics drivers don't work reliably for many people (crashes, unsupported new kernel and X server, slow downs, extreme temperatures, a very loud fan, 100% CPU usage, etc.).
  
  Proprietary NVIDIA/AMD graphics drivers don't fully support KMS/VirtualFB and are often late in supporting newer X.org server and kernel releases. Besides Linux developers do everything to break closed source drivers by changing APIs (to give you an example, each and every kernel from 3.8 to 3.14 included, had changes that rendered NVIDIA binary drivers inoperable, i.e. uncompilable) or making APIs unusable beyond the GPL realm. Edit 2016-03-21: NVIDIA blob now supports KMS, Vulkan, Wayland and Mir!
  
  ! Great many users experience severe video and desktop tearing while watching videos and youtube clips (using Adobe Flash) - this issue affects both proprietary (NVIDIA confirmed that this issue plagues Kepler and Maxwell GPUs; an NVIDIA specific workaround exists but it causes performance degradation) and open source GPU drivers. Ostensibly it's an X.org "feature".
  
  ! Linux drivers are usually much worse (they require a lot of tinkering, i.e. manual configuration) than Windows/Mac OS drivers in regard to support of non-standard display resolutions, very high (a.k.a. HiDPI) display resolutions or custom refresh rates.
  
  ! Under Linux setting multi-monitor configurations especially using multiple GPUs running binary NVIDIA drivers can be a major PITA.
  
  Audio subsystem:
  
  ! ALSA (the primary sound driver in modern Linux'es) is a constant pain for both developers and users.
  
  ! No reliable echo cancellation (if you use a normal microphone and speakers in many cases you won't be able to use Skype and other VoIP services normally). Windows, Android and MacOS implement it on a system level. There's a solution for PulseAudio - hopefully it'll be enabled by default in the future or/and there'll be an easier way to use it.
  
  ! No reliable sound system, no reliable unified software audio mixing (implemented in all modern OSes except Linux), many old or/and proprietary applications still open audio output exclusively causing major user problems and headache.
  
  PulseAudio is unsuitable for multiuser mode.
  
  No volume control for HDMI devices connected to NVIDIA GPUs (notwithstanding ALSA softvol hacks).
  
  High definition audio support (=96KHz, =24bit) is too often unusable. (Adobe Flash doesn't work with it, old Linux applications do not work with it or produce broken sound).
  
  (Applies only to certain sound cards, e.g. the Creative Audigy series) Insanely difficult to set up volume levels, audio recording and in some situations even audio output. Highly confusing, not self-explanatory audio channels names/settings.
  
  (Linux developers don't care about backward compatibility - OSS is mostly unsupported nowadays, OSSv4 is no longer being developed. ALSA FTW - like it or not) Changing the default sound card for all applications (i.e. for old applications using OSS or ALSA directly) if you have more than one of them is a major PITA.
  
  Printers, scanners and other more or less peripheral devices:
  
  ! There are still many printers which are not supported at all or only barely supported (among them are Lexmark and Canon) - some people argue that the user should research Linux compatibility before buying their hardware. What if the user decides to switch from Windows to Linux when he/she already has some hardware? When people purchase a Windows PC do they research anything? No, they rightly assume everything will work out of the box right from the get-go.
  
  Many printers features are only implemented in Windows drivers.
  
  ! Some models of scanners and (web-)cameras are still inadequately supported (again many features from Windows drivers are missing) or not supported at all.
  
  Incomplete or unstable drivers for some hardware. Problems setting up some hardware (like sound cards, touchpads in newest laptops, web cameras or Wi-Fi cards, for instance, 802.11ac and USB Wi-Fi adapters are barely supported under Linux and in many cases they are just unusable). Numerous people report that Broadcom and Realtek network adapters are barely usable or outright unusable under Linux.
  
  Laptops/notebooks special buttons and features often don't work (e.g. Fn + F1-F12 combination or special power saving modes).
  
  ! An insane number of regressions in the Linux kernel, when with every new kernel release some hardware can stop working inexplicably. I have personally reported two serious audio playback regressions, which have been consequently resolved, however most users don't know how to file bugs, how to bisect regressions, how to identify faulty components.
  
  ! Incomplete or missing support for certain power saving features modern laptops employ (like e.g. PCIe ASPM, proper video decoding acceleration, deep power saving states, etc.) thus under Linux you won't get the same battery life as under Windows or MacOS and your laptop will run a lot hotter. Jupiter (discontinued unfortunately), see Advanced Power Management for Linux.
  
  Software support:
  
  X system (current primary video output server in Linux):
  
  X.org is largely outdated, unsuitable and even very much insecure for modern PCs and applications.
  
  No high level, stable, sane (truly forward and backward compatible) and standardized API for developing GUI applications (like core Win32 API - most Windows 95 applications still run fine in Windows 10 - that's 20 years of binary compatibility). Both GTK and Qt (incompatible GTK versions 1, 2, 3 and incompatible Qt versions 2, 3, 4, 5 just for the last decade) don't strive to be backwards compatible.
  
  ! Keyboard shortcuts handling for people using local keyboard layouts is broken (this bug is now 10 years old).
  
  ! X.org doesn't automatically switch between desktop resolutions if you have a full screen application with a custom resolution running - strangely some Linux developers oppose to the whole idea of games on Linux. But since Linux is not a gaming platform and no one is interested in Linux as a gaming platform this problem importance is debatable. Valve has released Steam for Linux and they are now porting their games for Linux - but that's a drop in the bucket.
  
  ! X.org doesn't restore gamma (which can be perceived as increased brightness) settings on application exit. If you play Valve/Wine games and experience this problem run `xgamma -1` in a terminal. You can thank me by clicking the ad at the top of the page ;-)
  
  ! Scrolling in various applications causes artifacts.
  
  ! X.org allows applications to exclusively grab keyboard and mouse input. If such applications misbehave you are left with a system you cannot manage, you cannot even switch to text terminals.
  
  ! Keyboard handling in X.org is broken by design - when you have a pop up or an open menu, global keyboard shortcuts/keybindings don't (GTK) work (QT).
  
  It's fixed as for Qt5 - hopefully most Qt4 applications will be ported to Qt5: another keyboard handling issue is that in many situations applications' shortcuts do not work (Qt4) when you have a different than the English US keyboard layout.
  
  ! For VM applications keyboard handling is incomplete and passing keypresses to guest OS'es is outright broken.
  
  ! X.org architecture is inherently insecure - even if you run a desktop GUI application under a different user in your desktop session, e.g. using sudo and xhost, then that "foreign" application can grab any input events and also make screenshots of the entire screen.
  
  Adobe Flash Player has numerous problems under Linux (unsupported video acceleration decoding and rendering, video tearing, crashes and frames dropping at 100% CPU usage even on high end systems). In 2012 Adobe announced that Adobe Flash player wouldn't be supported any longer for any browsers other than Google Chrome. Edit 2016: no, this issue has not been resolved, it's just Adobe Flash Player which is rapidly becoming irrelevant.
  
  ! X.org server currently has no means of permanently storing and restoring settings changed by the user (xrender settings, Xv settings, etc.). NVIDIA and ATI proprietary drivers both employ custom utilities for this purpose.
  
  !! X.org has no means of providing a tear free experience, it's only available if you're running a compositing window manager in the OpenGL mode with vsync-to-blank enabled.
  
  !! X.org is not multithreaded. Certain applications running intensive graphical operations can easily freeze your desktop (a simple easily reproducible example: run Adobe Photoshop 7.0 under Wine, open a big enough image and apply a sophisticated filter - see your graphical session die completely until Photoshop finishes its operation).
  
  ! There's currently no way to configure mouse scroll speed/acceleration under X.org. Some mice models scroll erratically under X.org.
  
  There's no way to replace/upgrade/downgrade X.org graphics drivers on the fly (simply put - to restart X server while retaining a user session and running applications).
  
  No true safe mode for the X.org server (likewise for KMS - read below). Misconfiguration and broken drivers can leave you with a non-functional system, where sometimes you cannot access text virtual consoles to rectify the situation (in 2013 it became almost a non-issue since quite often nowadays X.org no longer drives your GPU - the kernel does that via KMS).
  
  Adding custom modelines in Linux is a major PITA.
  
  ! X.org totally sucks (IOW doesn't work at all in regard to old applications) when it comes to supporting tiled displays, for instance modern 4K displays (Dell UP3214Q, Dell UP2414Q, ASUS PQ321QE, Seiko TVs and others). This is yet another architectural limitation.
  
  !! HiDPI support is pretty much non-existent.
  
  ! Fast user switching (and also concurrent users' sessions) under X.org works very badly and is implemented as a dirty hack: for every user a new X.org server is started. It's possible to login twice under the same account while not being able to run many applications due to errors caused by concurrent access to the same files. Fast user switching is best implemented in KDE followed by Gnome.
  
  Related problems:
  
  1) Concurrently logged in users cannot access the same USB flash drive(s).
  
  2) There are reports that problems exists with configuring audio mixer volume levels.
  
  Wayland:
  
  !! Applications (GUI toolkits) must implement their own windows shadowing, because Wayland decorator has no access to applications sub-windows. This issue seems to be resolved.
  
  !! Wayland works through rasterization of pixels which brings about two very bad critical problems which will never be solved:
  
  Firstly, forget about performance/bandwidth efficient RDP protocol (it's already implemented but it works by sending updates of large chunks of the screen, i.e. a lot like old highly inefficient VNC), forget about OpenGL pass through, forget about raw compressed video passthrough. In case you're interested all these features work in Microsoft's RDP.
  
  Secondly, forget about proper output rotation/scaling/ratio change.
  
  !! 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.
  
  !! Applications (GUI toolkits) must implement their own DPI scaling.
  
  The above issues are actually the result of not having one unified graphical toolkit/API (and Wayland developers will not implement it). Alas, no one is currently working towards making existing toolkits share one common configuration for setting fonts antialiasing, DPI scaling and windows shadowing. At least in theory these issues can be easily solved, in practice we already have three independent toolkits for Wayland (GTK3/Qt5/Enlightenment).
  
  !! Applies to the X server/protocol as well: neither X.org, nor Wayland offer a way to extend/modify windows title bars' and File Open/Save dialogs. This is a very powerful feature which can be very useful in many situations. Again it's a result of the fact that there's no unified toolkit and no unified window manager (or protocol).
  
  Font rendering (which is implemented via high level GUI libraries) issues:
  
  ! White or light-colored fonts antialiasing on dark backgrounds (without Infinality patches which are yet to be included by default by any distro) is horrible.
  
  ! ClearType fonts are not properly supported out of the box (for a test I compiled FreeType 2.4.11 with ClearType technology but the results were abysmal). Even though the ClearType font rendering technology is now supported, you have no means to properly configure/tune it.
  
  Quite often default fonts look ugly, due to missing good (catered to the LCD screen - subpixel RGB full hinting) default fontconfig settings (this quite unpopular website alone gets over 20% of its visitors seeking to fix bad fonts (rendering) in Linux).
  
  Web fonts under Linux often look horrible in old distros.
  
  Fonts antialiasing is very difficult to implement properly when not using GTK/Qt libraries (Opera had been struggling with fonts antialiasing for a year before they made it work correctly, Google Chrome had fonts rendering broken for eight months).
  
  (Getting better but we're not yet there) By default most distros come without good or even Windows compatible fonts.
  
  Fonts antialiasing settings cannot be applied on-the-fly under many DE.
  
  By default most distros disable good fonts antialiasing due to patents - more or less resolved in 2012 (however even in 2016 there are still many distros which forget/refuse to enable SPR in freetype2).
  
  The Linux kernel:
  
  ! The kernel cannot recover from video, sound and network drivers' crashes (I'm very sorry for drawing a comparison with Windows Vista/7/8 where this feature is implemented and works beautifully in a lot of cases).
  
  KMS exclusively grabs video output and disallows VESA graphics modes (thus it's impossible to switch different versions of graphics drivers on the fly).
  
  KMS video drivers cannot be unloaded or reloaded.
  
  !! KMS has no safe mode: sometimes KMS cannot properly initialize your display and you have a dead system you cannot access at all (a kernel option "nomodeset" can save you, but it prevents KMS drivers from working at all - so either you have 80x25 text console or you have a perfectly dead display).
  
  Traditional Linux/Unix (ext4/reiser/xfs/jfs/btrfs/etc.) filesystems can be problematic when being used on mass media storage.
  
  File descriptors and network sockets cannot be forcibly closed - it's indeed unsafe to remove USB sticks without unmounting them first as it leads to stale mount points, and in certain cases to oopses and crashes. For the same reason you cannot modify your partitions table and resize/move the root partition on the fly.
  
  In most cases kernel crashes (= panics) are invisible if you are running an X session. Moreover KMS prevents the kernel from switching to plain 640x480 or 80x25 (text) VGA modes to print error messages.
  
  Very incomplete hardware sensors support, for instance, hwinfo32/64 detects and shows ten hardware sensors sources on my average desktop PC and over 50 sensors, whilst lm-sensors detect and present just four sources and 20 sensors. This situation is even worse on laptops - sometimes the only readings you get from lm-sensors are cpu cores' temperatures.
  
  !! A great number (sometimes up to a hundred) of very serious regressions every kernel release due to missing QC/QA.
  
  !! The Linux kernel is extremely difficult and cumbersome to debug even for the people who develop it.
  
  Under some circumstances the system or X.org's GUI may become very slow and unresponsive due to various problems with video acceleration or lack of it and also due to notorious bug 12309 - it's ostensibly fixed but some people still experience it). This bug can be easily reproduced under Android (which employs the Linux kernel) even in 2016: run any disk intensive application (e.g. under any Android terminal 'cat /dev/zero /sdcard/testfile') and enjoy total UI unresponsiveness.
  
  Problems stemming from the vast number of Linux distributions:
  
  ! No unified configuration system for computer settings, devices and system services. E.g. distro A sets up networking using these utilities, outputting certain settings residing in certain file system locations, distro B sets up everything differently. This drives most users mad.
  
  ! No unified installer/package manager/universal packaging format/dependency tracking across all distros (The GNU Guix project, which is meant to solve this problem, is now under development - but we are yet to see whether it will be incorporated by major distros). Consider RPM (which has several incompatible versions, yeah), deb, portage, tar.gz, sources, etc. It adds to the cost of software development.
  
  ! Distros' repositories do not contain all available open source software (libraries conflicts don't even allow that luxury). The user should never be bothered with using ./configure && make && make install (besides it's insecure, can break things in a major way, and it sometimes simply doesn't work because the user cannot install/configure dependencies properly). It should be possible to install any software by downloading a package and double clicking it (yes, like in Windows, but probably prompting for a user/administrator password). Linux distros. ©2000 Microsoft Germany
  
  ! Applications development is a major PITA. Different distros can use a) different libraries versions b) different compiler flags c) different compilers. This leads to a number of problems raised to the third power. Packaging all dependent libraries is not a solution, because in this case your application may depend on older versions of libraries which contain serious remotely exploitable vulnerabilities.
  
  ! Two most popular open source desktops, KDE and Gnome, can configure only few settings by themselves thus each distro creates its own bicycle (applications/utilities) for configuring a boot loader/firewall/network/users and groups/services/etc.
  
  Linux is a hell for ISP/ISV support personnel. Within the organization you can force a single distro on anyone, but it cannot be accomplished when your clients have the freedom to choose.
  
  ! It should be possible to configure pretty much everything via GUI (in the end Windows and Mac OS allow this) which is still not a case for some situations and operations.
  
  No polish and universally followed conventions. Different applications may have totally different shortcuts for the same actions, UI elements may be placed and look differently.
  
  Problems stemming from low Linux popularity and open source nature:
  
  ! Few software titles, inability to run familiar Windows software (some applications which don't work in Wine (look at the lines which contains the word "regression") have zero Linux equivalents).
  
  ! No equivalent of some hardcore Windows software like ArchiCAD/3ds Max/Adobe Premier/Adobe Photoshop/Corel Draw/DVD authoring applications/etc. Home and enterprise users just won't bother installing Linux until they can get their work done.
  
  ! A small number of games and few AAA games for the past six years. The number of available Linux games overall is less than 5% of games for Windows. Steam shows a better picture: 25% of games over there have Linux ports but 98-99% out of them are Indies, i.e. AAA titles, specially recent, are a rarity in Linux. Cedega (long dead) and Wine (very unstable, very regressions prone) offer very incomplete support.
  
  Questionable patents and legality status. USA Linux users cannot play many popular audio and video formats until they purchase appropriate codecs.
  
  General Linux problems:
  
  !! There's no guarantee whatsoever that your system will (re)boot successfully after GRUB (bootloader) or kernel updates - sometimes even minor kernel updates break the boot process. For instance Microsoft and Apple regularly update ntoskrnl.exe and mach_kernel respectively for security fixes, but it's unheard of that these updates ever compromised the boot process. GRUB updates have broken the boot process on the PCs around me for at least ten times. (Also see compatibility issues below).
  
  !! LTS distros are unusable on the desktop because they poorly support or don't support new hardware, specifically GPUs (as well as Wi-Fi adapters, NICs, sound cards, hardware sensors, etc.). Oftentimes you cannot use new software in LTS distros (normally without miscellaneous hacks like backports, PPAs, chroots, etc.), due to outdated libraries. A recent example is Google Chrome on RHEL 6/CentOS 6.
  
  !! Linux developers have a tendency to a) suppress news of security holes b) not notify the public when said hole have been fixed c) miscategorize arbitrary code execution bugs as "possible denial of service" (thanks to Gullible Jones for reminding me of this practice - I wanted to mention it aeons ago, but I kept forgetting about that).
  
  Here's a full quote by Torvalds himself: "So I personally consider security bugs to be just "normal bugs". I don't cover them up, but I also don't have any reason what-so-ever to think it's a good idea to track them and announce them as something special."
  
  Year 2014 was the most damning in regard to Linux security: critical remotely exploitable vulnerabilities were found in many basic Open Source projects, like bash (shellshock), OpenSSL (heartbleed), kernel and others. So much for "everyone can read the code thus it's invulnerable". In the beginning of 2015 a new critical remotely exploitable vulnerability was found, called GHOST.
  
  Year 2015 welcomed us with 134 vulnerabilities in one package alone: WebKitGTK+ WSA-2015-0002. I'm not implying that Linux is worse than Windows/MacOS proprietary/closed software - I'm just saying that the mantra that open source is more secure by definition because everyone can read the code is apparently totally wrong.
  
  Many Linux developers are concerned with the state of security in Linux because it is simply lacking.
  
  !! Linux/Unix web servers are generally a lot less secure than ... Windows web servers, "The vast majority of webmasters and system administrators have to update their software manually and test that their infrastructure works correctly".
  
  Seems like there are lots of uniquely gifted people out there thinking I'm an idiot to write about this. Let me clarify this issue: whereas in Windows security updates are mandatory and they are usually installed automatically, Linux is usually administered via SSH and there's no indication of any updates at all. In Windows most server applications can be updated seamlessly without breaking services configuration. In Linux in a lot of cases new software releases require manual reconfiguration (here are a few examples: ngnix, apache, exim, postfix). The above two causes lead to a situation when millions of Linux systems never receive any updates, because their respective administrators don't bother to update anything since they're afraid that something will break.
  
  August 2016 report from Kaspersky corroborates my thesis: in the first seven months of 2016 the number of infected Linux servers increased by 70%.
  
  !! A new Linux init(!) system systemd has an utterly broken design: systemd can and does segfault, crash and freeze. In a sane world init should never ever crash under no circumstances.
  
  Edit: systemd has become a lot more stable and reliable recently however this doesn't change the fact that an init daemon should be designed such a way 1) it should never leave the system in an undefined state 2) it should be trivially updateable 3) it should never crash. SystemD however has all these problems combined. I for one also believe that an init daemon should try to boot up to a login prompt whenever possible, however systemd will stop booting after encountering even minor problems with fstab.
  
  A year ago a simple solution was proposed: process id 1 (init) should be a very simple daemon, which will spawn all dependent systemd subsystems and processes. In this case the system can possibly recover from certain systemd errors. However no one really wants to implement this solution. Instead systemd grows bigger, more complicated and more prone to malfunctioning. Most embedded Linux system builders actually gave up on systemd due to its immoderate memory consumption and complexity.
  
  ! Fixed applications versions during a distro life-cycle. Say, you use DistroX v10.10 which comes with certain software. Before DistroX 11.10 gets released some applications get updated, get new exciting features but you cannot officially install, nor use them.
  
  ! Let's expand the previous point. Most Linux distros are made such a way you cannot upgrade their individual core components (like kernel, glibc, Xorg, Xorg video drivers, Mesa drivers, etc.) without upgrading your whole system. Also if you have brand new hardware oftentimes you cannot install current Linux distros because almost all of them (aside from rare exceptions) don't incorporate the newest kernel release, so either you have to use alpha/development versions of your distro or you have to employ various hacks in order to install the said kernel.
  
  Some people argue that one of the problems that severely hampers the progress and expansion of Linux is that Linux doesn't have a clear separation between the core system and user space applications. In other words (mentioned throughout the article) third party developers cannot rely on a fixed set of libraries and programming interfaces (API/ABI) - in most other OSes you can expect your application to work for years without recompilation and extra fixes - it's often not possible in Linux.
  
  No native or/and simple solutions for really simple encrypted file sharing in the local network with password authentication (Samba is not native, it's a reverse engineered SMB implementation, it's very difficult for the average Joe to manage and set up. Samba 4 reimplements so many Linux network services/daemons - it looks like a Swiss knife solution from the outer space).
  
  Glibc by design "leaks" memory (due to heap fragmentation). Firefox for Linux now uses its own memory allocator. KDE Konsole application uses its own memory allocation routines. Neil Skrypuch posted an excellent explanation of this issue here.
  
  ! Just (Gnome) not enough (KDE) manpower (X.org) - three major Open Source projects are seriously understaffed.
  
  ! It's a major problem in the tech industry at large but I'll mention it anyways because it's serious: Linux/open source developers are often not interested in fixing bugs if they cannot easily reproduce them (for instance when your environment substantially differs from the developer's environment). This problem plagues virtually all Open Source projects and it's more serious in regard to Linux because Linux has fewer users and fewer developers. Open Source developers often don't get paid to solve bugs so there's little incentive for them to try to replicate and squash difficult to reproduce bugs.
  
  ! A galore of software bugs across all applications. Just look into KDE or Gnome bugzilla's - some bugs are now ten years old with over several dozens of duplicates and no one is working on them. KDE/Gnome/etc. developers are busy adding new features and breaking old APIs, fixing bugs is of course a tedious and difficult chore.
  
  ! Steep learning curve (even in 2016 you oftentimes need to use CLI to complete some trivial or non-trivial tasks, e.g. when installing third party software).
  
  ! Poor or almost missing regression testing in Linux kernel (and, alas, in other Open Source software too) leading to a situation when new kernels may become totally unusable for some hardware configurations (software suspend doesn't work, crashes, unable to boot, networking problems, video tearing, etc.)
  
  ! GUI network management in Linux is a bloody mess. Consider yourself lucky if NetworkManager works reliably for you. In too many cases NM won't see your existing eth0 connection, nor will it be able to detect it, even if this connection has never been configured before. NM cannot change your NIC hardware parameters. You cannot establish PPPoE connections over Wi-Fi.
  
  Poor interoperability between the kernel and user space applications. E.g. many kernel features get a decent userspace implementation years after introduction.
  
  ! Linux security/permissions management is a bloody mess: PAM, SeLinux, Udev, HAL (replaced with udisk/upower/libudev), PolicyKit, ConsoleKit and usual Unix permissions (/etc/passwd, /etc/group) all have their separate incompatible permissions management systems spread all over the file system. Quite often people cannot use their digital devices unless they switch to a super user.
  
  No (easy to use) application level sandbox (like e.g. SandBoxie) - Fedora is working hard on it.
  
  (This needs to be thoroughly rechecked): observed general slowness: just compare start up times between e.g. OpenOffice and Microsoft Office. If you don't like this example, try launching OpenOffice in Windows and in Linux. In the latter case it will take more time to launch it.
  
  ! CLI (command line interface) errors for user applications. All GUI applications should have a visible errors representation.
  
  ! Very poor documentation and absence of good manuals/help system.
  
  Questionable services for Desktop installations (Fedora, Suse, Mandriva, Ubuntu) - not really important with the advent of systemd.
  
  ! No unified widely used system for packages signing and verification (thus it becomes increasingly problematic to verify packages which are not included by your distro). No central body to issue certificates and to sign packages.
  
  There are no antiviruses or similar software for Linux (the existing ones are made for finding Windows viruses and analyzing Windows executives - i.e. they are more or less useless for Linux). Say, you want to install new software which is not included by your distro - currently there's no way to check if it's malicious or not.
  
  !! Linux distributions do not audit included packages which means a rogue evil application or a rogue evil patch can easily make into most distros thus endangering the end user.
  
  ! A very bad backwards and forward compatibility.
  
  ! Due to unstable and constantly changing kernel APIs/ABIs Linux is a hell for companies which cannot push their drivers upstream into the kernel for various reasons like their closeness (NVIDIA, ATI, Broadcom, etc.), or inability to control development or co-develop (VirtualBox/Oracle, VMWare/Workstation, etc.), or licensing issues (4Front Technologies/OSS).
  
  Old applications rarely work in new Linux distros (glibc incompatibilities (double-free errors, memory corruption, etc.), missing libraries, wrong/new libraries versions). Abandoned Linux GUI software generally doesn't work in newer Linux distros. Most well written GUI applications for Windows 95 will work in Windows 7 (15 years of compatibility on binary level).
  
  New applications linked only against lib C will refuse to work in old distros. (Even though they are 100% source compatible with old distros).
  
  New libraries versions bugs, regressions and incompatibilities.
  
  Distro upgrade can render your system unusable (kernel might not boot, some features may stop working).
  
  There's a myth that backwards compatibility is a non-issue in Linux because all the software has sources. However a lot of software just cannot be compiled on newer Linux distros due to 1) outdated, conflicting, no longer available libraries and dependencies 2) every GCC release becoming much stricter about C/C++ syntax 3) Users just won't bother compiling old software because they don't know how to 'compile', nor they should know how to do that.
  
  DE developers (KDE/Gnome) routinely cardinally change UI elements, configuration, behaviour, etc.
  
  Open Source developers usually don't care about applications behaviour beyond their own usage scenarios. I.e. coreutils developers for no good reasons have broken head/tails functionality which is used by the Loki installer.
  
  Quite often you cannot run new applications in LTS distros. Recent examples: GTK3 based software (there's no official way to use it in RHEL6), and Google Chrome (Google decided to abandon LTS distros).
  
  Linux has a 255 bytes limitation for file names (this translates to just 63 four bytes characters in UTF-8) - not a great deal but copying or using files or directories with long names from your Windows PC can become a serious challenge.
  
  ! Current serious issues with the author's own PC:
  
  1) ALSA's audio mixer works differently than Windows' audio mixer causing an utter confusion.
  
  2) Suspend (specially in EUFI mode) is totally broken. Suspend doesn't work at all actually - NVIDIA refuses to fix this issue which plagues only Linux.
  
  3) RPM package manager is broken.
  
  4) My webcam does not work when being initialized by Skype (it doesn't do anything unusual).
  
  Most applications that exist both for Windows and Linux start up faster in Windows than in Linux (barring SSD disks but they are still prohibitively costly), sometimes several times faster.
  
  All native Linux filesystems are case sensitive about filenames which utterly confuses most users. This wonderful peculiarity doesn't have any sensible rationale.
  
  Ext4 Linux filesystem cannot be fully defragmented. It supports defragmentation but only for individual files. You cannot combine data and turn free space into one continuous area. XFS supports full defragmentation though, but by default most distros offer Ext4 and there's no official safe way to convert ext4 to XFS.
  
  Linux preserves file creation time only for certain filesystems (ext4, NTFS, fat). Another issue is that user space utilities currently cannot view or modify this time (ext4 `debugfs` works only under root).
  
  A lot of UNIX problems (PDF, 3MB) apply to Linux/GNU as well.
  
  There's a lot of hostility in the open source community.
  
  This is so freaking "amazing", you absolutely have to read it - the developer behind XScreenSaver is fighting with Debian developers.
  
  Random ramblings or why you may hate Linux (some are severely outdated/irrelevant/fixed but they are left for posterity to see the innards of the open source movement and community):
  
  1) KDE: troubleshooting kded4 bugs.
  
  2) A big discussion on Slashdot as to why people still prefer Windows over Linux.
  
  3) Another big discussion on Slashdot as to why Linux still lacks.
  
  4) Any KDE plasmoid can freeze the entire KDE desktop - seems to be fixed in KDE5.
  
  5) Why Desktop Linux Hasn't Taken Off - Slashdot.
  
  6) Torvalds Slams NVIDIA's Linux Support - Slashdot.
  
  7) Are Open-Source Desktops Losing Competitiveness? - Slashdot (A general consensus - No).
  
  8) Broadcom Wi-Fi adapters under Linux are a PITA.
  
  9) A Gnome developer laments the state of Gnome 3 development.
  
  10) Fuck LTS distros: Google Says Red Hat Enterprise Linux 6 Is Obsolete (WTF?! Really?!).
  
  11) A rant about Gnome 3 APIs.
  
  12) OMFG: Ubuntu has announced Mir, an alternative to X.org/Wayland.
  
  13) KDE's mail client cannot properly handle IMAP mail accounts.
  
  14) Desktop Linux security is a mess (zipped MS Powerpoint presentation, 1.3MB) + 13 HID vulnerabilities.
  
  15) Yet another Gnome developer concurs that Gnome 3 was a big mistake.
  
  16) Gnome developers keep fucking hard their users.
  
  17) Fixed now: KDE developers' yet another fuck up called, "You want to disable files indexing? Really? Fuck you! Eat what we're giving you."
  
  18) Linux "security" is a mess. For the past six months two local root exploits have been discovered in the Linux kernel. Six critical issues have been discovered in OpenSSL (which allow remote exploitation, information disclosure and MITM).
  
  19) Skype developers dropped support for ALSA. Wow, great, fuck compatibility, fuck old distros, fuck the people for whom PulseAudio is not an option.
  
  20) Well, fuck compatibility, there are now three versions of OpenSSL in the wild: OpenSSL itself, BoringSSL by Google, LibReSSL by OpenBSD. All with incompatible APIs/ABIs (OpenSSL itself breaks API/ABIs quite often).
  
  21) KDE developers decided to remove support for the xembed based system tray, so your old applications will not have a system tray icon, unless you patch your system. Wonder-fuck-you-ful. The feature has finally been reintroduced in Plasma 5.5.5 after two years (!!) of users' remonstrance.
  
  22) KDE developers/maintainers silently delete unpleasant users' comments on dot.kde.org. KDE developers ignore bugs posted at bugs.kde.org.
  
  23) Welcome: PulseAudio emulation for Skype. Audio is not fucked up in Linux you said?
  
  24) UDP connections monitoring is a hell on earth.
  
  25) Linux has become way too complex even for ... Linux developers.
  
  26) Linux developers gave up on maintaining API/ABI compatibility even among modern distros and decided to bundle a full Linux stack with every app to virtualize it. This is so f*cked up, I've got no words. Oh, Wayland is required for that, so this thing is not going to take off any time soon.
  
  27) Out of 20 most played/popular games in Steam only three are available for Linux. I'm not saying it's bad, it's just what it is.
  
  28) This article is getting unwieldy but fuck it, even Linus admits that API/ABI compatibility in Linux is beyond fucked up: "making binaries for Linux desktop applications is a major fucking pain in the ass. You don’t make binaries for Linux, you make binaries for Fedora 19, Fedora 20, maybe even RHEL5 from 10 years ago. You make binaries for Debian Stable…well actually no, you don’t make binaries for Debian Stable because Debian Stable has libraries that are so old that anything built in the last century doesn’t work."
  
  29) KDE is spiralling out of control (besides its code quality is beyond horrible - several crucial parts of the KDE SC, like KMail/akonadi, are barely functional): people refuse to maintain literally hundreds of KDE packages.
  
  30) Google Chrome stopped supporting 32bit distros starting March 2016. They don't care that 32bit distros and applications in some cases require up to 40% less RAM.
  
  31) Let's have some fun! ... or hatred maybe? Native Linux games do ... not work under Linux. Fuck compatibility. Fuck it! This "OS" is a fucking joke.
  
  Software development under and for Linux
  
  ! Stable API nonsense: you cannot develop kernel drivers out of the kernel tree, because they will soon become incompatible with mainline. That's the sole reason why RHEL and other LTS distros are so popular in enterprise.
  
  Games development: no complete multimedia framework.
  
  ! Hostility towards third party developers: many open source projects are extremely self-contained, i.e. if you try to develop your open source project using open source library X or if you try to bring your suggestions to some open source project, you'll be met with extreme hostility.
  
  A lot of points mentioned above apply to this category, they won't be reiterated.
  
  Enterprise level Linux problems:
  
  Most distros don't allow you to easily set up a server with e.g. such a configuration: Samba, SMTP/POP3, Apache HTTP Auth and FTP where all users are virtual. LDAP is a PITA. Authentication against MySQL/any other DB is also a PITA.
  
  ! No software (group) policies.
  
  ! No standard way of software deployment (pushing software via SSH is indeed an option, but it's in no way standard, easy to use or obvious - you can use a sledgehammer to crack nuts the same way).
  
  ! No CIFS/AD level replacement/equivalent (SAMBA doesn't count for many reasons): 1) Centralized and easily manageable user directory. 2) Simple file sharing. 3) Simple (LAN) computers discovery and browsing.
  
  No native production ready filesystem with deduplication and file compression. No filesystems at all to support per-file encryption (ext4fs implements encryption for directories starting from Linux 4.1 but it will take months before desktop environments start supporting this feature).
  
  !! No proper RDP/Terminal Services alternative (built-in, standardized across distros, high level of compression, low latency, needs zero effort to be set up, integrated with Linux PAM, totally encrypted: authentication + traffic, digital signature like SSH).
  
  Reactie gewijzigd op 6 november 2016 om 21:12 |
- 0 +1
  
  DiGiBaL op 3 november 2016 om 23:29 Meld misbruik
  
  Dus blijkbaar wel ... ook op mijn ouders dr PC voor wat zij doen. En die is qua specs nog lager dan dit.
  
  |
- +2 +3
  
  Powermax op 2 november 2016 om 23:36 Meld misbruik
  
  uberbofh:
  
  Maar er is helemaal geen Linux geprobeerd!
  
  Wij verwachtten, net als met de verschillende Linux-distributies, tegen problemen aan te lopen met de videochip en dat de 64-bit grafische drivers voor Windows 10 niet overweg kunnen met de oude videochip.
  
  en
  
  De 3rd-party USB Wifi-adapter die onder Linux niet aan de praat te krijgen was werkte out-of-the-box onder Windows 10 en zelfs het kijken van video's ging makkelijk en soepel.
  
  Je was waarschijnlijk zo gefrustreerd over de conclusie dat je er overheen gelezen hebt.
  
  Reactie gewijzigd op 3 november 2016 om 11:32 |
- +1 +2
  
  uberbofh op 3 november 2016 om 00:21 Meld misbruik
  
  Eigenlijk is het meer lachwekkend dat de eerste actie is om het geheugen te verdubbelen. Hiermee is het per definitie geen oud systeem meer. Vriend en vijand weet dat Windows tenminste 2x zo veel geheugen nodig heeft . Dat de eerder geteste Linux distro niet eens wordt genoemd is not done als je windows daar toch mee gaat vergelijken.
  
  Dus lachwekkend om het geheugen te verdubbelen voor de test.
  
  Reactie gewijzigd op 3 november 2016 om 09:53 |
- +3 +4
  
  Powermax op 3 november 2016 om 08:16 Meld misbruik
  
  Lachwekkend om te zien hoe je jezelf er weer probeert uit te lullen. Volgende keer even tot 10 tellen voor je weer domme dingen opschrijft. Je maakt jezelf zo ontzettend belachelijk op deze manier.
  
  Reactie gewijzigd op 4 november 2016 om 22:42 |
- 0 +1
  
  uberbofh op 3 november 2016 om 12:25 Meld misbruik
  
  Vriend en vijand is het er over eens dat windows een geheugenvreter is, als je dan als eerste actie het geheugen gaat verdubbelen tja....
  
  |
- +2 +3
  
  Powermax op 3 november 2016 om 13:35 Meld misbruik
  
  Zoals vriend en vijand het er nog altijd over eens is dat hardware support onder linux nog altijd te wensen overlaat.
  
  Reactie gewijzigd op 4 november 2016 om 22:43 |
- +1 +2
  
  uberbofh op 3 november 2016 om 15:42 Meld misbruik
  
  Is al lang verleden tijd. Linux support out-of-the-box meer hardware dan Windows.
  
  Reactie gewijzigd op 3 november 2016 om 17:28 |
- +3 +4
  
  Zorba op 3 november 2016 om 16:31 Meld misbruik
  
  Niet in deze test ;)
  
  Reactie gewijzigd op 5 november 2016 om 08:32 |
- +1 +2
  
  Ctrl op 3 november 2016 om 18:16 Meld misbruik
  
  Waardoor je je ook kunt afvragen hoe representatief deze test is.
  
  Reactie gewijzigd op 5 november 2016 om 09:37 |
- +3 +4
  
  Zorba op 3 november 2016 om 20:20 Meld misbruik
  
  Voorspelbaar.. als de testuitslag ongewenste resultaten geeft dan klopt de test niet ;)
  
  RDF?
  
  Reactie gewijzigd op 5 november 2016 om 08:33 |
- 0 +1
  
  Ctrl op 3 november 2016 om 20:48 Meld misbruik
  
  Dat staat er niet, toch?
  
  |
- +1 +2
  
  uberbofh op 3 november 2016 om 20:50 Meld misbruik
  
  Er is hier niemand, behalve Zorba en Digibal die dat zegt.
  
  1. maar daar ging de test niet over, is dat ze niet zeggen wat ze met welke Linux hebben gedaan, volgens de tekst van de schrijver zijn ze er niet eens mee begonnen omdat ze geluiden hadden opgevangen:
  
  In eerste instantie was het de bedoeling om Lubuntu op de laptop te installeren, maar wij vingen hier en daar geluiden op dat deze laptop niet altijd even goed overweg kon met verschillende Linux-distributies
  
  2. Ze hebben een testje gedaan om te kijken of windows 10 er op draait. Om daar zeker van te zijn hebben ze het geheugen verdubbeld en is het een flinke bak geworden waar zelfs 4 gevirtualiseerde Linux systemen prima tegelijk op draaien.
  
  Reactie gewijzigd op 3 november 2016 om 22:23 |
- +2 +3
  
  Zorba op 4 november 2016 om 11:45 Meld misbruik
  
  Zie de systemen hieronder die prima draaien.
  
  Dell's D430: Dual core, 1.33 GHz, 2 G RAM
  
  Compaq Mini CQ10 uit 2011 die ik wel ooit heb geüpgraded naar 2GB.
  
  En zo zijn er miljoenen gebruikers die W10 op verouderde hardware prima gebruiken.
  
  Accepteer dat gewoon ( ben blij voor ze!) en zeur niet over speciaal uitgeklede linux versies die ook kunnen wat de originele XP op 265 MB of W2K op 128MB ook al lang konden.
  
  Reactie gewijzigd op 5 november 2016 om 08:33 |
- 0 +1
  
  uberbofh op 4 november 2016 om 13:10 Meld misbruik
  
  En zo zijn er miljoenen gebruikers die W10 op verouderde hardware prima gebruiken
  
  NIet zonder te upgraden naar meer RAM. Leuk klusje voor Mien om de hoek maar daar leef jij weer van natuurlijk.
  
  |
- +1 +2
  
  Zorba op 4 november 2016 om 22:22 Meld misbruik
  
  kijk nu eens naar die hier genoemde hardware.. gewoon met 2GB geheugen.
  
  Maar ja.. [Link]
  
  Reactie gewijzigd op 5 november 2016 om 08:33 |
- 0 +1
  
  uberbofh op 4 november 2016 om 22:56 Meld misbruik
  
  Die hebben niet meegedaan met de installatie. Zijn fanboys.
  
  Antivirus ook even uitgezet voor de test.
  
  |
- +1 +2
  
  DiGiBaL op 4 november 2016 om 22:56 Meld misbruik
  
  Je leest Zorba's antwoord niet en daarnaast; ik heb hier twee tablets, HP Stream 7 met 1 GB en een no-name Chinese brand Chuwi met 2 GB. Beiden draaien Windows 10 apps incl. zonder enige pick-up. Perfecte consumptie devices voor onder 150 euri.
  
  Reactie gewijzigd op 5 november 2016 om 08:34 |
- +4 +5
  
  quinckslag op 2 november 2016 om 19:30 Meld misbruik
  
  Ik draai windows 10 op enkele Dell's D430: Dual core, 1.33 GHz, 2 G RAM en het werkt prima! Met een gewone harde schijf (5400 rpm) is het goed te doen, met een SSD werkt het gewoon erg vlot! Alle hardware wordt herkend, behalve een specifieke Wifi module, maar gelukkig had ik nog een reserve (gekocht via eBay).
  
  In alle gevallen is een gratis upgrade uitgevoerd vanuit Windows 7 Ultimate.
  
  Reactie gewijzigd op 3 november 2016 om 11:33 |
- +3 +4
  
  pipolakki op 2 november 2016 om 17:57 Meld misbruik
  
  dell inspiron 9100 laptop 4 gig alles werkend win 10
  
  2x dell optiplex 2008-2010 4 gig alles werkend win 10
  
  win 10 kun je opstarten zonder dat hij kijkt naar gecertificeerde drivers, zodoende zijn nagenoeg alle win7 en viesbah drivers te installeren zonder gemekker .
  
  Reactie gewijzigd op 3 november 2016 om 08:52 |
- +3 +4
  
  eurojojo op 2 november 2016 om 15:34 Meld misbruik
  
  Ik draai Win10 zonder problemen op een Compaq Mini CQ10 uit 2011 die ik wel ooit heb geüpgraded naar 2GB.
  
  Reactie gewijzigd op 3 november 2016 om 08:52 |
Reageren
Reactie bewerken
Misbruik melden

Reageer

Om een reactie te plaatsen moet u ingelogd zijn.

Zo installeerden wij Windows 10 op een oude bak

Er wordt vaak gezegd dat een oude computer nieuw leven kan worden ingeblazen door er Linux op te installeren. "Linux is lichter en kan beter overweg met oude hardware dan Windows." Maar is dat ook zo? Wij namen de proef op de som en installeerden Windows 10 op een tien jaar oude desktop.

Zo installeerden wij Windows 10 op een oude bak

Er wordt vaak gezegd dat een oude computer nieuw leven kan worden ingeblazen door er Linux op te installeren. "Linux is lichter en kan beter overweg met oude hardware dan Windows." Maar is dat ook zo? Wij namen de proef op de som en installeerden Windows 10 op een tien jaar oude desktop.

Meer RAM

ICT-vacatures

Lees meer over

Oudste boven ▾ Reacties

Reageren

Reactie bewerken

Misbruik melden

Reageer

Preview

Gerelateerde vragen

Zo installeerden wij Windows 10 op een oude bak

Er wordt vaak gezegd dat een oude computer nieuw leven kan worden ingeblazen door er Linux op te installeren. "Linux is lichter en kan beter overweg met oude hardware dan Windows." Maar is dat ook zo? Wij namen de proef op de som en installeerden Windows 10 op een tien jaar oude desktop.

Zo installeerden wij Windows 10 op een oude bak

Er wordt vaak gezegd dat een oude computer nieuw leven kan worden ingeblazen door er Linux op te installeren. "Linux is lichter en kan beter overweg met oude hardware dan Windows." Maar is dat ook zo? Wij namen de proef op de som en installeerden Windows 10 op een tien jaar oude desktop.

Delen

Meer RAM

ICT-vacatures

Delen

Lees meer over

Oudste boven ▾ Reacties

Reageren

Reactie bewerken

Misbruik melden

Reageer

Preview

Gerelateerde vragen