The default wallpaper is meant to be pleasing, and I guess it’s meant to appeal to the average person? I’ve known several people that don’t change their wallpapers or that use that automatic carousel thing with a different image every time you wake the device.
I usually set my wallpaper once right after install then never change it. I only see it for a few seconds right after boot anyways. If you see your wallpaper then you aren’t really doing anything.
I think that there’s a legit rejoinder of “Why aren’t you optimizing the code to reduce compilation time, if it’s such a problem?”
For something like C++, ccache, distcc, PIMPL (to reduce use of templates, which blows up C++ compilation time), precompiled headers, make code more modular to reduce the size of the compilation unit that changes when any one change happens, break stuff into libraries, etc. Look to see whether there are things like build timestamps being inserted into headers that are producing unnecessary recompilations. clang and gcc can profile compilations to identify what’s chewing up time.
I mean, none of the optimizations I listed rely on multiple cores.
It’s true that just running parallel compilation jobs on your build machine is a simple way to speed things up, no disagreement, but it’s not like optimizing compilation time isn’t a thing outside of that.
i was thinking more about tooling, most of that stuff didn’t exist as widely as today and you couldn’t really look for it when waiting for a compile either.
Well…the in-compiler time analysis I think wasn’t as good then, though I recall doing my own ad-hoc profiling, logging time for each unit. But the refactoring stuff should be available.
I dunno how far back distcc goes.
checks git repository
The git log goes back to 2008, so almost 20 years, but it’s also talking about release 3.0 then, so there might have been time outside a VCS or with history that didn’t get imported.
In my experience, [proprietary] projects are doing well if their Makefile isn’t so broken that they have to run it twice just to make sure everything actually compiles. And you want them to actually optimize it…?!
If you see your wallpaper then you aren’t really doing anything.
I use sway these days. It’s tiling, so I rarely see my desktop background anymore.
But not everyone uses a tiling system.
While I like the idea of avoiding having onscreen pixels wasted showing useless information, and I think that tiling systems do help achieve this, I avoided tiling systems for some years, as a fair bit of software still didn’t play well with it (e.g. I remember default behavior with GIMP being half of the screen being the main window, half being the GIMP toolbar window). I think that we’re past that phase now, but there are people who prefer stacking window systems for various reasons and don’t use tiling systems.
The default wallpaper is meant to be pleasing, and I guess it’s meant to appeal to the average person? I’ve known several people that don’t change their wallpapers or that use that automatic carousel thing with a different image every time you wake the device.
I usually set my wallpaper once right after install then never change it. I only see it for a few seconds right after boot anyways. If you see your wallpaper then you aren’t really doing anything.
I think that there’s a legit rejoinder of “Why aren’t you optimizing the code to reduce compilation time, if it’s such a problem?”
For something like C++, ccache, distcc, PIMPL (to reduce use of templates, which blows up C++ compilation time), precompiled headers, make code more modular to reduce the size of the compilation unit that changes when any one change happens, break stuff into libraries, etc. Look to see whether there are things like build timestamps being inserted into headers that are producing unnecessary recompilations.
clangandgcccan profile compilations to identify what’s chewing up time.Taking a comic about a flimsy excuse and doing a serious analysis of a joke problem is such an xkcd thing to do.
that xkcd comic is coming up on 20 years old. most computers didn’t have multiple cores yet.
I mean, none of the optimizations I listed rely on multiple cores.
It’s true that just running parallel compilation jobs on your build machine is a simple way to speed things up, no disagreement, but it’s not like optimizing compilation time isn’t a thing outside of that.
i was thinking more about tooling, most of that stuff didn’t exist as widely as today and you couldn’t really look for it when waiting for a compile either.
Well…the in-compiler time analysis I think wasn’t as good then, though I recall doing my own ad-hoc profiling, logging time for each unit. But the refactoring stuff should be available.
I dunno how far back
distccgoes.checks git repository
The git log goes back to 2008, so almost 20 years, but it’s also talking about release 3.0 then, so there might have been time outside a VCS or with history that didn’t get imported.
Wikipedia says that
ccachegoes back 24 years.In my experience, [proprietary] projects are doing well if their
Makefileisn’t so broken that they have to run it twice just to make sure everything actually compiles. And you want them to actually optimize it…?!IDK man, I like knowing that Frieren is looking out for me in the background. Even if I don’t see it, I appreciate that it’s there.
I use sway these days. It’s tiling, so I rarely see my desktop background anymore.
But not everyone uses a tiling system.
While I like the idea of avoiding having onscreen pixels wasted showing useless information, and I think that tiling systems do help achieve this, I avoided tiling systems for some years, as a fair bit of software still didn’t play well with it (e.g. I remember default behavior with GIMP being half of the screen being the main window, half being the GIMP toolbar window). I think that we’re past that phase now, but there are people who prefer stacking window systems for various reasons and don’t use tiling systems.
You just gotta be careful which automatic carousel you use…
https://www.techspot.com/news/105673-official-bing-wallpaper-app-does-nasty-malware-like.html
Hilarious btw