server VS rfcs

PS: Check Tolgee.io and give us github stars

To learn more visit our website [tolgee.io](https://tolgee.io)

I am not sure it it's documented somewhere, but you can also select custom fields it's automatically mapped to the interface. So it's pretty useful for complex queries with lot of joined columns. I use it a lot in Tolgee code. Check this line in one of our JPA repositories:

It's from third party maintainer, thats true, but it's downloaded directly from tolgee.io's resources. Can you please share, which ad block do you use? Thanks!

OK! And what is Tolgee?

PS: Check Tolgee.io and give us github stars

Hi there! Seems cool! Have you considered localization of the platform? We develop open-source tool for web app localization - Tolgee. Let's chat if we can help you! :)

For deploying the application to the cloud, I recommend running it in multiple containers or use database managed by your cloud provider. In Tolgee we use Kubernetes for deploying our Application container and DigitalOcean's managed PostgreSQL DB, so we don't have to worry about the database cluster.

Tolgee

Examples from the conversations of that time:

> ...we want closures to capture the values we rendered with, and to keep "seeing" those values forever. That's really important for concurrent mode where a notion of current value doesn't really exist. Hooks design models a component as being in many non-clashing states at the same time, instead of switching the "current" state (which is what classes model well). People don't really need to think about these details, but they're motivating the design a lot. [0]

> In Concurrent Mode, render may run more then one time, and since this in a class is mutable, renders that should be the same may not be. [1]

[0] - https://github.com/reactjs/rfcs/pull/68#issuecomment-4778866...

[1] - https://tkplaceholder.io/why-function-components-fit-react-b...

There are multiple names for this hook. You can find the documentation under the names useEvent or useEffectEvent.

-https://www.patterns.dev/ -https://github.com/reactjs/rfcs/blob/main/text/0188-server-components.md -https://dev.to/this-is-learning/qwik-the-post-modern-framework-3c5o -https://dev.to/this-is-learning/astro-framework-169m -https://developers.google.com/web/updates/2019/02/rendering-on-the-web -https://web.dev/vitals/

However, in React, function components can return a ReactNode. This type includes number | string | Iterable | undefined and will likely also include Promise( in the future.

I was also hoping that useEvent would eliminate some weird dependency cases, who knows when that will actually happen (https://github.com/reactjs/rfcs/pull/220).

Given a lot of unknowns on SSR and ReactEng working on RSC it feels like the wrong move to use next.js and I should just use normal react. For basic react is create react app the way to go or vite?

As mentioned before, Next.js takes a stance of treating every component as a Server Component by default. If you want to use a Client Component, you'll need to annotate the file with use client; directive at the top of the component file.

Use client is actually a React convention for what it’s worth. https://github.com/reactjs/rfcs/pull/227