- Djot requires
  
    - writing nested lists
  
      - with blank lines in between
  
    - successive list items at the same level
    - can skip the blank line
  
      - but not this list item

Djot could have avoided the blank line requirement by not trying to join hard-wrapped lines back into one paragraph / list item. That would work for me because I only soft wrap my text. Djot’s choice to support hard wrapping caused all of its users (including those who hard wrap) to have worse nested list syntax.

  <<<<<<< left
  ||||||| base
  def calculate(x):
      a = x * 2
      b = a + 1
      return b
  =======
  def calculate(x):
      a = x * 2
      logger.debug(f"a={a}")
      b = a + 1
      return b
  >>>>>>> right

I also use the merge tool of JetBrains IDEs such as IntelliJ IDEA (https://www.jetbrains.com/help/idea/resolve-conflicts.html#r...) when working in those IDEs. It uses a three-pane view, not a four-pane view, but there is a menu that allows you to easily open a comparison between any two of the four versions of the file in a new window, so I find it similarly efficient.

Comments URL: https://news.ycombinator.com/item?id=47458284

Points: 4

# Comments: 0

• Which of axe-core’s rules (https://github.com/dequelabs/axe-core/blob/develop/doc/rule-...) LLMs violate most often

• Which groups of users are most affected by those rule violations (e.g. blind users or deaf users)

• Whether it’s likely that I unintentionally violate those same rules in web pages I write

Examples of rule violations and statistics on most-violated rules would make the website more convincing by showing that the detected accessibility errors reflect real problems. It would rule out that the only detected error was a single noisy false positive rule in axe-core. I bet that most readers are not familiar enough with axe-core to trust that it has no false positive rules.

Comments URL: https://news.ycombinator.com/item?id=46528502

Points: 26

# Comments: 7

A better comparison would use, for example, a React component:

  function Button({ children }) {
    return (
      
        {children}
      
    );
  }
  
  // Usage:
  Save

A better argument against Tailwind would be the added complexity of having a build system and a front-end framework or templating language, if your project doesn’t already have those for other reasons.

(adapted from my better-formatted comment at https://lobste.rs/c/oznzzj)

Also, from Jujutsu’s README (https://github.com/jj-vcs/jj#mandatory-google-disclaimer):

> I (Martin von Zweigbergk, martinvonz@google.com) started Jujutsu as a hobby project in late 2019, and it has evolved into my full-time project at Google, with several other Googlers (now) assisting development in various capacities.

Pronounced correctly, “segue” sounds just like “Segway” – not like “seg-oo”, as you might have assumed.

I see what you did in the second paragraph too. It’s another example of “a millimeter of difference in the length of a line” mattering in that it looks weird, though it’s not much harder to read.

The market correctly rewards those who bet NO in such a case. Therefore, bettors have no reason to bet YES if they really think NO.

That’s a misreading. If 30% of judges vote YES, then only 30% of the prediction’s market cap is awarded to those who bet YES, while the remaining 70% of the market cap is awarded to those who bet NO. The market correctly rewards those who bet NO in such a case. Therefore, bettors have no reason to bet YES if they really think NO.

I think those are better names for the two steps of moving files than Cut and Paste. Cut implies deleting the file immediately, which isn’t what Cut does in file browsers that support such a command.

https://en.wikipedia.org/wiki/Voronoi_diagram

https://en.wikipedia.org/wiki/Treemapping

Really? As a Lobsters reader, I occasionally review the first page of the Lobsters Moderation Log, which is public for transparency’s sake: https://lobste.rs/moderations. And I’ve never seen any log about a story’s authorship being reassigned, whether for a good reason or a bad one.

According to my reading of the source code of Lobsters (https://github.com/lobsters/lobsters/blob/96cf0b32ee81bb1bd7...), such a change would be described in the Moderation Log as “changed user from the_original_user to another_user”. I just searched all moderation logs of story changes in the last two years (39 pages of logs), and no log contains the string “changed user from”. So whether “stealing” of posts ever happened, I don’t think Lobsters users have to worry about that happening now.

Or are you also accusing the mods of hiding those specific changes from the Moderation Log somehow?