Live data from Hacker News

Show HN: Jq-Like Tool for Markdown

github.com

61–70 of 79 posts

Re: Show HN: Jq-Like Tool for Markdown

#61
post #27
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?

[deleted]

Re: Show HN: Jq-Like Tool for Markdown

#62
post #7

Earlier quoted context omitted.

Curious, which license can't you use at work for a simple shell tool? Considering you're not linking against it, even GPL3 should be okay, right?

Most big employers consider GPL unusable and will only allow Apache, MIT, BSD, and other permissive patent-free licenses.

Yeah, caution with GPL is understandable if you're shipping it or making it a part of a hosted service. But internal use is not the intention of GPL, so a blanket ban like that would put that shop at a disadvantage, like the other comment said, that basically rules out all kinds of things.

Re: Show HN: Jq-Like Tool for Markdown

#63

Earlier quoted context omitted.

Holy crap, is that why it's felt so syrupy recently? What was wrong with the old implementation?!

It wasn't React. Everyone knows modern applications must be written in React.

We are in Hell. Ugh.

Re: Show HN: Jq-Like Tool for Markdown

#65
congrats on your tool, will check it out. I have a side question on markdown: cursor messes up markdown generation quite often for me. I think its responses are always in markdown with sections for code and asking it to generate markdown breaks it. So the question: any ideas on how to have cursor generate markdown?

Re: Show HN: Jq-Like Tool for Markdown

#68
post #27
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?

After reading a bunch of stuff as result of this, I think you are the most correct. Difference in performance on different frameworks seems to be more like philosophical rather than practical.

It is enough that your website has just a couple of images, comparison of the "shipping size" of the runtime bundling becomes rather meaningless. It is the same for initial latency for showing the rendered content.

These frameworks were designed for heavy sites, and their "base speed" becomes irrelevant. If you understand how do they work and use them correctly, there shouldn't be that much difference. Assuming, that we use JavaScript on client-side in the end.

Re: Show HN: Jq-Like Tool for Markdown

#69
post #26

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.

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 have issues searching for a simple 100% substring match? There should always be an option in a search for most software, to search for exact substring without involving any magic. Then the checkbox to optionally ignore case. Only when this basic search functionality is ensured, should they care about developing anything else.

Re: Show HN: Jq-Like Tool for Markdown

#70

Earlier quoted context omitted.

Holy crap, is that why it's felt so syrupy recently? What was wrong with the old implementation?!

It wasn't React. Everyone knows modern applications must be written in React.

As a greybeard sysadmin, this is why I write pure html5/css3 with as little js as possible, and where it can't be avoided, vanilla with no frameworks.

I really have grown to hate most frameworks... (and I don't hate em, but for the devs who push them... it's become the new Java, another bane of linux admins everywhere.)

Post reply on HN