You obviously didn't fall for the trap that each basket is slightly smaller as you go up. I had assumed they were all the same size and was very confused for a moment.
They made an init system called systemd, and it worked way better than anything prior.
Then they realised that to have a functional and maintainable system, you need a bunch of other system level tooling to be in and around about the same layer as the unit system (time sync, base network, disk mounting, etc.). All of these other things got spun off as daemon projects, for example "systemd-timesyncd". And all got good and consistent command line tooling that made things relatively convenient.
The downside is now power-users saw systems taking over their computer and "violating the Unix philosophy". I would argue that at some level, it doesn't. They've made a suite of relatively independent tools all part of the same group with the purpose of managing the system. It gets things running, it gets users logged in and out, it tells you what when wrong, and it will restart things if it can. System management, do one thing and do it well.
I think the fact is that managing a modern system in a way that "just works" is complicated challenge. Many people either haven't run Ubuntu 9, and done a software update, or have repressed a lot of those memories.
Is it perfect: no. Is it the best model we have so far: I would say so.
I used this setup for my last work laptop. Arch + Win10 on separate drives. I was lucky with my ThinkPad that the UEFI boot select (F12 on boot) was easy to use, so I didn't actually use grub/etc. at all. Just select Windows drive and boot, or select Linux drive and boot (systemd-boot).
During installation, I had each other drive disconnected, such that the bootloader for each system ended up on the right drive. Also makes the installation less stressful as you can wipe and flash the whole drive without worrying about a mix-up.
Did not use secure boot at the time. No issues there from memory. My current setup is win11 and secure boot with openSUSE. Possible, but a bit more of a headache to get right.
Never had any issues with either drive affecting the other. You will be able to get into the windows/NTFS drive from Linux which can cause issues if Windows is in a hibernate state. Try to avoid doing that in general. Windows generally can't see the other filesystem, maybe the boot partition, but it should stick to its own drive. I don't think I ever had cross-contamination.
Kernel level business should have no effect on boot and drive setup. Also UEFI and microcode patches from either OS always seemed to work fine.
I've never seen that Win10 tool before. Honestly I'd recommend just using their USB install media and doing a normal setup. I've tried to be tricky with Windows N in the past but it came back to bite me. It's probably fine regardless if you choose o use it.
Absolute worst case: keep a live USB handy. At least that way you can always get back to a recovery mode if something does go wrong.
Final thoughts: Windows 11 seems to play better with a shared UEFI boot volume. I haven't had an issue so far (>1 year) with windows trying to edit or break the boot setup. I have had Win10 change the boot order in the past, but I feel like that might have been aligned with major windows updates. Probably not much of a concern nowdays.
I agree with the sentiment of being "a huge amount of effort", but I also have issue when looking at things like the YouTube example. Honestly, in that scenario I'd rather it not have an animation than do something janky.
I think it's one of those things where you can't put a blanket statement on either side. If you're going to put effort in (i.e. add animations), it should at least be not worse than doing nothing.
Looks cool. Has anyone used it in earnest? I've always wanted to try a LaTeX successor, but the former is so prevalent that I've been concerned about it losing steam or not being compatible with journals, etc.
I think you might be underestimating uptake. Google suggests upwards of 50% usage. Also I'm fairly certain that a lot of residential infrastructure has been slowly moving to IPv6 in Australia at least. Not an overnight process, but it's happening. Over here we have a lot of newer mobile plans offering IPv6 as well.
I think a big holdback is that a lot of larger corporations will still use IPv4/NAT setups at the top level, even if all of the hardware in the network supports it. "If it's not broke don't fix it." The result is huge amounts of daily traffic coming from these institutions being IPv4 by default, with all devices in WiFi, etc, being lumped into the same group.
Interesting, but I'd have to say that I've been contempt just using an app that doesn't suck (musicolet). The comments about battery could hold a point to me if I were going on a week long trip, or something of the like, but anywhere that would happen for me is somewhere that I wouldn't be taking music/phone for distractions anyway.
I think the finer point I agree with is being able to just have a copy of your own music and play it without being belt-fed opinions or ads. Managing it is always a bit of a pain, but I've got a system that works for me, and MTP on android works better than trying to deal with iTunes in my books.
While it might not work for everything, I have a number of sites that are used for field work that would benefit from these approaches. Things like dashboards an configuration tools.
Arguably, the tools should be desktop apps, or something of the like, but the reality is that using PWAs in this way is easier for everyone (the developer, the distributor, the user).
Not sure about mpv, but I use a gstreamer pipeline to tender cameras to the raw KMS terminal display. It works much more reliably (I.e. Predictable loading times and no stutter) compared to loading a DE first. Noting that it was on a low power RPI.
You obviously didn't fall for the trap that each basket is slightly smaller as you go up. I had assumed they were all the same size and was very confused for a moment.
How?
They made an init system called systemd, and it worked way better than anything prior.
Then they realised that to have a functional and maintainable system, you need a bunch of other system level tooling to be in and around about the same layer as the unit system (time sync, base network, disk mounting, etc.). All of these other things got spun off as daemon projects, for example "systemd-timesyncd". And all got good and consistent command line tooling that made things relatively convenient.
The downside is now power-users saw systems taking over their computer and "violating the Unix philosophy". I would argue that at some level, it doesn't. They've made a suite of relatively independent tools all part of the same group with the purpose of managing the system. It gets things running, it gets users logged in and out, it tells you what when wrong, and it will restart things if it can. System management, do one thing and do it well.
I think the fact is that managing a modern system in a way that "just works" is complicated challenge. Many people either haven't run Ubuntu 9, and done a software update, or have repressed a lot of those memories.
Is it perfect: no. Is it the best model we have so far: I would say so.
Is that the actual hole? I can't believe they could star in this.
Is this not the equivalent of asking someone on the street to pay for a fence for your property so you don't have to look at them?
I used this setup for my last work laptop. Arch + Win10 on separate drives. I was lucky with my ThinkPad that the UEFI boot select (F12 on boot) was easy to use, so I didn't actually use grub/etc. at all. Just select Windows drive and boot, or select Linux drive and boot (systemd-boot).
During installation, I had each other drive disconnected, such that the bootloader for each system ended up on the right drive. Also makes the installation less stressful as you can wipe and flash the whole drive without worrying about a mix-up.
Did not use secure boot at the time. No issues there from memory. My current setup is win11 and secure boot with openSUSE. Possible, but a bit more of a headache to get right.
Never had any issues with either drive affecting the other. You will be able to get into the windows/NTFS drive from Linux which can cause issues if Windows is in a hibernate state. Try to avoid doing that in general. Windows generally can't see the other filesystem, maybe the boot partition, but it should stick to its own drive. I don't think I ever had cross-contamination.
Kernel level business should have no effect on boot and drive setup. Also UEFI and microcode patches from either OS always seemed to work fine.
I've never seen that Win10 tool before. Honestly I'd recommend just using their USB install media and doing a normal setup. I've tried to be tricky with Windows N in the past but it came back to bite me. It's probably fine regardless if you choose o use it.
Absolute worst case: keep a live USB handy. At least that way you can always get back to a recovery mode if something does go wrong.
Final thoughts: Windows 11 seems to play better with a shared UEFI boot volume. I haven't had an issue so far (>1 year) with windows trying to edit or break the boot setup. I have had Win10 change the boot order in the past, but I feel like that might have been aligned with major windows updates. Probably not much of a concern nowdays.
I agree with the sentiment of being "a huge amount of effort", but I also have issue when looking at things like the YouTube example. Honestly, in that scenario I'd rather it not have an animation than do something janky.
I think it's one of those things where you can't put a blanket statement on either side. If you're going to put effort in (i.e. add animations), it should at least be not worse than doing nothing.
Looks cool. Has anyone used it in earnest? I've always wanted to try a LaTeX successor, but the former is so prevalent that I've been concerned about it losing steam or not being compatible with journals, etc.
I think you might be underestimating uptake. Google suggests upwards of 50% usage. Also I'm fairly certain that a lot of residential infrastructure has been slowly moving to IPv6 in Australia at least. Not an overnight process, but it's happening. Over here we have a lot of newer mobile plans offering IPv6 as well.
I think a big holdback is that a lot of larger corporations will still use IPv4/NAT setups at the top level, even if all of the hardware in the network supports it. "If it's not broke don't fix it." The result is huge amounts of daily traffic coming from these institutions being IPv4 by default, with all devices in WiFi, etc, being lumped into the same group.
They're using FPGAs.
Pretty much the same setup. I don't really use playlists often though, and currently using syncthing to a NAS.
Interesting, but I'd have to say that I've been contempt just using an app that doesn't suck (musicolet). The comments about battery could hold a point to me if I were going on a week long trip, or something of the like, but anywhere that would happen for me is somewhere that I wouldn't be taking music/phone for distractions anyway.
I think the finer point I agree with is being able to just have a copy of your own music and play it without being belt-fed opinions or ads. Managing it is always a bit of a pain, but I've got a system that works for me, and MTP on android works better than trying to deal with iTunes in my books.
Looks like a bug. If you expand the Pad001 item, is there a body in there that's not visible?
Are you using a stable release version?
Carefully drill a centred hole between the two existing ones on the clock to hang it from?
Time to move to AV1!
While it might not work for everything, I have a number of sites that are used for field work that would benefit from these approaches. Things like dashboards an configuration tools.
Arguably, the tools should be desktop apps, or something of the like, but the reality is that using PWAs in this way is easier for everyone (the developer, the distributor, the user).
If you execute a parent, you end up with living or zombie children that you need to find and put down.
WordWavr #23 3/6 🔴🟢🟢 Can you beat me? 🌊 https://wordwavr.app/
It's true, that's how it's said down here! Usually by fans more so than just generally.
Not sure about mpv, but I use a gstreamer pipeline to tender cameras to the raw KMS terminal display. It works much more reliably (I.e. Predictable loading times and no stutter) compared to loading a DE first. Noting that it was on a low power RPI.