• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: July 8th, 2023

help-circle
  • Es lohnt sich zu lernen, wie man die Kommandozeile nutzt. Bei Linux ist die Grundidee, diese nicht vor dem Nutzer zu verstecken, sondern bewusst als mächtiges Werkzeug zugänglich zu machen und einzubinden. Als Einsteiger kommst du zum Glück heutzutage auch ganz gut ohne klar, aber viele der inneren Feineinstellungen von Linux lassen sich am besten darüber regeln und gerade wenn du online nach Hilfe suchst wirst du oft auf Befehle stoßen, die du in ein Terminal eingeben musst. Das ist ein bisschen so, wie man in Windows früher oder später auf die Registry stößt, wenn man Dinge verändern möchte.

    Es gibt da ein tolles (und kostenloses) E-Buch von William Schott dazu, dass den Umgang anschaulich lehrt:

    http://linuxcommand.org/tlcl.php

    Damit wirst du Schritt für Schritt herangeführt und lernst auch nebenbei etwas über den Grundaufbau von Linux. Gerade am Anfang hat es mir sehr geholfen, einfache Aufgaben gleichzeitig vergleichend mit einem grafischen Programm und auf der Kommandozeile auszuführen. Also zB das Kopieren einer Datei von A nach B.

    Ich empfehle dir auch explainshell.com. Dort kannst du einen Befehl reinkopieren und sie Seite zerlegt ihn in seine Bestandteile und erklärt dir was sie jeweils bewirken.

    Anfangs auf jeden Fall ein dual boot setup beibehalten! Lieber Schritt für Schritt über viele Monate den Wechsel machen als plötzlich überfordert und frustriert zu sein und dann nicht mehr zurück zu können.


  • One reason to keep in mind is backwards compatibility and the expectancy that every Linux system has the same basic tools that work the same.

    Imagine you have a script running on your server that uses a command with or without specific arguments. If the command (say tar) changes its default parameters this could lead to a lot of nasty side effects from crashes to lost or mangled data. Besides the headache of debugging that, even if you knew about the change beforehand it’s still a lot effort to track down every piece of code that makes use of that command and rewrite it.

    That’s why programs and interfaces usually add new options over time but are mostly hesitant to remove old ones. And if they do they’ll usually warn the others beforehand that a feature will deprecate while allowing for a transitional period.

    One way to solve this conundrum is to simply introduce new commands that offer new features and a more streamlined approach that can replace the older ones in time. Yet a distribution can still ship the older ones alongside the newer ones just in case they are needed.

    Looking at pagers (programs that break up long streams of text into multiple pages that you can read one at a time) as a simple example you’ll find that more is an older pager program while the newer less offers an even better experience (“less is more”, ¿get the joke?). Both come pre-installed as core tools on many distributions. Finally an even more modern alternative is most, another pager with even better functionality, but you’ll need to install that one yourself.






  • It’s so dumb that JSON doesn’t officially have comments.

    So much this.

    Used to work at a company where I sometimes had to manually edit the configuration of devices which were written and read in JSON. Super inconvenient if you have to document all changes externally. As a “hack” I would sometimes add extra objects to store strings (the comments). But that’s super dicey as you don’t know if it somehow breaks the parsing. You’re also not guaranteed the order of objects so if the configuration gets read, edited and rewritten your comment might no longer be above/below the change you made.

    Always found it baffling that such a basic feature is missing from a spec that is supposed to cover a broad range of use cases.


  • Interesting. In German typography we used to use lower quotation marks at the beginning of a quote and lower quotation marks at the end of a quote, both in handwriting and print:

    „Amazing“

    But the lower version isn’t found on the default QWERTZ keyboard layout so in personal digital communication (instant messages, emails, etc) especially you find double upper ones a lot:

    “Amazing” or ‘Amazing’

    The formal spelling rules haven’t been updated and you may still find the lower-upper vision in professional publications where the software adjusts the quotation marks according to a global setting. But most anything that is typed directly by a user will use the lazy lower-lower version.


  • Well at least it consistently unlogical. But wait: it actually depends on the grammatical case for example:

    die Mädchen = the girls das Haus der Mädchen = the house of the girls // the girls’ house

    So depending on context male, female, neutral articles are all used (der Mädchen, die Mädchen, das Mädchen) 🤷‍♂️




  • sonnenzeit@feddit.detoMemes@lemmy.mlEnglish Language Problems
    link
    fedilink
    arrow-up
    11
    arrow-down
    1
    ·
    1 year ago

    No idea why lol.

    This always confused me, even as a native speaker so I looked it up some. Ultimately it’s because modern German is the confluence of multiple older, historic languages one of which came from a tree with a strict male/female rule for nouns while the other one’s grammar defaulted to a neutral case.

    As languages merge or adopt from others they often becomes a conjoined mess of multiple rules coexisting at the same time. A contemporary example is that in English the plural of a word is usually formed by attaching the suffix “s” to the singular form, aka house becomes houses. However there’s plenty of exceptions (mouse, mice) in particular if the words stem from a different language (octopus, octopi but nowadays octotuses is also acceptable). In that sense to people not privy to the etymology of words and who only study/learn the language per se there would be no perfectly accurate mechanism to predict the plural of a word.