Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)L
Posts
18
Comments
18
Joined
11 mo. ago

  • How will we stave off ecosystem takeover if not by taking its early signs seriously? At the start of every case of "Stallman Was Right" was a lot of presumption that, in the eyes of many, did not make a solid conclusion.

  • They really want people to stop talking about the Epstein files, huh?

  • As the saying goes, don't throw the baby out with the bathwater. I think @floofloof@lemmy.ca summed things up pretty well here.

    Also, from my reply to that comment:

    As for the off-putting statements about ‘Rust people’: Since the article was published on March 19, I wonder if much of it, revolving around what the author saw as indications of authoritarianism, came from heavy disquiet in the face of authoritarianism’s recent gaining hold of the White house. I’d even consider it likely that people who post on Techrights have an above-average sensitivity for this kind of thing. It could be that the author has since arrived at a more differentiated and just view. Of note, since the time of his writing, the Rust project did remedy things that he criticized about their website.

  • Agree on everything. (As for the off-putting statements about 'Rust people': Since the article was published on March 19, I wonder if much of it, revolving around what the author saw as indications of authoritarianism, came from heavy disquiet in the face of authoritarianism's recent gaining hold of the White house. I'd even consider it likely that people who post on Techrights have an above-average sensitivity for this kind of thing. It could be that the author has since arrived at a more differentiated and just view. Of note, since the time of his writing, the Rust project did remedy things that he criticized about their website.)

    1. Your criticism omits the passages about usage of the MIT license over the GPL (the ones I quoted in the post). I haven't quoted the other parts of the article because they are not as substantial, but their being opinionated and questionable in what they say about 'Rust people' does not mitigate the recklessness of those who strive to create MIT-licensed replacements for GNU coreutils.

    2. Discord on the website of the Rust project: That's not a lie at all: it was the truth at the time of publication on March 19, and even as late as May (having been there for at least four years). So it appears that the Rust project has decided to drop Discord as an officially advertised channel. Good move. I would think that vocal criticism like the author's played a role in this.

    3. Rust forum telling users to use Firefox, Chrome or Safari, and refusing to be accessible by other browsers (however circumventible this may have been): How was this not a sign of flagrant disregard for free software and for people's right to use the web however the fuck they want to use it - or how they need to use it, in case of disabilities? (This antifeature doesn't seem to be in place anymore, but compare point 2.)

  • Linux @lemmy.world

    The dangerous push by Canonical to rewrite GNU coreutils as Rust code without the GNU license

    techrights.org /n/2025/03/19/Is_Ubuntu_Compromised_Push_Away_From_GNU_and_GPL_Led_by_Army_Of.shtml
  • Linux @lemmy.ml

    The dangerous push by Canonical to rewrite GNU coreutils as Rust code without the GNU license

    techrights.org /n/2025/03/19/Sami_Tikkanen_Explains_on_Rust_Language_and_Its_Goals.shtml
  • Ubuntu Linux @lemmy.ml

    The dangerous push by Canonical to rewrite GNU coreutils as Rust code without the GNU license

    techrights.org /n/2025/03/19/Is_Ubuntu_Compromised_Push_Away_From_GNU_and_GPL_Led_by_Army_Of.shtml
  • Opensource @programming.dev

    The dangerous push by Canonical to rewrite GNU coreutils as Rust code without the GNU license

    techrights.org /n/2025/03/19/Is_Ubuntu_Compromised_Push_Away_From_GNU_and_GPL_Led_by_Army_Of.shtml
  • It isn't a question of "How long are they supposed to support it for"; it's a matter of "Don't artificially break things".

    As to Linux distro EOLs, they're are bad examples for several reasons:

      1. Linux distros are being provided to us for free – Never look a gift horse in the mouth.
      1. Linux distro EOLs are generally a very different beast than a Windows EOL: They change your user experience and may break some beloved software, but they generally don't make core hardware components unusable, let alone entire computers.
      1. When the Linux kernel does discontinue support for some very old hardware, we still have the source code of the last version available and are free to build some continuation. When your Windows updates end, you're left with nothing. And that's not just a theoretical option (which, however, is important enough in itself!): Only in the case of 35-year old hardware is it unlikely that people would actually do that work (on the kernel and all the relevant higher-level software). If – by contrast – the Linux kernel team would for no good reason stop supporting hardware that's a mere 10 years old, you betcha there would be people starting work to fill in the void (starting with current kernel devs who don't agree with that decision). Why? Because that's what Linux community is doing right now and has been doing for decades – keeping up support for hardware way older than 10 years.
      1. Linux developers are credible when they say that a decision to drop support for some old thing is because continuation would be to much work. Sure, also for Windows 10, economic unfeasability of further maintenance might have been the reason why they discontinued it. However, over the course of years and decades, Microsoft has given us countless well-documented reasons to suspect that their decision here is not because they have, to their own displeasure, concluded that the burden of continued support has become too heavy, but because they've spotted some new way to make money and/or reinforce their market dominance in various segments, to which people's ability to stick with their current systems is an impediment. Since people not having a TPM2 on their computers is extremely unlikely to require much additional effort on Microsoft's side to keep them supported, this is all the more likely to be the case, and that's what the plaintiff's claim is.
  • You can encourage your target audience to back up their important data upfront in order to save them a couple of hours at the beginning of your party. But also try to bring plenty of external drives as others here have suggested already.

  • "The only requirement is that you share your progress and log your hours." So participants are free to choose how they log their hours?

  • Python @programming.dev

    Book recommendation if you've been using Python for a while: Effective Python by Brett Slatkin

  • Shell Scripting @programming.dev

    The Shell Scripting Tutorial: Parsing long command-line arguments with getopt

    www.shellscript.sh /examples/getopt/
  • Perfect, thanks for the explanation. Indeed, I found the same solution via StackOverflow about simultaneously.

  • Shell Scripting @programming.dev

    (Solved) Ways to run the join command on memory/variable contents instead of files?

  • Ah that's good to know about zsh.

    Sorry regarding the second code block; it does indeed work as intended, and quite elegantly.

  • For the first code snippet to run correctly, $list would need to be put in double quotes: echo "$list" | ... , because otherwise echo will conflate the various lines into a single line.

    The for loop approach is indeed quite readable. To make it solve the original task (which here means that it should also assign a number just smaller than $threshold to $tail, if $threshold is not itself contained in $list), one will have to do something in the spirit of what @Ephera@lemmy.ml and I describe in these comments.

  • Thank you, in fact I ended up doing something that's mathematically pretty much just that: I have the previous line stored in an auxiliary variable lastline, and it is the evaluation of the current line $0 that determines whether the previous line gets printed.

     
        
    awk -v threshold=150 'BEGIN {lastline=""}
      (lastline!="" && threshold<$0){print lastline} #the additional check lastline!="" prevents an empty line at the very beginning
      {lastline=$0}
      END{print} #hardcode printing of the very last line, because otherwise it would never be printed
    ' 
    
      

    Of note, in the case where some list entries are repeated, the behavior of this script will be:

    • The threshold value, if it's in the list, will always be printed just once, even if it occurs multiple times in the list, and also if it happens to be the first, last, or only entry in the list.
    • All larger entries will be printed exactly as often as they occur in the list. This even holds for the largest value: its last repetition will be printed via the final END{print} statement, whereas all preceding instances get printed through the statement that depends on threshold<$0.

    (IIRC, it was a StackOverflow post that led me to this.)

  • Shell Scripting @programming.dev

    Say you have a list of increasing numbers and a threshold. How do you get the highest number smaller-or-equal to the threshold and all numbers that are larger?

  • Thanks, that's good to know, I'll see how well I can adapt my workflow to this. (The reason for using Konsole tabs so far is the easy switching via Alt+[number], but I suppose using Helix's integrated multi-document system should offer other advantages (e.g. regarding registers) that could outweigh this by far.)

  • Helix Editor @programming.dev

    How to make current filename show up as the window/console title? (Konsole being my terminal emulator)

  • Very specifically for learning about GNU/Linux and Unix, I highly recommend the book Classic Shell Scripting by Arnold Robbins and Nelson Beebe (O'Reilly Media, 2005).

    ISBN: 9780596005955

    I recently wrote the following about it in a post:

    This book is extremely readable and gives a very good introduction to the various standard Unix shell commands (grep, sed, awk, tr, sort, to name but a few) and how to tie them together to do useful things. It’s very suitable if you have some experience with the command line at the level of individual commands but now want to see how to do construct more interesting pipelines and scripts. It includes an introduction to regular expressions. The fact that the book is already 20 years certainly means that some explanations and approaches are outdated, but since shell programming is at the core about text processing, almost all contents of the book are still highly relevant today.

  • Libre Hardware @lemmy.ml

    The long, long road to a Free Printer

  • Programming Books @programming.dev

    Classic Shell Scripting (O'Reilly Media, 2005). Great for leveling up one's skills with the Unix shell

  • OSHW - Open Source Hardware @scribe.disroot.org

    Researchers launch open-source robotic exoskeleton to help people walk

    techxplore.com /news/2025-06-source-robotic-exoskeleton-people.html
  • Open Source Hardware @lemmy.ml

    Researchers launch open-source robotic exoskeleton to help people walk

    techxplore.com /news/2025-06-source-robotic-exoskeleton-people.html
  • Libre Hardware @lemmy.ml

    Researchers launch open-source robotic exoskeleton to help people walk

    techxplore.com /news/2025-06-source-robotic-exoskeleton-people.html
  • Web Development @programming.dev

    Things I would like every young web engineer to learn (Toot by Alex Russell)

    toot.cafe /@slightlyoff/114734591135486998
  • New to this instance, but for me too it is comparatively sluggish since I started using it yesterday.

  • Or get a used thin client (e. g. HP T620, T630, T640 or Dell Wyse 5070). Cost: ~40-100$. Biggest advantage: Passive cooling, i. e. they're absolutely quiet.

  • Hardware @programming.dev

    Reviving the Spirit of Open Science Hardware: Highlights from the 2025 Open Hardware Summit

    gerritniezen.com /reviving-the-spirit-of-open-science-hardware-highlights-from-the-2025-open
  • OSHW - Open Source Hardware @scribe.disroot.org

    Reviving the Spirit of Open Science Hardware: Highlights from the 2025 Open Hardware Summit

    gerritniezen.com /reviving-the-spirit-of-open-science-hardware-highlights-from-the-2025-open
  • Libre Hardware @lemmy.ml

    Reviving the Spirit of Open Science Hardware: Highlights from the 2025 Open Hardware Summit

    gerritniezen.com /reviving-the-spirit-of-open-science-hardware-highlights-from-the-2025-open