Formerly /u/Zagorath on the alien site.

  • 818 Posts
  • 6.25K Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle

  • Connections
    Puzzle #721
    🟦🟦🟦🟦
    🟪🟪🟪🟪
    🟩🟩🟩🟩
    🟨🟨🟨🟨

    Skill 98/99
    Uniqueness 1 in 1,513

    Really fun one today.

    Spoilers

    I spent ages on the pentathlon one. Noticed swim, fence, and shoot pretty quickly, but my brain saw “ride” and couldn’t think of anything other than cycling, which isn’t in the MP. So I thought for a bit that it could be “multi-sport event”. Until eventually it clicked…horse riding.

    No idea how ice fits into the blue category, but I figured out the other 3.


  • Ah interesting.

    Unfortunately yeah there’s a lot of inconsistency with how different Lemmy clients display markdown. Even on the first-party platforms, ^multiple words of superscript^ or ~multiple words of subscript~ works some (Jerboa) but not others (lemmy-ui web interface).

    The problem with this specifically though is with neither the Connections site nor with any of the Lemmy clients…it’s with the interplay between Connections and the basic markdown specification. The markdown spec very specifically allows you to break one paragraph down into multiple lines, so that you can write like I am right now, and keep individual lines small while having it all display as a single paragraph. If your client is showing this as separate lines, it is misapplying the markdown spec.

    If you want a new line in markdown, you can add a blank line in between (like I did just before this sentence), to create a whole new paragraph.
    Or you can end your line with two spaces (like I did the line before this)
    or with a backslash, to escape the newline and tell the markdown parser “treat this newline as an actual newline”. Both the double space and the backslash methods insert a “line break”.

    Here’s how this comment should display (apart from the superscript and subscript parts):

    And how its script looks:














  • I never actually put any serious effort into using MuseScore myself before the changes, so I can’t comment from extensive personal experience.

    But as a musician, I did use scores written by someone in MuseScore, as well as ones written in Sibelius. And I could always tell when it was MuseScore. I’m sure it was possible to write good looking scores in MuseScore 2, but it clearly did not make it easy. The scores were obviously inferior in terms of layout and design compared to those produced in Sibelius. Basic things like spaces between notes not being the right proportion, or dynamic markings appearing as plain italic text instead of the usual bold dynamics would be wrong in MuseScore far more often than in Sibelius.

    As a general rule, a good UX should:

    1. Make it very, very easy to do (or discover how to do) the most common basic things, and should result in them being done in the way a user expects
    2. Not slow down a power user from accomplishing basic tasks at speed
    3. Allow easy discovery of and access to less common tasks

    A lot of designed-by-software-engineer FOSS applications do a good job of 2 and an ok job of 3, but fail at 1.


  • Interesting. That would make his survey of rather limited value, in my opinion, because just by doing notes (including rests), durations (just from semiquaver to semibreve, including tie and dot), and accidentals, you get 18, right off the bat. Considering the ranges offered in the poll he made were 1–5, 5–10, 10–20, and 20+ (never mind the overlap if you happened to use exactly 5 or 10…), that makes it very hard for anyone who types their note input instead of hunting around slowly with the mouse to get into anything other than the top bucket. Especially since he quite explicitly said “including typical ones (like Ctrl+S, Ctrl+Z, etc.)”

























OSZAR »