• 1 Post
  • 120 Comments
Joined 2 years ago
cake
Cake day: December 1st, 2023

help-circle
  • Docker’s main advantage is just being more well known and hence more supported as a default option.

    Even then, I feel that this availability of docker compose files is an illusion, due to their verbosity and limitations inherent to docker. Less granular control of permissions, clunkiness in updating images, and multi container stacks feeling like an afterthought.

    In pretty much all other ways podman feels superior. Cockpit provides a basic web gui, but quadlets are the main draw. Way easier to configure, explicitly designed for multi containers, and updating all images is a single command.

    Roughly, the different ecosystems from least to most complex are:

    Docker/Portainer -> Podman/Cockpit/Quadlets -> Kubernetes










  • Maths feels like a first class citizen in latex. The syntax is ugly, but there is some logic through the legacy jank.

    Typst makes fundamental design decisions that render it unsuitable beyond extremely simply equations. In LaTeX, curly braces are nearly always reserved for enclosing arguments, to avoid confusion with actual brackets.

    Typst uses normal brackets for both its scripting and actual maths.

    For example, \frac{n(n+1)}{2} in latex turns into (n(n + 1)) / 2 in typst. The typst code is incredibly unclear - the first set of brackets with the slash together actually form the fraction operator, so neither end up visible.

    You can see how this would start to struggle even with high school level maths, with bracketed terms and possibly fractional terms in exponents, integrals, etc.

    For example, it is very difficult for me to work out the difference between the following three in typst. That is specifically not what you want from a typesetting language.

    1/2(x + y)
    1/x(x + y)
    1/2^x(x + y)
    

    LaTeX ignores whitespace, so you can just use a formatter to space out your code and ensure the curly braces. This is not even an option in typst, which uses the space as an escape character.









  • I respect the pedantry, but I was trying say that I was using the “Anglo” - which in casual speech is short for the casual “Anglo-Saxon”, itself short for White Anglo Saxon Protestant.

    I remember I had this exact same conversation IRL, and we determined that the confusion and somewhat jargony nature of the latter two terms (especially since WASP isn’t well understood outside the US) was why people in casual speech just use the ambiguous “Anglo”.

    Semantics 🤷‍♂️



  • Poor people using spices to cover rotting food is a complete myth falsely attributed to the Middle Ages. Spices were incredibly expensive and a luxury limited to the upper class - anyone rich enough to afford spices did not have to worry about rotting food.

    The actual reason for the perceived blandness of White American food is basically the converse of this. Stereotypical white suburban food is probably closest to mid western cuisine.

    The mid west was uniquely isolated from Spanish, French, or Italian influence (which were heavier in tastes), lacked international trade to get any spices, and as the nation’s bread bowl specialised in and received lots of subsidies for growing staple crops, like corn.

    Ethnically, its white populace is overrepresented by more Anglo ethnicities, like the British, German, and Nordic, which also had more, shall we say, limited palates.

    Spices Were Used to Mask the Taste of Bad Meat in the Middle Ages? - https://culinarylore.com/food-history:spices-used-to-cover-taste-bad-meat/