• 37 Posts
  • 262 Comments
Joined 3 months ago
cake
Cake day: April 2nd, 2025

help-circle

  • The signal to noise ratio on Stack Overflow has been low for a long time now, even before LLMs showed up. I was once a high-rep contributor there. Nowadays, I usually won’t even bother clicking web search results that lead there, let alone share my knowledge with them. (And with Cloudflare, which is now a man-in-the-middle between the site and its users.)

    IMHO, the community could use a distributed Q&A network, with no instance able to interfere with anyone’s access to our accumulated knowledge.



  • I would be interested in a project like this if it were a distributed network.

    It’s important to ensure that accumulated community knowledge will survive, and conversations can continue, when an instance dies or becomes intolerable. (Reddit and Stack Exchange have recently brought this into sharp focus.) It’s so important that I no longer contribute to sites like this unless they provide those assurances.

    So I hope this one develops into something that meets that need.


  • Inability to learn from your mistakes is nothing to be proud of. Delete this

    Someone misinterpreting what I wrote because they only paid attention to part of it does not make it a mistake.

    When they follow up by trying to re-frame the topic that I started into a different one, and then criticize me for not having addressed their pet topic, and furthermore tell me I should have used different words so that they can avoid admitting their misunderstanding… well, that’s just willful aggression.

    Much like your comment to me is aggressive, and rude. You are now blocked.


  • You also said “feel” not “look”.

    I did, in order to express that I was thinking of overall sense conveyed by the visuals, rather than whether differences in frame rate could be noticed under scrutiny. Words often have multiple meanings depending on context.

    [Edit: I also said “choppy”, referring to the slide-show-like visual effect that most of us have seen at very low frame rates. I also described animation mechanics that are obviously about the appearance of motion. So there was no reason to assume that I was talking about the inter-frame input lag on which you are so fixated.]

    you should clarify it in your own comment.

    I could, but I won’t. I already clarified for you twice. I’m not interested in further indulging your combative insistence on misinterpretating what I wrote, and nobody else seems to have had trouble understanding me. Bye bye.


  • Yes but frame rate is primarily about responsiveness, not aesthetics,

    In games that tie physics and inputs to frame rate, 25-30 fps is about a 30-40 millisecond response in the worst case; usually less. That’s plenty fast enough in most games I’ve played. And not all games do that anyway. So I can’t say I agree with your statement as a general rule.

    What game do you play where that’s not fast enough?

    In any case, it’s irrelevant to my point. The comment you responded to is explicitly about the frame rates feeling choppy. Meaning visual effect.







  • I wonder if a personalized reputation system based on your votes of other people’s comments, and influenced by votes from folks who have earned enough upvotes from you, could be developed without turning your feed into an echo chamber like Facebook.

    Sort of like PageRank, but for fediverse users instead of web pages, and with each user keeping (and seeing) their own rankings of everyone else.






  • Geany is excellent. It’s a lightweight programmer’s editor with enough features and configurable hooks to provide the important parts of a full-blown IDE. It renders text clearly, never feels laggy, and doesn’t get greedy with your RAM. I recommend it to people who can’t stand the bloat that’s often seen elsewhere these days, but would rather have a GUI than resort to vim.

    A couple minor annoyances to me:

    • It doesn’t yet support the Language Server Protocol, so any language that it doesn’t understand will be left without syntax and context-sensitive features. (On the other hand, it does support a lot of languages.)
    • It inherits Scintilla’s use of Gtk for its GUI, so it’s an alien app on Qt-based desktops.

    I use it anyway, because I find it easier / more comfortable to use than Kate.


  • I suspect zram’s swap device only consumes RAM when it actually contains swapped pages, but I don’t know for sure. Can anyone link an authoritative statement on this?

    I use it on a 32 GiB workstation, also with PERCENT=50 and ALGO=zstd in Debian’s /etc/default/zramswap, and vm.swappiness=60. This is its only swap device. I like that it avoids needless SSD wear and painfully slow interactivity during large compile and compression jobs.

    Is it worth it on your system, which has only 2 CPU cores? If your memory-intensive workloads compress well, then I would think yes, for the same reasons that I like it. If you find your CPU struggling with it, you could always change to a lighter compression algorithm.

    On the other hand, if your memory-intensive tasks don’t compress well, then no, I would not expect it to be a good use of your CPU.

    You’ll never know until you try it. I suggest checking the output of zramctl when running tasks that create memory pressure.



  • Sorry; I shouldn’t have written Cloudflare specifically. Their CAPTCHA page now contains scripts from Google, not Cloudflare. I have corrected my comment.

    How do you know this?

    Because a couple months ago, archive.is/archive.today started showing me CAPTCHA pages instead of the archived articles when I use Firefox with scripts disabled. The current page contains scripts hosted by Google, which I won’t enable, so I can’t read the archived articles.

    What about https://ghostarchive.org/?

    I haven’t used that site enough to have a consistent picture of what it’s doing. When I tried it a few minutes ago, it directed me to a CAPTCHA wall when trying to submit an article, but not when searching for an archived article. I’ll try to remember to look at it again periodically, to be able to answer this question in the future.