🅸 🅰🅼 🆃🅷🅴 🅻🅰🆆.
𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 𝖋𝖊𝖆𝖙𝖍𝖊𝖗𝖘𝖙𝖔𝖓𝖊𝖍𝖆𝖚𝖌𝖍
No noteworthy DE
You mean, Gnome or KDE? KDE hasn’t announced they’re dropping X, AFAIK.
There are a great many window managers that don’t support Wayland. If herbstluftwm ran on Wayland, I’d try switching again. But it doesn’t, and the project has stated they have no intention of adding support.
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.
Hugo has a watch mode, right? It should rebuild if it detects changes.
Ah. I was wondering where the “Hugo, but Rust” was.
I love these rewrites in other languages. They often learn from, and improve on, their predecessors in a way that having to maintain backwards compatability doesn’t allow.
It’s not dead if people are still developing and using it.
No, never. I mean, sincerely I can’t remember ever owning an NVidia GPU.
For years, my main daily driver was a laptop which had an Intel GPU. When I swiched back to mostly a desktop a couple years ago, I went with AMDs – because I think they make better CPUs than Intel – and so am running Ryzen GPUs on the two desktop computers. All of the other computers in my house are headless micro-servers, ODroids, mainly.
Both the Intel i915 and the current Ryzens are rock-solid and fast under X. I haven’t had issues on Intel GPUs in years, and have never had to do any tweaking on Ryzen. Back in the early days of my XPSes (I’ve owned 3 models over the years) I used to have to muck around with the drivers, but not in the past 6 years. A couple years ago I installed Artix on the XPS and didn’t have to do anything with the drivers or X config – it just worked. Earlier this year I wiped Artix and installed EndeavourOS, and again, X worked and has been utterly solid without any tweaks.
I am aware that some people have issues with X – there’s this tearing thing I’ve read about, but I have never, in all the decades I’ve been running Linux, seen it myself. Even back when I was editing modlines and xorg.conf. In all those years I’ve seen a lot of issues with X – missing drivers, poor GL performance, difficult configuration – but never that tearing thing. I can imagine if I did, I’d be glad for a solution, and would be eager to switch.
Oh, about 4 or 6 months ago? I had problems with font scaling and multiple monitors with different resolutions, and correct DPI handling. I hear that’s all been fixed, but I haven’t tried it yet.
I have no reason to try it. X works just fine for me. I have herbstluftwm set up the way I like it, and there’s only one Wayland window manager that looks at all similar in functionality to herbstluftwm (niri?). picom gives me all of the functionlity I find useful or attractive: dimming non-focused windows and light tranparency on terminals. Switching would be a lot of work, finding a bar to work like polybar, getting the WM set up, finding a good terminal to replace rio. And why? For what? X works well and reliably, and I don’t have any edge cases like I did in Wayland, so should I make the time and effort to switch? There’s no compelling reason, at the moment. There’s nothing I want, or need, from Wayland.
I’ll probably log in to Niri to play with it one of these days when I have nothing better to do. I’m curious if it does anything herbstluftwm doesn’t.
Eventually, I may be forced to switch, but at the moment I just see a bunch of unnecessary effort on my part to just get back to what I have under X now. Seriously, what’s the compelling reason for me to use Wayland?
It is, a little. There’s no information in the text, so if there is any it’s in the embedded YouTube video, and I don’t watch talking heads when the information could be an article.
I want this to work so badly, and I thought inclusion into mainline was a positive development, but it’s just been scary.
That prioritized storage targets feature looks so nice.
My experience has been less that stellar, but it’s always improving.
I’ve accepted it’s inevitable, but at the moment nobody’s forcing me to switch and I have zero motivation to. I haven’t had any issues with X in years.
Thankfully, I’m not in Ubuntu, so I don’t have anyone shoving their decisions down my throat (software-wise).
Powertop is the shizzle. I use to use it on my laptop all the time to identify energy vampires and extend battery life during, e.g., air travel.
Don’t use it on the desktop, but it was indispensable on a laptop.
You’ve got lots of answers, so I’ll just say that shorthand character classes like \s, \w, and \d - all those backslash ones - are not widely supported, especially in the only POSIX tools. Many tools have an extended or Perl mode that makes them available, but some don’t. You can’t rely on them being everywhere. That’s why you’re getting suggestions to use explicit, long-form character classes like [0-9].
Ooo, another Artix user! We’re like hen’s teeth.
Go, because
I was using Java in my job, and had been since 1995 at that point, and did not touch it except for work. When I finally got fed up with dynamic, interpreted languages (around 2008?) I evaluated Rust, Vala, and Go, and Go won. In retrospect, I’m really glad I didn’t pick Vala, but whenever I look into Rust these days I’m also glad I didn’t pick that.
For scripting, now I stick to bash, or zsh if I’m not sharing the code. Bash scripts never fail because bash changes; the biggest risk is having to be careful with commands; tools I’ve become accustomed to, like ripgrep, aren’t guaranteed to be installed everywhere, and POSIX tools like grep have variants that differ in argument support: GNU grep is substantially different from SysV grep. If I’m distributing it and can’t write it using basic, standard bash and the standard SysV POSIX tools available in BusyBox, I write it in Go.
I did do a project in V recently and like it a lot, but it’s not mature enough to switch to, yet, and it’s so close to Go I can’t switch between the two because I start to conflate them.
I will very rarely program in C to fix a bug in some project I’m using. C is so basic, I’ll never forget it; the biggest hazard in C is other people’s idioms.
Good choice. I’ve been running Radicale for years, reverse proxied behind Caddy, and it’s been solid.
Very probable! When replying, my client only lets me see the comment I’m replying to, so losing track of who said what is a common problem for me. I assumed you were OP because I didn’t think anyone else was advocating for Plebbit.
This is the way.
I will say, Jellyfin’s aggressive transcoding has brought even my relatively modern, 12-core AMD to its knees, but for everything else, more RAM has been more important than CPU or GPU specs for self-hosting. Before Jellyfin, I hosted the entire house on an ARM-based micro.
That said, the game changes if OP wants to do any LLM stuff. Memory is still important, but the GPU starts to play a bigger role.
If I could know only one stat for making a decision, though, it’d be RAM.
Naw, there are several good use cases for blockchain. Ask a blockchain hater how to implement an auditable change log, and they’ll re-invent blockchain and claim it’s not.
I’m only saying: you specifically mentioned Bitcoin, and then later said design goals included cryptocurrency integration. I’m not opposed to crypto, conceptually - I’m just giving a possible reason why you may be garnering downvotes.
Sure; I’m saying that there are trigger words that are guaranteed to generate negative comments: blockchain, crypto, crypto currency, and Bitcoin.
You said that you can’t understand the negative feedback. I’m giving you one reason why you might be seeing it. Lemmy and Mastodon (the AP FediVerse in general) is not cryptocurrency-friendly. If you mention “Bitcoin” in the post, you’re going to get brigaded. If someone sniffs around on the repo documentation and sees the crypto link, they’ll mention it in the comments and you’ll get brigaded.
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.
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.