), because then my feed is a bit awkward to ready for non-Yarn clients. 😅
), because then my feed is a bit awkward to ready for non-Yarn clients. 😅
), because then my feed is a bit awkward to ready for non-Yarn clients. 😅
), because then my feed is a bit awkward to ready for non-Yarn clients. 😅
I was thinking back to CD players. Switching tracks took a moment, although I don’t know anymore how long exactly. IIRC, playing CDs on a computer was a bit slower than in a dedicated player.
Don’t worry, switching to the next OGG file on my disk is basically instant. 😅
I was thinking back to CD players. Switching tracks took a moment, although I don’t know anymore how long exactly. IIRC, playing CDs on a computer was a bit slower than in a dedicated player.
Don’t worry, switching to the next OGG file on my disk is basically instant. 😅
I was thinking back to CD players. Switching tracks took a moment, although I don’t know anymore how long exactly. IIRC, playing CDs on a computer was a bit slower than in a dedicated player.
Don’t worry, switching to the next OGG file on my disk is basically instant. 😅
I was thinking back to CD players. Switching tracks took a moment, although I don’t know anymore how long exactly. IIRC, playing CDs on a computer was a bit slower than in a dedicated player.
Don’t worry, switching to the next OGG file on my disk is basically instant. 😅
That’s what I meant by “absolute” performance: A human being tolerates a system boot up time of 0.5-2 minutes, for example, so there’s an absolute/fixed duration that any task is allowed to take. Boot: 0.5-2 minutes. Opening Word: 1-10 seconds. Saving an image file: 1-10 seconds. Time until the next song starts to play when you click “next track”: 0-5 seconds. Stuff like that. As long as we don’t exceed those durations, people will be more or less happy.
Wasted potential? Ab-so-fucken-lutely.
(Maybe I’m repeating myself. I’m tired. Sorry. 😅)
That’s what I meant by “absolute” performance: A human being tolerates a system boot up time of 0.5-2 minutes, for example, so there’s an absolute/fixed duration that any task is allowed to take. Boot: 0.5-2 minutes. Opening Word: 1-10 seconds. Saving an image file: 1-10 seconds. Time until the next song starts to play when you click “next track”: 0-5 seconds. Stuff like that. As long as we don’t exceed those durations, people will be more or less happy.
Wasted potential? Ab-so-fucken-lutely.
(Maybe I’m repeating myself. I’m tired. Sorry. 😅)
That’s what I meant by “absolute” performance: A human being tolerates a system boot up time of 0.5-2 minutes, for example, so there’s an absolute/fixed duration that any task is allowed to take. Boot: 0.5-2 minutes. Opening Word: 1-10 seconds. Saving an image file: 1-10 seconds. Time until the next song starts to play when you click “next track”: 0-5 seconds. Stuff like that. As long as we don’t exceed those durations, people will be more or less happy.
Wasted potential? Ab-so-fucken-lutely.
(Maybe I’m repeating myself. I’m tired. Sorry. 😅)
That’s what I meant by “absolute” performance: A human being tolerates a system boot up time of 0.5-2 minutes, for example, so there’s an absolute/fixed duration that any task is allowed to take. Boot: 0.5-2 minutes. Opening Word: 1-10 seconds. Saving an image file: 1-10 seconds. Time until the next song starts to play when you click “next track”: 0-5 seconds. Stuff like that. As long as we don’t exceed those durations, people will be more or less happy.
Wasted potential? Ab-so-fucken-lutely.
(Maybe I’m repeating myself. I’m tired. Sorry. 😅)
Browsing the web today feels similar to 25 years ago. Even all this wobbling that my link above demonstrates already existed back then (in a way), but it was caused by images loading so slowly. Then, for a brief moment, some browser (I don’t remember which one) had this brilliant feature of trying to keep the current scrolling position *stable* while the page was still loading. That was great. 😃 This feature then got lost again, probably because it’s too hard to do with JavaScript changing the DOM all the time. So now we’re back to the way it was before.
Corporations should give devs the slowest and oldest machines that they have. 😏 Not only would this be more sustainable, it would also force them to optimize better.
Browsing the web today feels similar to 25 years ago. Even all this wobbling that my link above demonstrates already existed back then (in a way), but it was caused by images loading so slowly. Then, for a brief moment, some browser (I don’t remember which one) had this brilliant feature of trying to keep the current scrolling position *stable* while the page was still loading. That was great. 😃 This feature then got lost again, probably because it’s too hard to do with JavaScript changing the DOM all the time. So now we’re back to the way it was before.
Corporations should give devs the slowest and oldest machines that they have. 😏 Not only would this be more sustainable, it would also force them to optimize better.
Browsing the web today feels similar to 25 years ago. Even all this wobbling that my link above demonstrates already existed back then (in a way), but it was caused by images loading so slowly. Then, for a brief moment, some browser (I don’t remember which one) had this brilliant feature of trying to keep the current scrolling position *stable* while the page was still loading. That was great. 😃 This feature then got lost again, probably because it’s too hard to do with JavaScript changing the DOM all the time. So now we’re back to the way it was before.
Corporations should give devs the slowest and oldest machines that they have. 😏 Not only would this be more sustainable, it would also force them to optimize better.
Browsing the web today feels similar to 25 years ago. Even all this wobbling that my link above demonstrates already existed back then (in a way), but it was caused by images loading so slowly. Then, for a brief moment, some browser (I don’t remember which one) had this brilliant feature of trying to keep the current scrolling position *stable* while the page was still loading. That was great. 😃 This feature then got lost again, probably because it’s too hard to do with JavaScript changing the DOM all the time. So now we’re back to the way it was before.
Corporations should give devs the slowest and oldest machines that they have. 😏 Not only would this be more sustainable, it would also force them to optimize better.
https://movq.de/v/112a927861/hiccupfx/
😂😭
https://movq.de/v/112a927861/hiccupfx/
😂😭
https://movq.de/v/112a927861/hiccupfx/
😂😭
https://movq.de/v/112a927861/hiccupfx/
😂😭
As we all know, writing a Wayland compositor from scratch is next to impossible. Luckily, there’s the wlroots project which aims to build a base library for this task. Basically every compositor except for GNOME and KDE uses it. (This is good! The less fragmentation, the better.)
wlroots is still very volatile, lots of changes with every release. Downstream users (i.e., the projects that write the actual compositor) have to constantly “chase” changes in wlroots. dwl, my favorite compositor at the moment, has recently switched their
main branch to target the wlroots *git* version instead of the latest release. My understanding is that they *have* to do this in order to keep up with wlroots (maybe I’m wrong).Everything is volatile and a moving target.
Why does any of this matter for me? Because I have to eventually fork dwl or at least keep a patch set, and I don’t have the stamina to constantly fiddle with this stuff. I’m running my own X11 window manager, it’s highly specialized, and using just “some Wayland compositor out there” is a *huge* step backward that I’m not willing to take. I tried, it’s just painful and annoying with *zero* benefits.
So … it was fun experimenting with Wayland a bit, but I’m now back to waiting for things to settle down considerably.
As we all know, writing a Wayland compositor from scratch is next to impossible. Luckily, there’s the wlroots project which aims to build a base library for this task. Basically every compositor except for GNOME and KDE uses it. (This is good! The less fragmentation, the better.)
wlroots is still very volatile, lots of changes with every release. Downstream users (i.e., the projects that write the actual compositor) have to constantly “chase” changes in wlroots. dwl, my favorite compositor at the moment, has recently switched their
main branch to target the wlroots *git* version instead of the latest release. My understanding is that they *have* to do this in order to keep up with wlroots (maybe I’m wrong).Everything is volatile and a moving target.
Why does any of this matter for me? Because I have to eventually fork dwl or at least keep a patch set, and I don’t have the stamina to constantly fiddle with this stuff. I’m running my own X11 window manager, it’s highly specialized, and using just “some Wayland compositor out there” is a *huge* step backward that I’m not willing to take. I tried, it’s just painful and annoying with *zero* benefits.
So … it was fun experimenting with Wayland a bit, but I’m now back to waiting for things to settle down considerably.
As we all know, writing a Wayland compositor from scratch is next to impossible. Luckily, there’s the wlroots project which aims to build a base library for this task. Basically every compositor except for GNOME and KDE uses it. (This is good! The less fragmentation, the better.)
wlroots is still very volatile, lots of changes with every release. Downstream users (i.e., the projects that write the actual compositor) have to constantly “chase” changes in wlroots. dwl, my favorite compositor at the moment, has recently switched their
main branch to target the wlroots *git* version instead of the latest release. My understanding is that they *have* to do this in order to keep up with wlroots (maybe I’m wrong).Everything is volatile and a moving target.
Why does any of this matter for me? Because I have to eventually fork dwl or at least keep a patch set, and I don’t have the stamina to constantly fiddle with this stuff. I’m running my own X11 window manager, it’s highly specialized, and using just “some Wayland compositor out there” is a *huge* step backward that I’m not willing to take. I tried, it’s just painful and annoying with *zero* benefits.
So … it was fun experimenting with Wayland a bit, but I’m now back to waiting for things to settle down considerably.
As we all know, writing a Wayland compositor from scratch is next to impossible. Luckily, there’s the wlroots project which aims to build a base library for this task. Basically every compositor except for GNOME and KDE uses it. (This is good! The less fragmentation, the better.)
wlroots is still very volatile, lots of changes with every release. Downstream users (i.e., the projects that write the actual compositor) have to constantly “chase” changes in wlroots. dwl, my favorite compositor at the moment, has recently switched their
main branch to target the wlroots *git* version instead of the latest release. My understanding is that they *have* to do this in order to keep up with wlroots (maybe I’m wrong).Everything is volatile and a moving target.
Why does any of this matter for me? Because I have to eventually fork dwl or at least keep a patch set, and I don’t have the stamina to constantly fiddle with this stuff. I’m running my own X11 window manager, it’s highly specialized, and using just “some Wayland compositor out there” is a *huge* step backward that I’m not willing to take. I tried, it’s just painful and annoying with *zero* benefits.
So … it was fun experimenting with Wayland a bit, but I’m now back to waiting for things to settle down considerably.
gaapgna from a while ago – so this is just normal Aussie slang for AC/DC?! 🤯🥴
gaapgna from a while ago – so this is just normal Aussie slang for AC/DC?! 🤯🥴
gaapgna from a while ago – so this is just normal Aussie slang for AC/DC?! 🤯🥴
gaapgna from a while ago – so this is just normal Aussie slang for AC/DC?! 🤯🥴
> I run it in a Work profile on my GrapheneOS phone that I can switch off at any time
Hmmmmmmm, I like that idea. If I could ban WhatsApp into a second profile and only switch it on every now and then, I would feel a little bit better about it.
(I don't really trust Android, though, and I suspect that apps can still install background services that are *always* active. Pure speculation and paranoid on my part, but still.)
> I run it in a Work profile on my GrapheneOS phone that I can switch off at any time
Hmmmmmmm, I like that idea. If I could ban WhatsApp into a second profile and only switch it on every now and then, I would feel a little bit better about it.
(I don't really trust Android, though, and I suspect that apps can still install background services that are *always* active. Pure speculation and paranoid on my part, but still.)
> I run it in a Work profile on my GrapheneOS phone that I can switch off at any time
Hmmmmmmm, I like that idea. If I could ban WhatsApp into a second profile and only switch it on every now and then, I would feel a little bit better about it.
(I don't really trust Android, though, and I suspect that apps can still install background services that are *always* active. Pure speculation and paranoid on my part, but still.)
> I run it in a Work profile on my GrapheneOS phone that I can switch off at any time
Hmmmmmmm, I like that idea. If I could ban WhatsApp into a second profile and only switch it on every now and then, I would feel a little bit better about it.
(I don't really trust Android, though, and I suspect that apps can still install background services that are *always* active. Pure speculation and paranoid on my part, but still.)
@aelaraji To be honest, I don’t like Matrix that much myself. We don’t use any of the fancy crypto features and all that, no federation either. And clients like “FluffyChat” look and feel pretty much like any other chat client. It’s a rather simple setup. Problem is just that it’s not WhatsApp and *people want WhatsApp*, nothing else. 🫤 (Hence I have little hope that Signal would be a big success.)
@aelaraji To be honest, I don’t like Matrix that much myself. We don’t use any of the fancy crypto features and all that, no federation either. And clients like “FluffyChat” look and feel pretty much like any other chat client. It’s a rather simple setup. Problem is just that it’s not WhatsApp and *people want WhatsApp*, nothing else. 🫤 (Hence I have little hope that Signal would be a big success.)
@aelaraji To be honest, I don’t like Matrix that much myself. We don’t use any of the fancy crypto features and all that, no federation either. And clients like “FluffyChat” look and feel pretty much like any other chat client. It’s a rather simple setup. Problem is just that it’s not WhatsApp and *people want WhatsApp*, nothing else. 🫤 (Hence I have little hope that Signal would be a big success.)
@aelaraji To be honest, I don’t like Matrix that much myself. We don’t use any of the fancy crypto features and all that, no federation either. And clients like “FluffyChat” look and feel pretty much like any other chat client. It’s a rather simple setup. Problem is just that it’s not WhatsApp and *people want WhatsApp*, nothing else. 🫤 (Hence I have little hope that Signal would be a big success.)
> Anyone who reads the CrowdStrike self-description and then buys the product has really earned a major fault.
The nasty thing is: Sysadmins don’t decide this, do they? The management does. And *they* don’t have to clean up this bloody fucking mess.
All the fellow sysadmins who were hit by this have my sympathies. 😂
> Anyone who reads the CrowdStrike self-description and then buys the product has really earned a major fault.
The nasty thing is: Sysadmins don’t decide this, do they? The management does. And *they* don’t have to clean up this bloody fucking mess.
All the fellow sysadmins who were hit by this have my sympathies. 😂
> Anyone who reads the CrowdStrike self-description and then buys the product has really earned a major fault.
The nasty thing is: Sysadmins don’t decide this, do they? The management does. And *they* don’t have to clean up this bloody fucking mess.
All the fellow sysadmins who were hit by this have my sympathies. 😂
> Anyone who reads the CrowdStrike self-description and then buys the product has really earned a major fault.
The nasty thing is: Sysadmins don’t decide this, do they? The management does. And *they* don’t have to clean up this bloody fucking mess.
All the fellow sysadmins who were hit by this have my sympathies. 😂
(I’m just glad it didn’t affect us at work.)