Harris had all sorts of good things planned at home. It’s baffling to me that some voters thought it was more important to lose the election.

Voters don't lose elections, campaigns do. Harris failed, and this kind of "turning around of the blame" thing that Dems try to do is one of the reasons why they don't win elections: they never learn.

you mean election, not elections, right? cause you know, 2018, 2020…

The reality is that Trump voters were (are?) dumb as rocks and tricked by simple populist messaging. There was nothing harris could've done short of succumbing to populism herself, and cloaking her campaign in dishonesty, fear, and simpleton reasoning.

Maybe she shouldve done that, but you can see why she didn't.

> There was nothing harris could've done

Then, there's no hope for America. Why bother running a candidate? Waste of money that could be spent on local elections.

The reality is, Kamala could have won that election. Quite easily as well:

1. Don't send bill Clinton to Dearborn to lecture people on how it's ok to bomb Palestine actually

2. Don't try to pivot right on immigration, instead turn hard left: argue for citizenship for all undocumented immigrants with no criminal history

3. Ignore all culture war issues, focus on affordability and nothing else. Promise to raise taxes for the rich, end subsidies for oil and gas companies, and stop sending billions to Israel and other American imperialist vassals

That was a React vulnerability, not a Next one.

It was a vulnerability that only could exist due to the incestuous relationship between React and Vercel. It was something Vercel has been trying to heavily push into React for years (which is why they hired previous react core team members).

I really hope React Native’s support for Mac and Windows apps takes off. The benefits of Electron without Chromium, plus native controls/functions.

Eh, this argument falls apart for many reasons:

- His main example of bloated client-side dependencies is moment.js, which has been deprecated for five years in favor of smaller libraries and native APIs, and whose principal functionality (the manipulation and display of the user's date/time) isn't possible on the server anyway.

- There's an underlying assumption that server-side code is inherently good, performant, and well crafted. There are footguns in every single language and framework and library ever (he works for WordPress, he should know).

- He's right to point out the pain of React memoization, but the Compiler now does this for you and better than you ever could manually

- Larger bundle sizes are unfortunate, but they're not the main cause of performance issues. That'd be images and video sizes, especially if poorly optimized, which easily and immediately dwarf bundle downloads; and slow database queries, which affect server-side code just as much as browser-side code.

> There's an underlying assumption that server-side code is inherently good, performant, and well crafted

To me it’s an assumption that server side code is going to be running on a server. Which is a known quantity and can be profiled to the nth degree. It’s extremely difficult to profile every possible device your site will run on, which is crucial with low powered mobile devices.

> Larger bundle sizes are unfortunate, but they're not the main cause of performance issues. That'd be images and video sizes

Not really, no. Large bundle sizes prevent the initialisation of the app, which means the user can’t do anything. By comparison images and videos download asynchronously and get processed on a separate thread. JS bundles also need to be parsed after being downloaded, if you pair a crappy Android phone with an 5G connection the parsing can literally take longer than the download.

> Larger bundle sizes are unfortunate, but they're not the main cause of performance issues. That'd be images and video sizes, especially if poorly optimized, which easily and immediately dwarf bundle downloads; and slow database queries, which affect server-side code just as much as browser-side code.

In network terms JS tends to be downloaded at a higher priority than both images and video so has a larger impact on content appearing

JS is also the primary main thread blocker for most apps / pages… profile any NextJS app and you’ll see what a horrendous impact NextJS has on the main thread and the visitor’s experience

> There's an underlying assumption that server-side code is inherently good, performant, and well crafted.

I didn't read it that way. I believe the underlying assumption is that the server-side code won't run in a power-constrained computer, thus having more performance headroom.

React sites are easily static.

Static or pre-rendered static? I rarely come across the latter, but the former is pretty common.

This problem was solved a long time ago with CSS Modules.

I prefer almost anything to CSS modules, so this bike shedding topic is probably very subjective.

Fortunately, short CPU bursts are most of what most people do. Race to idle!

Safari started supporting it over two years ago.

It's not that the entire crew is compromised medically, it's that logistically if one goes home they all have to.