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

71–79 of 79 posts

Re: Show HN: Jq-Like Tool for Markdown

#71

Post by arminiusreturns »

cmddds wrote: post #47
jvanderbot wrote: post #25

Earlier quoted context omitted.

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.

I just started using git, can you give me some advice?

Use it everyday, preferable with a porcelain such as magit in emacs.

Alias commands help.

Run your own git server instead of using one of the big names.

Use git hooks. (https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks)

When starting out, looking at visuals of how git works can help a lot I've found when training others. (https://www.junosnotes.com/wp-content/uploads/2021/07/basic-...)

Re: Show HN: Jq-Like Tool for Markdown

#72

Post by arminiusreturns »

infogulch wrote: post #67

I've always wanted a "literate programming" / jupyter-style notebook based on markdown. Maybe this could help make something like that possible.

Emacs org-mode and babel are what I use instead. Very powerful alternative to Jupyter imho, but of course not for everyone.

I have used commit hooks so that non-emacs users could push updates that still get executed to avoid the emacs tie in though, the biggest issue with it I've found.

Re: Show HN: Jq-Like Tool for Markdown

#73

Post by frankfrank13 »

I worked on a project converting word docs to markdown so they could more easily be ingested into an LLM, one issue was that context windows used to be very short, so we would basically split on `\n#` to get sections, but this turns into a whole thing where you have to make guesses about which header level is appropriate to split at, and then you turn each section into a separate chunk in FAISS. Anyways we ended up using HTML instead of MD but theres so much tooling for traversing HTML and not MD. This would have been helpful for that

Re: Show HN: Jq-Like Tool for Markdown

#74

Post by bastardoperator »

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…

Or maybe GitHub built these features over 10 years ago and millions upon millions of people use them daily without issue. You can literally have any semblance of what you're describing with a PR check, and that feature is also pretty old. The API is right there, you just have to use it.

Re: Show HN: Jq-Like Tool for Markdown

#75

Post by sunaookami »

zelphirkalt wrote: post #69
nicce wrote: post #26

Earlier quoted context omitted.

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.

Whatever is at fault, their code viewer now sucks. I often cannot even use basic text functionality like double click + drag to highlight/select whole words. It has become broken software at some point. For the code search one annoyance that they introduced was, that one needs to be logged in to search a project. Another annoyance is how the search works. Why, oh why, do soooo many programs/websites/software things h…

Just selecting text in the code viewer is so broken it drives me nuts everytime. Thankfully you can just press "." to open VS Code Web with the current file open.

Re: Show HN: Jq-Like Tool for Markdown

#76

Post by simonw »

troupo wrote: post #48
simonw wrote: post #30

Earlier quoted context omitted.

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.

IIRC only search is React. Everything else is still Hotwire or Hotwire-like, with numerous bugs

GitHub Issues is React now - I think as of a month or so ago. Try running the React Developer Toolbar on those pages to see.

Re: Show HN: Jq-Like Tool for Markdown

#78

Post by lanstin »

zahlman wrote: post #9
lanstin wrote: post #2

Ironically one of the reasons markdown (and other text based file formats) were popular because you could use regular find/grep to analyze it, and version control to manage it.

I don't think anyone ever really expected to see widespread use of regexes to alter the structure of a Markdown document. Honestly, while something like "look for numbers and surround them with double-asterisks to put them in boldface" is feasible enough (and might even work!), I can't imagine that a lot of people would do that sort of thing very often (or want to) anyway. If a document is supposed to have structure…

I think that prospect (of programmatically structurally editing markdown files) would have made everyone burst out in laughter in 2000; if you want to programmatically alter stuff, put it into sexp's or some other syntax. SGML. Apparently human readable but really a tricky format leads to this sort of thing: https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-fr...

Re: Show HN: Jq-Like Tool for Markdown

#79

Post by jkmcf »

tomcam wrote: post #27
nicce wrote: post #26

Earlier quoted context omitted.

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?

How many well-written code bases have you seen?

React is a PITA to learn, and even the easiest frameworks encounter devs who jump right in and commit shot code to deliver "value" right away, only for that code to live on forever haunting the devs left with mess after the founder coders move on.

Post reply on HN