News for hackers. Stuff that matters.
Re:Removing jQuery from GitHub.com frontend by andrei_says_ on Wednesday July 25, 2018 @10:47PM (#17614730)
Each computer executes it a limited number of times, with lightning speed. Differences are imperceptible. The cumulative effect you are speaking of is hypothetical.

Writing code which just works on multiple browsers results in faster development and easier to maintain code and frees dev cycles to focus on performance.

Re:Removing jQuery from GitHub.com frontend by bihnkim on Wednesday July 25, 2018 @11:31PM (#17614884)
> frees dev cycles to focus on performance

Perhaps this is the case--jQuery saved them so much time that they've reached a point where they are free to optimize their frontend by removing jQuery.

Re:Removing jQuery from GitHub.com frontend by andrei_says_ on Thursday July 26, 2018 @03:22PM (#17620166)
Maybe these are not the same developers?

I know I may be replacing jquery with stimulus or eventually vuejs but writing 5 lines of jquery code for my MVP is exactly the right balance today.

Re:Removing jQuery from GitHub.com frontend by kthejoker2 on Thursday July 26, 2018 @09:38AM (#17617363)
Knuth would approve. If you don't have a product, what are you optimizing?
Re:Removing jQuery from GitHub.com frontend by Shorel on Thursday July 26, 2018 @11:54AM (#17618430)
> Differences are imperceptible.

That argument sounds very postmodern. The main issue with perception is that it easily tricked and even more, it can be strongly influenced by bias.

The cumulative effect can surely be measured and reasoned about.

It is very different to program for your new startup idea where adding features faster than your competition is more important than anything else in order to grow your user base, compared to improving an established product already being used by millions of people.

Different needs, different approaches.

Re:Removing jQuery from GitHub.com frontend by andrei_says_ on Thursday July 26, 2018 @03:28PM (#17620218)
> The main issue with perception is that it easily tricked and even more, it can be strongly influenced by bias.

I agree that this is an issue, mainly with all kinds of manipulation in politics and product quality/quantity/health impacts but the 5ms vs 2ms execution time of JavaScript is not one of the problems.

I’d focus on humanity gleefully steering itself into a climate collapse and mass ecocide while focusing on all kinds of completely irrelevant bs.