Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
And in fact, that's what I did with my wife's most recent computer. AMD A8-7600 + 12GB of RAM + 120GB SSD. Extremely cheap and it can still play Minecraft and Call of Duty: Black Ops 2 for my sons.
But if you were going to get an SSD anyway, plus 6+GB of RAM (more for a power user or developer or someone doing video editing or virtualization), then I agree with you. Paying the extra $100 to go from an $80 AMD "APU" to a $120 Intel i3-4160 and compatible motherboard will pay off in spades. Even the $70 Pentium dual core 50 watt G3258 kills any AMD processor this side of the overclocked 220 watt FX series chips for single-threaded performance.
I'm an AMD fan from way back because of the monopoly tricks Intel pulled in the late 1990s early 2000s ( https://en.wikipedia.org/wiki/.... ) - I figure Intel has the money and resources to put towards open source today because of the advantage they unfairly gained due to tricks then.
2. Faster never hurts. There's no extra money made by waiting longer.
3. You wrote "A prod server should not be running piles of things". My point is with systemd you don't have to. I never said init did not also fit that criteria.
4. Sure. But it makes it easier. Just a few text file entries.
5. No, as far as I understand systemd socket activation the startup cost is incurred once on the first request, then after that the process keeps running. So best possible combination.
6. Again, less work to set all of this up. Just a text file.
7. Again, less work to get this feature. With systemd, you get this with "systemctl restart foo.service". No extra commands in every single init script for every single service to make sure all resources are closed down.
8. And you can keep writing them. systemd is compatible with init scripts. So what's the drawback?