undefinedzero

The US-EU data exchange agreements turn out to not be GDPR compliant time and time again.

At the last few grams, a small reduction gets very expensive. Helinox are super light, great for hiking and motorcycles. If you’re in a car, you can take a lot more with you.

The page will render perfectly fine before it is hydrated when using getStaticProps. To verify , simply run LightHouse in Chrome on a page with cache busting on and look at the screenshot timeline. It will render in a fraction of a second, long before React gets loaded.

The initial request size is not a great way to compare frontend frameworks. Next goes into a lot of effort to optimize navigation around your site, and gives you full usage of React in your frontend so you can show amazing things like charts, forms etc.

If the JS files are set to load asynchronously, the initial load should be almost equally as fast, and React should load in the background. Afterwards, additional navigation should be near instant.

This is what client side apps do (e.g. React). They come with their own set of challenges which when not solved correctly turn into downsides. Probably still easier for Wikipedia to do than fixing their backend.

A flame trench would probably be a lot more inconvenient to them. Right now they can freely move around most of the launch pad. This is probably important for their rapid iteration, which is what is going to get them to orbit as quickly as they can. If a big chunk of the launch pad is consumed by a trench, that area becomes inaccessible by their platforms, cranes, etc.

I, a React developer for ~8 years, don’t really remember what useEffect does without the second param. I never needed it, so I forgot. I almost feel it should be a required prop, and I doubt that that knowledge alone would fail or pass an interview.

> Instead, these prompts function more like instructions to a commissioned artist—they identify what the prompter wishes to have depicted, but the machine determines how those instructions are implemented in its output.

If you commission an artist, the produced result becomes yours and you own copyright on it. How different is it with AI?

The AI did not creatively decide to do something. An order was placed, it fulfilled it, and ownership was transferred.

Rendering performance can definitely add up, but rarely do React websites render so many elements that you get to 700ms. Once you do, you can nearly always fix that with an performance optimizations iteration. I reckon that issue is just as likely in all frameworks, and less likely to be about React using 0.2ms (or something like that) longer per element to render before optimizations.

AngularJS and Angular are really the same product. Angular 1 turned into Angular 2 turned into Angular 15. That’s far from different frameworks, even if in between versions you’re essentially learning a new framework.

With SSG and to a lesser extend SSR, React has close to zero impact on the initial page load. It’s all just HTML.

React/competitor performance that people use to compare frameworks is about rendering performance. E.g. React takes 100ms longer to rerender 10,000 elements (random numbers for the example). In these situations the actual real world difference will be negligible.

Site performance is much more API based, and that’s the same regardless of frontend. React has more library solutions to optimize the UX though, as it’s the most mature and popular.

Semantic versioning isn’t really usable for typed languages as the majority of fixes would be considered breaking changes.