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/)JD
Posts
0
Comments
82
Joined
2 yr. ago

  • For the same reason I think software developers have the right to choose to release under copyleft, I think they have the right to release under SaaS or copyright. I don't think it is fair to take those rights from them. (I may choose to avoid SaaS or other proprietary models where possible, but I am not pure about it... I just do so recognizing that proprietary tools are a band-aid and could become unusable when any upgrade or TOS changes.)

    As one example, keep in mind that some governments may choose to punish a software developer for making "offensive" (by whatever their standards are) content, and rather than fighting a losing battle in one jurisdiction so you in some other jurisdiction can keep using that controversial software the developer may just choose to cut their losses and turn it off for everyone. If you force them to release it anyway then said punitive government may continue to hold the developer responsible for the existence of that software.

    There are rights and responsibilities associated with a proprietary model... and IMO you (and your permissive government) should not be overriding those rights for your own short-sighted benefit.

  • A) this issue applies to all kinds of software.

    B) procuring software is a two-way street ... the producer assigns terms by which access is obtained, and you agree to those terms in exchange for that access. If the software is SaaS then if the producer chooses to shut down the service then you are SOL. If the software is provided with a long list of terms via Steam, then you are basically buying SaaS with local caching and execution. Maybe don't reward producers by agreeing to one-sided deals like SaaS?

    This kind of headache is what prompted Richard Stallman to come up with the idea for the GNU license. Maybe you think that is too radical... but maybe imposing your ideas of what licensing terms should look like on (only?) game developers is radical also.

  • Perhaps re-frame the question: is it expected that you should partake of marijuana on the first date?

    Really, a date is about getting to know each other, and any assumptions about the suitability of these kinds of social lubricants may indicate a divergence or convergence of cultural norms.

    In other words, arranging a to meet at a bar sends a signal well before the "date" actually begins about how you approach life... if such a proposal is accepted then the other party is at least open to you consuming.

    There are quite likely a lot of people who will breeze right past this and proceed to get tipsy to provide a cover story for embarrassing mistakes... and every but of this is fodder for judging how well you will get along if there are further dates. Don't get depressed if the other person decides against future dates... no matter your feelings if they don't feel likewise then best to drop it early.

    The important thing to do is communicate the kind of person you are... forgiving, uptight, loose, teetotaler... and learn what kind of person the other is... preferably without conflict, and with respect. If alcohol fits with your persona, don't hide it.

  • They are a record of the process of adding to the Linux kernel. Such background can be used to trace the history of contributions if those contributions turn out to have had malicious intent or were derived from code that came from sources that were not compatible with the GNU license that the kernel is released under.

  • Agree, but this is the ELI10 explanation, not the ELI5 explanation. ChromeOS and Android are both operating systems that look and act very different than an operating system like Debian or Fedora, but all four of these examples use the Linux kernel.

  • Just a note: Windows software for controlling hardware is highly likely to assume a)direct access to the hardware (sometimes mediated thorough ancient APIs and assuming the existence of defunct expansion slots) and b) assume meatspace time can be counted using OS timing ticks (which get stretched out as modern VMs timeshare with other processes underneath the virtulized hardware). It is awfully tough to replace them sometimes.

  • Bash scripts tend to use transformation programs that accept input through standard input and use the output from standard output. For replacing one character with another, the "tr" program is typically used.

    To operate on the command-line arguments to a program like "mv", bash allows you to use back-tick quotes.

     
        
    set FNAME="path/bad:file\\name"
    mv "$FNAME" `echo "$FNAME" | tr ":\\" "_-"`
    
      

    Note the use of escaped backslashes... the pair represents a single charcter. Be sure to study the manual for each command (e.g. man tr) before using it at first.

    Te experiment building this kind of complicated command, replace the "mv" with "echo" to see what the two constucted arguments will be, and switch back to "mv" when they look right.

    One approach to looping is to turn the above into a script that fixes one filename specified as an argument to the script ($1 inside the script) and then interactively pipe all the filenames through xargs to give them one at a time to your script.

     
        
    find topdir -type f | xargs -d "\n" yourscriptname
    
      

    You must try this on sample data and also backup your current data before turning your script loose on it... so often there are little things that don't behave the way you expect when some unexpected input interacts with your script.

    Finally, there are scripting languages like Python that have a lot of these capabilities built in... and with more consistent syntax than the many-tools bash approach, but they can have the headache of a lot more specialized setup requirements than just bash to go along with those advantages.

  • Permanently Deleted

    Jump
  • Stick with Windows. Microft will deliver paradigm shifts and you will have no say in the matter. They are already removing options for disabling Copilot, and for all the promised backward compatibility they are letting go of features that lots of old Windows software depended on, as they introduce features similar to ones in Linux. I cannot really fault them for all of these changes, but the difference is actually one of choice and privacy, and not really the one you seem to think it is.

  • It is not recursive though. A directory is a special kind of inode that enumerates file inode numbers and when that list changes then the contents of that "directory inode" change. But if /home/user/.bashrc is deleted then the timestamp for /home will not be affected because the timestamps are associated with inodes rather than directory entries (assuming no symbolic links are involved).

    https://www.redhat.com/en/blog/inodes-linux-filesystem https://en.wikipedia.org/wiki/inode

  • Just to second that, the model series is Latitude, not Inspiron. and yeah, the i5 processor options I got over the years beat the i7 on processing power. The Precision models are a step up, but not any kind of low cost and seem not quite as tough.

  • As you add more compute per user interaction ("smart" features), you increase power consumption. To keep an 18hour discharge cycle, you have to have more battery. Since phone thickness is a negative marketing feature but increased screen size is a positive marketing feature, you end up with bigger phones.

    Every time they reduce compute power consumption, feature inflation overtakes the gain and more power is needed over time. Try turning on battery saver in the morning... even with "normal" use the battery will last significantly longer due to disabling background power consumption.