

Lamenting that a phone or tablet can’t use zwave for networking is really strange.
It would be, if anyone were doing that.
🅸 🅰🅼 🆃🅷🅴 🅻🅰🆆.
𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 𝖋𝖊𝖆𝖙𝖍𝖊𝖗𝖘𝖙𝖔𝖓𝖊𝖍𝖆𝖚𝖌𝖍
Lamenting that a phone or tablet can’t use zwave for networking is really strange.
It would be, if anyone were doing that.
So Thread is a low-power radio, and Matter is the protocol? Does it is the same frequency ranges - 2.4 and 5 GHz? Or does it have a different spectrum? One of the reasons I chose zwave initially was because the standard allows far more devices in the spectrum than ZigBee, and WiFi crowding is already an issue with only all of the phones, tablets, computers, and devices that I couldn’t get in zwave.
I know logind can’t easily be, because I ran Artix for a while and they were using a decoupled version of it, and there was a big discussion about swapping it for something else because it was so hard to maintain.
I also have the prompt set to the host name. I’ve never understood why people included their usernames; I don’t log in to more than one account on each machine.
It is not modular. This is a lie Poettering keeps pushing to defend building a huge edifice of interdependent systems.
Look at the effort required to factor out logind. It can’t just be used in it’s own; it has a hard dependency on systemd and needs code changes to decouple.
I will repeat that journald is really bad at what it does, and further assert that you can not run systemd without journald, or vice versa. That you can not run systemd without getting timed job control. Even if you chose not to use it, it’s in there. And you can not get time job control without the init part. In most unix systems, init and cron are utterly decoupled and can be individually swapped with other systems.
Systemd is not modular if you can’t swap parts out for other software. Systemd’s modularity is a bald-faced lie.
The one exceptions are homed and resolvd, which are relatively new and were addedlong after systemd came under fire for being monolithic. And, ironically, they’re the components most distributions don’t use by default.
How are the battery lives of your devices? I have motion sensors throughout my house connected via zwave, and I replace their button batteries about every 18 months. Does Matter run over a low energy technology?
It absolutely is. The typesetting is beautiful, and it’s far easier to work with than (LA)TeX. It also doesn’t take up 2GB of disk space.
I’ve been using systemd on most of my systems since it was released; I was an early jumper to upstart as well.
The thing I don’t like about systemd is how pervasive in the OS it is. It violates the “do one thing, do it well” Unix philosophy, and when systemd went from an init system to starting to take everything over, I started liking it less.
My issues with systemd is that it isn’t an unmitigated success, for me. journald is horrible: it’s slow and doesn’t seem to catch everything (the latter is extremely rare, but that it happens occasionally makes me nervous). There are several gotchas in running user services, such as getting in-session services working correctly (so that user services can access the user session kernel keyring).
Recently I’ve been using dinit on a system, and I’m pretty happy with it. I may switch all of my systems over to it; I’m running Arch everywhere, and while migrating Arch to Artix was scary the first time, in the end it went fairly smoothly.
Fundamentally, systemd is a monolithic OS system. It make Linux into more of a Windows or MacOS, where a bunch of different systems are consolidated under a single piece of software. While it violates the Unix philosophy, it has been successful because monolithic systems tend to be easier to use: users really only have to learn two command-line tools, vs a dozen. Is it categorically better, just because the user interface is easier for new Linux users?
dinit also has the ability to run user services, FWIW.
As long as it isn’t github.
Publish that puppy. It can’t hurt.
Don’t do it in github, though. Sourcehut is better; or if you crave that cluttered, JS-heavy feel, Gitlab.
Maybe! How is it better than keeping a README?
If it’s just a command, I put it in a readme. If it’s a series of commands, I put it in a shell script. What would your tool bring to the party, and if I’m going to turn to a third party solution, why shouldn’t I use Salt or Puppet instead?
Except that one is automatically versioned and would have saved you this pain, and the other relies on you actively remembering to reflexively commit, and then do extra work to clean up your history before sharing, and once you push, it’s harder to change history and make a clean version to share.
These days, there’s little excuse to not use COW with automated snapshots in addition to your normal, manual, VCS activities.
Harder to encrypt though, so I question “more secure.”
// Increment i
i++;
Very info. Much useful.
We started with plain text. Then everything got more complicated, and everything came with its own incrutable DB. Now we’ve come full circle: todo.txt, calendar.txt, plain text markup documents[1].
Some things don’t need to be more complex than they are.
Some people never left simple and straightforward, but it feels like the Eternal September happened, and fewer people stayed with simple, and now it’s getting popular again. ↩︎
The most popular Linux distros are binary based. Gentoo upgrades build all new software from source. If you don’t want long install times, don’t usr one of these compile-everything-from-source distros.
There’s no option to install Windows from source, and it doesn’t really come with anything more than the OS, anyway, so it’s apples yto oranges. Windows might not even be compilable on consumer hardware.
Yeah, I wasn’t saying it was bad; I meant only that Linux didn’t have to worry about device drivers for it, because the fob handles reading the fingerprint chip.
I dunno. I have a fair number of packages installed from AUR, and the Rust ones take forever to compile. CPUs may have gotten faster, but some popular languages have gotten much slower to compile.
None necessary, but thanks.