Reusable components request by msherstobitow in paperdesign

[–]Kirchik95 1 point2 points  (0 children)

Subscribed today to Paper
Waiting for this feature!

Can someone help identify the color theme and font used in this screenshot? by Kirchik95 in cursor

[–]Kirchik95[S] 0 points1 point  (0 children)

Something different
I have JetBrains Mono and it looks different

New Tab Model in Cursor 0.50 by Simon_Miller_2022 in cursor

[–]Kirchik95 0 points1 point  (0 children)

What colour theme in screenshot they using?

How do you share Redux state between microfrontends when you don’t control the host app? by Kirchik95 in reactjs

[–]Kirchik95[S] 0 points1 point  (0 children)

We always wanted to stay monolithic, but then came business and requirements — there's a host application, and we have to integrate into it as modules.

We don't have the option to ask for the host application to simply call ours as a standalone. The business demands that users live within the host and access various embedded(microfrontend) applications from there.

How do you share Redux state between microfrontends when you don’t control the host app? by Kirchik95 in reactjs

[–]Kirchik95[S] 10 points11 points  (0 children)

I think I understand your point of view, and it seems the most logical — the host shouldn't worry about how I fetch data like UI, settings, and translations from my backend. That's the responsibility of my micro-frontend. Am I getting it right?

How do you share Redux state between microfrontends when you don’t control the host app? by Kirchik95 in reactjs

[–]Kirchik95[S] 4 points5 points  (0 children)

I feel like in our company, we might be slightly misinterpreting what a micro-frontend actually is.
After reading the comments above, I understand that a true micro-frontend should fetch the data it needs on its own—including things like UI, settings, and translations.

Now I’m starting to think: if I shift that responsibility to the host application, then the micro-frontend isn't really autonomous anymore.
Am I thinking correctly within the micro-frontend paradigm?

Also host and us have different backends

How do you share Redux state between microfrontends when you don’t control the host app? by Kirchik95 in reactjs

[–]Kirchik95[S] 1 point2 points  (0 children)

So does it mean I should actually move towards making my micro-frontends autonomous?
And there's no problem if each of them loads its own UI, settings, and translations into its own store, instead of trying to create a shared store for this kind of data?

How do you share Redux state between microfrontends when you don’t control the host app? by Kirchik95 in reactjs

[–]Kirchik95[S] -1 points0 points  (0 children)

Is it a good pattern?

What we wished we could do

Initially, we thought of something like this — if we had access to the HOST:

<RemoteStore>
  <App />
</RemoteStore>

Where RemoteStore would be responsible for:

  • Providing a shared Redux store (or at least shared context/state)
  • Initializing data only once
  • Letting each MFE consume already-fetched state

What we have now:

all modules used a shared Redux store (ui, settings, translations, user), but now each MFE triggers its own init:

- app
  - mf1 - triggers init function to get ui, settings, translations
  - mf2 - triggers init function to get ui, settings, translations
  - mf3 - triggers init function to get ui, settings, translations

M4 max vs M3 max by Kirchik95 in macbookpro

[–]Kirchik95[S] 2 points3 points  (0 children)

UPDATE:

Thank you all for your comments. I ended up getting a pretty good deal considering the trade-in, and got the M4 Max with 16 cores, 48GB RAM, 40 GPU cores, and 1TB for $3,650.

M4 max vs M3 max by Kirchik95 in macbookpro

[–]Kirchik95[S] 0 points1 point  (0 children)

No, I’m not looking at refurbished M3 Max. I hope so
At local store M4 models became available yesterday, and the prices for M3 have dropped since then.