Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Jq-Like Tool for Markdown

github.com

Post reply on HN
Print view View original

21–30 of 79 posts

Re: Show HN: Jq-Like Tool for Markdown

#21

Post by MathMonkeyMan »

saghm wrote: post #16
unglaublich wrote: post #6

My flow is to go through the Pandoc JSON AST and then use Jq. This works for other input formats, too.

I've never had a need for parsing markdown like this, bit I have to wonder, would it make to go through HTML instead, given that it's what markdown is designed to compile to? At that point, I'd assume there's any number of existing XML tools that work work, and my (maybe naive) assumption is that typical markdown documents would be relatively flat compared to how deeply nested "native" HTML/XML often gets, so it does…

I did this for a tool that checks relative links in markdown files, e.g. readmes in a repo.

markdown -> xhtml -> sxml -> logic (racket)

Re: Show HN: Jq-Like Tool for Markdown

#22

Post by bradgessler »

verdverm wrote: post #14

> GitHub PRs are Markdown documents, and some organizations have specific templates with checklists for all reviewers to complete. Enforcing these often requires ugly regexes that are a pain to write and worse to debug This is because GitHub is not building the features we need, instead they are putting their energy towards the AI land grab. Bitbucket, by contrast, has a feature where you can block PRs using a checkb…

Not only is GitHub focused on AI, but they’re also making their UI slower and jankier by rewriting it in React.

I feel like a “Linear for GitHub” is due.

Re: Show HN: Jq-Like Tool for Markdown

#23

Post by hamandcheese »

verdverm wrote: post #14

> GitHub PRs are Markdown documents, and some organizations have specific templates with checklists for all reviewers to complete. Enforcing these often requires ugly regexes that are a pain to write and worse to debug This is because GitHub is not building the features we need, instead they are putting their energy towards the AI land grab. Bitbucket, by contrast, has a feature where you can block PRs using a checkb…

GitHub was ignoring users needs long before the AI craze.

Re: Show HN: Jq-Like Tool for Markdown

#25

Post by jvanderbot »

hamandcheese wrote: post #23
verdverm wrote: post #14

> GitHub PRs are Markdown documents, and some organizations have specific templates with checklists for all reviewers to complete. Enforcing these often requires ugly regexes that are a pain to write and worse to debug This is because GitHub is not building the features we need, instead they are putting their energy towards the AI land grab. Bitbucket, by contrast, has a feature where you can block PRs using a checkb…

GitHub was ignoring users needs long before the AI craze.

It's hard to remember, but as soon as gitlab showed up, GitHub went from a "maybe someday if I make it" site to a "let's just use GitHub for everything" site.

Prior to gitlab ratcheting up the usability, features, and cost effectiveness, I preferred hosted git for 99% of use cases.

Re: Show HN: Jq-Like Tool for Markdown

#26

Post by nicce »

bradgessler wrote: post #22
verdverm wrote: post #14

> GitHub PRs are Markdown documents, and some organizations have specific templates with checklists for all reviewers to complete. Enforcing these often requires ugly regexes that are a pain to write and worse to debug This is because GitHub is not building the features we need, instead they are putting their energy towards the AI land grab. Bitbucket, by contrast, has a feature where you can block PRs using a checkb…

Not only is GitHub focused on AI, but they’re also making their UI slower and jankier by rewriting it in React. I feel like a “Linear for GitHub” is due.

Is it true that it is React’s fault? Is there any other replacement for heavy user interaction, that is clearly more performative? You cannot do that on server side.

Re: Show HN: Jq-Like Tool for Markdown

#27

Post by tomcam »

nicce wrote: post #26
bradgessler wrote: post #22

Earlier quoted context omitted.

Not only is GitHub focused on AI, but they’re also making their UI slower and jankier by rewriting it in React. I feel like a “Linear for GitHub” is due.

Is it true that it is React’s fault? Is there any other replacement for heavy user interaction, that is clearly more performative? You cannot do that on server side.

> Is there any other replacement for heavy user interaction, that is clearly more performative?

Well-written React?

Re: Show HN: Jq-Like Tool for Markdown

#28

Post by AcquiescentWolf »

nicce wrote: post #26
bradgessler wrote: post #22

Earlier quoted context omitted.

Not only is GitHub focused on AI, but they’re also making their UI slower and jankier by rewriting it in React. I feel like a “Linear for GitHub” is due.

Is it true that it is React’s fault? Is there any other replacement for heavy user interaction, that is clearly more performative? You cannot do that on server side.

Vue, Svelte, Solid.

Re: Show HN: Jq-Like Tool for Markdown

#29

Post by whateveracct »

bradgessler wrote: post #22
verdverm wrote: post #14

> GitHub PRs are Markdown documents, and some organizations have specific templates with checklists for all reviewers to complete. Enforcing these often requires ugly regexes that are a pain to write and worse to debug This is because GitHub is not building the features we need, instead they are putting their energy towards the AI land grab. Bitbucket, by contrast, has a feature where you can block PRs using a checkb…

Not only is GitHub focused on AI, but they’re also making their UI slower and jankier by rewriting it in React. I feel like a “Linear for GitHub” is due.

Linear? That website makes my laptop heat up like nuts.

Re: Show HN: Jq-Like Tool for Markdown

#30

Post by simonw »

nicce wrote: post #26
bradgessler wrote: post #22

Earlier quoted context omitted.

Not only is GitHub focused on AI, but they’re also making their UI slower and jankier by rewriting it in React. I feel like a “Linear for GitHub” is due.

Is it true that it is React’s fault? Is there any other replacement for heavy user interaction, that is clearly more performative? You cannot do that on server side.

GitHub worked great for 15+ years without React everywhere. I'm finding interacting with issues to be a whole lot jankier over the past few months.
Post reply on HN