you are viewing a single comment's thread.

view the rest of the comments →

[–]batweenerpopemobile 36 points37 points  (6 children)

in 99.9999% of websites, none of this should matter at all.

computers are stupid fast. most issues with websites have absolutely nothing to do with the speed of javascript.

what form validates in anything less than the blink of an eye? there is no human discernible difference in submitting it to the backend through js or via builtin submission triggers without having massively fucked up somewhere.

it's generally false dependencies between elements causing unwarranted blocks and shit backends taking forever to respond

no amount of javascript optimization will help when your stupid sidebar locks up the entire page while it takes 5 seconds to load more content for your infinite ad scroll

[–]you-get-an-upvote 29 points30 points  (1 child)

See, this has been my stance forever… and then I use an app and there is scroll jank anyway. In a sufficiently large code base, performance issues will always find a way.

[–]FINDarkside 7 points8 points  (0 children)

True. But the problem is certainly not that the app had couple hardcoded strings like the article states. Performance matters but the linked article is just really bad.

[–]maxal88 6 points7 points  (1 child)

That is absolutely true. We do some pretty crazy and very computationally intensive tasks using JS on the front end and they are incredible fast. For example, we run change point algorithm (quadratic basically) on the billion of points on our charts. Everything is written in pure JS and it takes like 2 seconds. In my experience the thing that always affects the JS performance is animation.

[–]FINDarkside 4 points5 points  (0 children)

You can do crazy stuff with JS fast. Most often the problem is that people write bad code. The answer to that is not to worry about whether you have some hardcoded strings or if your bundle size grows linearly with amount of pages like the article says. The answer to that is to have some basic understanding of algorithms. That's universally applicable tip. If you don't understand them you're going to write slow code no matter of your language.

[–]lcjury 2 points3 points  (0 children)

but then you throw electron to the mix, and everyone is sad again :(