If it quacks like a duck..

Because historically we do not have technology complex enough to need specific minerals. Now we do.

> Most of these needs we can fulfill with many different minerals. And the amount of all [1] minerals in earths crust is staggering compared to any foreseeable futre, so we are just going to flip to whatever is easiest/cheapest to dig.

There is another factor at play though: energy required to extract the minerals. Ones deeper in the earth's crust are likely more energy intensive to extract and perhaps even purify. At some point it won't be worth it.

And we are probably going to burn fossil fuel to obtain the energy for this?

Is mineral not a finite resource? I don't understand your source of optimism here.

Are we going realistically find enough undiscovered lithium reserves that is the same size as our known reserves as of 2022, even assuming that he is off by a factor of 4?

[0] https://www.youtube.com/watch?v=MBVmnKuBocc&t=2604s

Long video, but informative.

TLDR: We don't have enough minerals (including reserves) to completely switch our energy from ff to renewables, assuming our current energy consumption flatline, and our renewable technology efficiency and mineral consumption remain the same.

>But I don't think the "pretend it isn't" makes any sense

Well, let me expand a bit more. React's pitch is that view is a function of state, and essentially designed around the idea of an immutable state which re-renders everything when changed. It then offered some APIs to allow fine-tuning of rendering via hooks which either ties with data changes or some rendering life-cycle. To me the API screams of stubborn refusal to let go of the "view as a function of state" mantra: When you encounter a scenario where it breaks the mantra, lets add another lever to handle it. This lever also has to be pulled by you the developer, and it is up to you to know when to do it.

>I actually like React more than Svelte for many reasons, but magic compilers and templates are two big ones.

I don't really have an issue with compilers. They are the accepted magic that bridges between language for people and language for machines. The ideal language might be something that is functional and immutable language that it is easy for us to read, but compiles to the optimized, imperative updates that machine can run well.

I'd probably like React better if it had a compile layer on top of its more functional parts?

As for templates, JSX is probably the one great thing that came out of React. It is no wonder that many other frameworks are embracing JSX, but none of them are really forking the idea of hooks.

I recalling using a lot of useRef to manually tune when to re-render, and in an ideal world I shouldn't be this granular about it.

You can certainly use one of the many React map wrapper libraries to lessen the pain, the pain is still very real, just dealt with by someone else.

You guys have any blog posts detailing this transition?

Basically all the ceremonies and friction of the networking aspect and video/audio aspects are gone.

Now I think the community model of Discord isn't really in congruence with the knowledge base model a la Reddit(its hard to drop-in and out of community just to get one answer), but it is still vastly superior to its competition.

Maybe SO should just acquihire Phind. Use Phind as the gatekeep to filter out questions with well established answers before another doe-eyed user make the fatal mistake of asking a non well-formed question before they are excoriated by the poweruser #44956.

If the startup takes off? Great! If it doesn't? At least those SaaS products offered free trials.

You can learn to architecture better, but you can never get better at duck taping together the capricious and arbitrary APIs between hottest new techs.