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?
Show HN: Jq-Like Tool for Markdown
61–70 of 79 posts
Re: Show HN: Jq-Like Tool for Markdown
#62Earlier 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.
Re: Show HN: Jq-Like Tool for Markdown
#63Re: Show HN: Jq-Like Tool for Markdown
#64Re: Show HN: Jq-Like Tool for Markdown
#65Re: Show HN: Jq-Like Tool for Markdown
#66Re: Show HN: Jq-Like Tool for Markdown
#67Re: Show HN: Jq-Like Tool for Markdown
#68Earlier 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?
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
#69Earlier 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.
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
#70Earlier 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.
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.)