No, I didn't. I don't use Pis, I have ODroids. Heck, they may sell batteries for ODroids, too.
For me, it wouldn't have made much difference because I have UPSes around the house serving things like routers, modems, and switches. And I do care about size and energy use. I'm only saying there are advantages to using laptops.
You can get little integrated LCD cases for Pis too, can't you? And maybe even a little fold-out keyboard. Congratulations! You've re-invented the laptop!
Thanks! That's all great information.
I'd bet there are a bunch of college students involved in the implementation, too. I don't see ongoing maintenance taking much more manpower than MS; we certainly had dedicated teams for it at my last company, so maybe that will be a budgetary wash, and what they save will be the probably significant licensing.
Thanks. I wonder why both jitsi and Matrix. Someone in the thread said it was too bad Matrix's video conferencing wasn't good enough that they had to add an extra software component, but I wonder what, exactly, the evaluation found wrong with it.
I have a lot of issues with Matrix, but the video conferencing didn't seem worse than the horrible key management.
Every day?
rio -e 'tmux attach -t#'). Because terminals crash, because it survives session restarts, because it lets me log in remotely and continue what I started in my desktop, and because it works over ssh and having a consistent multiplexer environment across machines is nice. I used sceen for years before discovering tmux, and have tried almost every other terminal multiplexer; and none add any significant value for me over tmux.I'm currently using Rio as my terminal. It has bugs, but it's actively developed and regularly releases will fix one more thing. It has both ligature and sixel support, and it's wildly fast and far, far less memory intensive than either kitty or ghostty, which are both pretty fat. I am not including it in "the list" because some remaining bugs are pretty big, like randomly crashing when it gets resized or sees some sequence of asci escape codes. It's not much of an issue because I run everything in tmux, and it crashes less with every release, but I hesitate to recommend it until it's more stable.
This is, in my mind, one of the benefits of laptops over micro computers: integrated UPS. Even an old, degraded battery will probably get you a couple of hours with the screen off.
IME, power consumption is going to be worse overall, for any laptop likely to be in the recycle bin, it's probably double the consumption of an ARM SBC. The integrated UPS and usually decent power conditioning of the power supply saves you more money with a laptop. Plus, keyboard and screen for emergencies - I just generally expect that, over there life of a micro I'm going to have to drag out and plug in a spare keyboard, mouse, and monitor because something in a device, or an upgrade, or BIOS flash, is preventing a boot.
There are a lot of good reasons to use laptops instead of SBCs, if you don't mind the extra power draw and (as she says) don't have size requirements.
This article is terrible.
In less than three months' time, almost no civil servant, police officer or judge in Schleswig-Holstein will be using any of Microsoft's ubiquitous programs at work.
Instead, the northern state will turn to [an unnamed, gaping information hole] open-source software to "take back control" over data storage and ensure "digital sovereignty", its digitalisation minister, Dirk Schroedter, told AFP.
"We're done with Teams!" he said, referring to Microsoft's messaging and collaboration tool and speaking on a video call -- via an [unnamed, gaping information hole] open-source German program, of course.
What will they use instead? Who the fuck knows! The article omits this crucial piece of information.
And don't say it's TBD; they're not going to say they're "done with Teams" without knowing what they're switching to. Or, even if they haven't put the final nail in the decision, they have a short list.
Mint eschews all of the Snap crap, though, doesn't it?
Jesus, please tell me it does. I've been recommending it to beginners. I thought it was sanitized.
Void is rolling release IIRC
That's what I thought, but the main website says Void focuses on stability over being cutting edge, which would imply some sort of release cycle. Or, maybe they just update packages less frequently.
I still hold Debian in higher regard since it's slightly easier for a novice to get used to
It's hard to beat Mint as a novice distro, for sure.
Did you look at Pelican?
I have not, but I will. I may also look at Zola, although it, too, appears at the surface level to be tightly coupled with markdown.
the template language is buggy and inscrutable
It's just Go templates, which are pretty solid; I'd be surprised by any bugs, unless they're in the Hugo short codes. The syntax is challenging, even if you're a Go developer and use it all the time. It's a bespoke DSL, and a pretty awful one: it's verbose, obtuse, and makes some common things hard.
Go is my language of choice, but my faith gets shaky whenever I have to use templates.
I'm not a huge fan of Python; despite its popularity, it's got a lot of problems, not least of which is the whole Python 2/3 fiasco; which, years later, is still plaguing us. However, if I can containerized it so it isn't constantly breaking in the background when I do a system update, I'm not opposed to using a project written in it. At least it isn't Node; I won't let that crap onto any server I admin.
Edit: Zola has the same problem as Hugo.
Ah, Ok.
I do as (or a similar workflow): I rsync the content directory and let Hugo on the server render. My sites are public, but perhaps they're just much smaller or not as popular; Hugo renders even my largest site in about a second, but for a large, slow, heavy-use production situation I could see a push-and-swap process for a more atomic site update.
I don't see the degradation you do, but there are so many possible variables.
My biggest gripe about Hugo is how limited it is in supporting source document formats. There's no mechanism for hooking in different formats, and the team is reluctant to merge PRs for other formats. When I started with Hugo, I had a large repository of essays spanning a decade and written in a variety of markup, from asciidoc (which I used for years), to reST, to markdown; and markdown is by far the worst. I was faced with converting everything to markdown, which was usually a lossy process because markdown is so limited, or not publishing all of that history. And now we have djot, which is almost the perfect plain text markup language, but I again have to first do a lossy conversion to markdown to get Hugo to consume it. It low-key sucks, and I'm actively looking for an alternative that has a more flexible AST-based model for which new formats can be added; something that consumes a format like pandoc's AST.
(I'm replying to you twice b/c totally different topics)
Tell me more about your Void experience. I've been meaning to give it a shot, except I don't get as much enjoyment out of fussing with distros as I used to. What are the pain points? Under Artix, I used dinit which I really liked, but I tried s6 first and absolutely hated it. I didn't try runit; how is it?
What I'm most interested in is xbps, because IMO it's the package manager that makes or breaks a system. I'm quite fond of pacman and have encountered far fewer dependency hell situations than I did with either rpm or deb, and rolling release is a must. xbps looks kind of like a rolling stable release?
That's a really good point. I have forgotten whether there are anonymous accounts in Matrix for rooms, but even if so it wouldn't be the same as scheduling a meeting and sending a specific meeting link a-la Zoom.
Yeah, this is the reason.