3 ms·
Actually I hope that developers start using less powerful machines with less screen estate, less memory, less CPU power and less battery. That should make them
by gioele 15y ago
Actually I hope that developers start using less powerful machines with less screen estate, less memory, less CPU power and less battery. That should make them care about things like focused UX, memory consumption and power-aware programming.
I used a slow PowerPC machine with Linux for a while. After that I really realised how important is to use non-proprietary packages (do you want to scan? here is a 20KB x86-only binary needed for some strange DRM thing) or how important it is to decouple applications from libraries (so that you have to compile less things and spend less time watching your compiler run).
- X-Istence 15y agoI work on building distributed fault tolerant high performance server systems. Compiling all of the code for the project on a Core 2 Duo with 4 GB of ram takes about 2 minutes and uses about 2.5 Gb of ram while linking. I don't care about power consumption or UX with what I am currently working on, it is going to be running on 64 core beasts with 128 GB's of ram... That being said, as a developer I still want a generous amount of screen real estate to get more work done faster, the more code I can display on my screen the better I can and faster I can develop without having to get my tasks back on track, without having to context switch. I understand where you are coming from, and I understand the idea behind it, but at the end of the day I want to spend less time waiting for my compiler.