β² 335 βΌ The Creator of Git and Linux (thelemmy.club) submitted 4 hours ago by rulray@lemmy.dbzer0.com to c/linuxmemes@lemmy.world 82 comments fedilink hide all child comments
[β] bobslaede@feddit.dk 60 points 3 hours ago (9 children) Isn't it a bit strange not to change your wallpaper to something different than the default Windows one? permalink fedilink source hideshow 18 child comments replies: [β] altkey@lemmy.dbzer0.com 2 points 15 minutes ago First time I saw that picture, win11 was new, and having it running meant you had a rather recently built PC with a TPM module. So, an additional layer of a (satirical?) hardware flex that I don't think goes well with, well, the worse Windows at the time. permalink fedilink source parent [β] wonderingwanderer@sopuli.xyz 2 points 1 hour ago When I switched to Endeavor, Ganymede was the Default wallpaper and I fucking loved it so I kept it. The next update it changed (since it was still set to default), so I dug through an rsync backup to find it and changed it back to Ganymede permalink fedilink source parent [β] Pomal@sh.itjust.works 30 points 3 hours ago (1 child) For the Arch defaults, I find their stock wallpapers generally pleasing in a weird n-dimensional way. When I was a young microslopper, it was always whatever brought me joy from newgrounds that week. permalink fedilink source parent hideshow 2 child comments replies: [β] felsiq@piefed.zip 20 points 2 hours ago (3 children) Archβ¦ defaults?? Are you thinking of cachyOS or maybe plasmaβs defaults? permalink fedilink source parent hideshow 6 child comments replies: [β] Undearius@lemmy.ca 23 points 2 hours ago (1 child) No, the base CLI is pleasing permalink fedilink source parent hideshow 2 child comments replies: [β] Pomal@sh.itjust.works 2 points 1 hour ago This is also a true experience xD permalink fedilink source parent [β] Pomal@sh.itjust.works 4 points 1 hour ago Plasma, le derp, ty permalink fedilink source parent [β] SaharaMaleikuhm@feddit.org 6 points 2 hours ago Different guy, but I like my Plasma wallpapers. I mean I rarely get to see it cause I got stuff to do, but they are nice enough. permalink fedilink source parent [β] rtxn@lemmy.world 11 points 3 hours ago The average tech bro doesn't have the skill to maintain a single system long enough for customizations to matter. permalink fedilink source parent [β] gon@lemmy.dbzer0.com 10 points 3 hours ago (2 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [β] eodur@piefed.social 11 points 3 hours ago (3 children) 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. permalink fedilink source parent hideshow 6 child comments replies: [β] Pomal@sh.itjust.works 22 points 3 hours ago (1 child) permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 3 points 3 hours ago* (last edited 3 hours ago) (3 children) 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. permalink fedilink source parent hideshow 6 child comments replies: [β] luciferofastora@feddit.org 3 points 1 hour ago Taking a comic about a flimsy excuse and doing a serious analysis of a joke problem is such an xkcd thing to do. permalink fedilink source parent [β] lime@feddit.nu 15 points 3 hours ago (1 child) that xkcd comic is coming up on 20 years old. most computers didn't have multiple cores yet. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 1 point 3 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] lime@feddit.nu 2 points 2 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 2 points 2 hours ago* 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. Wikipedia says that ccache goes back 24 years. permalink fedilink source parent [β] grue@lemmy.world 2 points 1 hour ago 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...?! permalink fedilink source parent [β] gon@lemmy.dbzer0.com 8 points 3 hours ago 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. permalink fedilink source parent [β] tal@lemmy.today 2 points 3 hours ago 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. permalink fedilink source parent [β] Zombie@feddit.uk 7 points 3 hours ago (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [β] gon@lemmy.dbzer0.com 3 points 3 hours ago Hilarious btw permalink fedilink source parent [β] Honytawk@discuss.tchncs.de 5 points 3 hours ago Maybe Linus also has that background. But we wouldn't know since his screen is off. permalink fedilink source parent [β] dudeface@lemmy.world 2 points 2 hours ago I never pick a custom image for my my OS background, I never see it Sometimes I switch it to grey or black permalink fedilink source parent [β] xylol@leminal.space 2 points 2 hours ago I never look at the wallpaper long enough to care about changing whatever is default permalink fedilink source parent [β] Waterpumpee@lemmus.org 2 points 3 hours ago since i have family and cant change it to prn,i keep it at default too. Honestly though, i barely see it. Theres always some ui over it. permalink fedilink source parent
[β] altkey@lemmy.dbzer0.com 2 points 15 minutes ago First time I saw that picture, win11 was new, and having it running meant you had a rather recently built PC with a TPM module. So, an additional layer of a (satirical?) hardware flex that I don't think goes well with, well, the worse Windows at the time. permalink fedilink source parent
[β] wonderingwanderer@sopuli.xyz 2 points 1 hour ago When I switched to Endeavor, Ganymede was the Default wallpaper and I fucking loved it so I kept it. The next update it changed (since it was still set to default), so I dug through an rsync backup to find it and changed it back to Ganymede permalink fedilink source parent
[β] Pomal@sh.itjust.works 30 points 3 hours ago (1 child) For the Arch defaults, I find their stock wallpapers generally pleasing in a weird n-dimensional way. When I was a young microslopper, it was always whatever brought me joy from newgrounds that week. permalink fedilink source parent hideshow 2 child comments replies: [β] felsiq@piefed.zip 20 points 2 hours ago (3 children) Archβ¦ defaults?? Are you thinking of cachyOS or maybe plasmaβs defaults? permalink fedilink source parent hideshow 6 child comments replies: [β] Undearius@lemmy.ca 23 points 2 hours ago (1 child) No, the base CLI is pleasing permalink fedilink source parent hideshow 2 child comments replies: [β] Pomal@sh.itjust.works 2 points 1 hour ago This is also a true experience xD permalink fedilink source parent [β] Pomal@sh.itjust.works 4 points 1 hour ago Plasma, le derp, ty permalink fedilink source parent [β] SaharaMaleikuhm@feddit.org 6 points 2 hours ago Different guy, but I like my Plasma wallpapers. I mean I rarely get to see it cause I got stuff to do, but they are nice enough. permalink fedilink source parent
[β] felsiq@piefed.zip 20 points 2 hours ago (3 children) Archβ¦ defaults?? Are you thinking of cachyOS or maybe plasmaβs defaults? permalink fedilink source parent hideshow 6 child comments replies: [β] Undearius@lemmy.ca 23 points 2 hours ago (1 child) No, the base CLI is pleasing permalink fedilink source parent hideshow 2 child comments replies: [β] Pomal@sh.itjust.works 2 points 1 hour ago This is also a true experience xD permalink fedilink source parent [β] Pomal@sh.itjust.works 4 points 1 hour ago Plasma, le derp, ty permalink fedilink source parent [β] SaharaMaleikuhm@feddit.org 6 points 2 hours ago Different guy, but I like my Plasma wallpapers. I mean I rarely get to see it cause I got stuff to do, but they are nice enough. permalink fedilink source parent
[β] Undearius@lemmy.ca 23 points 2 hours ago (1 child) No, the base CLI is pleasing permalink fedilink source parent hideshow 2 child comments replies: [β] Pomal@sh.itjust.works 2 points 1 hour ago This is also a true experience xD permalink fedilink source parent
[β] Pomal@sh.itjust.works 2 points 1 hour ago This is also a true experience xD permalink fedilink source parent
[β] SaharaMaleikuhm@feddit.org 6 points 2 hours ago Different guy, but I like my Plasma wallpapers. I mean I rarely get to see it cause I got stuff to do, but they are nice enough. permalink fedilink source parent
[β] rtxn@lemmy.world 11 points 3 hours ago The average tech bro doesn't have the skill to maintain a single system long enough for customizations to matter. permalink fedilink source parent
[β] gon@lemmy.dbzer0.com 10 points 3 hours ago (2 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [β] eodur@piefed.social 11 points 3 hours ago (3 children) 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. permalink fedilink source parent hideshow 6 child comments replies: [β] Pomal@sh.itjust.works 22 points 3 hours ago (1 child) permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 3 points 3 hours ago* (last edited 3 hours ago) (3 children) 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. permalink fedilink source parent hideshow 6 child comments replies: [β] luciferofastora@feddit.org 3 points 1 hour ago Taking a comic about a flimsy excuse and doing a serious analysis of a joke problem is such an xkcd thing to do. permalink fedilink source parent [β] lime@feddit.nu 15 points 3 hours ago (1 child) that xkcd comic is coming up on 20 years old. most computers didn't have multiple cores yet. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 1 point 3 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] lime@feddit.nu 2 points 2 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 2 points 2 hours ago* 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. Wikipedia says that ccache goes back 24 years. permalink fedilink source parent [β] grue@lemmy.world 2 points 1 hour ago 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...?! permalink fedilink source parent [β] gon@lemmy.dbzer0.com 8 points 3 hours ago 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. permalink fedilink source parent [β] tal@lemmy.today 2 points 3 hours ago 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. permalink fedilink source parent [β] Zombie@feddit.uk 7 points 3 hours ago (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [β] gon@lemmy.dbzer0.com 3 points 3 hours ago Hilarious btw permalink fedilink source parent
[β] eodur@piefed.social 11 points 3 hours ago (3 children) 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. permalink fedilink source parent hideshow 6 child comments replies: [β] Pomal@sh.itjust.works 22 points 3 hours ago (1 child) permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 3 points 3 hours ago* (last edited 3 hours ago) (3 children) 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. permalink fedilink source parent hideshow 6 child comments replies: [β] luciferofastora@feddit.org 3 points 1 hour ago Taking a comic about a flimsy excuse and doing a serious analysis of a joke problem is such an xkcd thing to do. permalink fedilink source parent [β] lime@feddit.nu 15 points 3 hours ago (1 child) that xkcd comic is coming up on 20 years old. most computers didn't have multiple cores yet. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 1 point 3 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] lime@feddit.nu 2 points 2 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 2 points 2 hours ago* 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. Wikipedia says that ccache goes back 24 years. permalink fedilink source parent [β] grue@lemmy.world 2 points 1 hour ago 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...?! permalink fedilink source parent [β] gon@lemmy.dbzer0.com 8 points 3 hours ago 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. permalink fedilink source parent [β] tal@lemmy.today 2 points 3 hours ago 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. permalink fedilink source parent
[β] Pomal@sh.itjust.works 22 points 3 hours ago (1 child) permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 3 points 3 hours ago* (last edited 3 hours ago) (3 children) 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. permalink fedilink source parent hideshow 6 child comments replies: [β] luciferofastora@feddit.org 3 points 1 hour ago Taking a comic about a flimsy excuse and doing a serious analysis of a joke problem is such an xkcd thing to do. permalink fedilink source parent [β] lime@feddit.nu 15 points 3 hours ago (1 child) that xkcd comic is coming up on 20 years old. most computers didn't have multiple cores yet. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 1 point 3 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] lime@feddit.nu 2 points 2 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 2 points 2 hours ago* 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. Wikipedia says that ccache goes back 24 years. permalink fedilink source parent [β] grue@lemmy.world 2 points 1 hour ago 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...?! permalink fedilink source parent
[β] tal@lemmy.today 3 points 3 hours ago* (last edited 3 hours ago) (3 children) 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. permalink fedilink source parent hideshow 6 child comments replies: [β] luciferofastora@feddit.org 3 points 1 hour ago Taking a comic about a flimsy excuse and doing a serious analysis of a joke problem is such an xkcd thing to do. permalink fedilink source parent [β] lime@feddit.nu 15 points 3 hours ago (1 child) that xkcd comic is coming up on 20 years old. most computers didn't have multiple cores yet. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 1 point 3 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] lime@feddit.nu 2 points 2 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 2 points 2 hours ago* 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. Wikipedia says that ccache goes back 24 years. permalink fedilink source parent [β] grue@lemmy.world 2 points 1 hour ago 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...?! permalink fedilink source parent
[β] luciferofastora@feddit.org 3 points 1 hour ago Taking a comic about a flimsy excuse and doing a serious analysis of a joke problem is such an xkcd thing to do. permalink fedilink source parent
[β] lime@feddit.nu 15 points 3 hours ago (1 child) that xkcd comic is coming up on 20 years old. most computers didn't have multiple cores yet. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 1 point 3 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] lime@feddit.nu 2 points 2 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 2 points 2 hours ago* 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. Wikipedia says that ccache goes back 24 years. permalink fedilink source parent
[β] tal@lemmy.today 1 point 3 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] lime@feddit.nu 2 points 2 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 2 points 2 hours ago* 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. Wikipedia says that ccache goes back 24 years. permalink fedilink source parent
[β] lime@feddit.nu 2 points 2 hours ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] tal@lemmy.today 2 points 2 hours ago* 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. Wikipedia says that ccache goes back 24 years. permalink fedilink source parent
[β] tal@lemmy.today 2 points 2 hours ago* 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. Wikipedia says that ccache goes back 24 years. permalink fedilink source parent
[β] grue@lemmy.world 2 points 1 hour ago 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...?! permalink fedilink source parent
[β] gon@lemmy.dbzer0.com 8 points 3 hours ago 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. permalink fedilink source parent
[β] tal@lemmy.today 2 points 3 hours ago 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. permalink fedilink source parent
[β] Zombie@feddit.uk 7 points 3 hours ago (1 child) 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 permalink fedilink source parent hideshow 2 child comments replies: [β] gon@lemmy.dbzer0.com 3 points 3 hours ago Hilarious btw permalink fedilink source parent
[β] Honytawk@discuss.tchncs.de 5 points 3 hours ago Maybe Linus also has that background. But we wouldn't know since his screen is off. permalink fedilink source parent
[β] dudeface@lemmy.world 2 points 2 hours ago I never pick a custom image for my my OS background, I never see it Sometimes I switch it to grey or black permalink fedilink source parent
[β] xylol@leminal.space 2 points 2 hours ago I never look at the wallpaper long enough to care about changing whatever is default permalink fedilink source parent
[β] Waterpumpee@lemmus.org 2 points 3 hours ago since i have family and cant change it to prn,i keep it at default too. Honestly though, i barely see it. Theres always some ui over it. permalink fedilink source parent