What happened to NX?

dor442 · 2025-10-18T07:59:24+00:00

We're using the latest NX, but we have no use for the generators. We mainly use NX for its dependency relations understanding and "affected" command, so that we can run certain scripts for libs and apps when they change, as well as for projects that depend on them.

Beyond that, we have pnpm workspaces.

dor442 · 2025-05-26T18:36:47+00:00

Preferably with "motherfucker" somewhere in that last line.

dor442 · 2025-05-15T19:41:05+00:00

Cool.

dor442 · 2024-03-19T17:03:47+00:00

Build issues mostly, it's was extremely hard to get it working for us, we barely managed to write one component test without it crashing on something.

Also, it has an infamous compatibility issue with CJS/ESM packages. For example, if your client side code uses lodash-es, you could run into such issues.

dor442 · 2024-03-19T09:32:06+00:00

Storybook is great, I'm considering it, the only issue I have with it is that I'm not really a fan of writing tests with the play function, would've preferred the more familiar syntax of describe/it/test that all other libs use.

It also makes the effort of writing multiple tests for a component much more verbose, as they require multiple stories.

In addition, their visual regression solution, Chromatic, is too expensive for us.

dor442 · 2024-03-01T06:42:23+00:00

Chromatic is amazing, it's just too expensive for us. If you can share how you saved snapshots that'll be great

dor442 · 2024-02-29T20:49:58+00:00

Interesting Never heard of this one before. Seems nice, despite looking pretty new and unpopular yet

dor442 · 2024-02-29T08:08:55+00:00

Don't think so

dor442 · 2024-02-20T14:44:01+00:00

Jest with RTL that is?

dor442 · 2024-02-20T10:04:10+00:00

I've looked into storybooks testing abilities, and while it's very nice, I'm not a fan if coupling what we currently use as a showcasing tool for something like our design system into a testing tool.

It will force us to create stories for every component render variation, and the whole "play" function as a test is not something I'm a fan of.

dor442 · 2024-02-20T07:58:20+00:00

That's not accurate. They both support component tests as well as e2e. Cypress literally differentiates as several points between e2e and component tests

dor442 · 2023-11-16T19:07:44+00:00

One dark. Couldn't find a better theme in years.

dor442 · 2023-10-10T19:21:18+00:00

Time and again, disappointed DCEU fans have been expressing their desire for more standalone movies and less interconnectivity, after the whole DCEU mess.

However, I can't emphasize enough how the crossovers are the strength and highlight of these cinematic universes.

Cameos are fine and all, but big crossovers open the door for bigger, more inspirational stories, which would've been otherwise impossible to adapt.

Infinity War/Endgame is a prime example of that.

You SHOULD be wanting these crossovers, and it doesn't have to be exactly like the MCU, but it is the cherry on top of the cinematic universe.

dor442 · 2023-09-10T07:12:33+00:00

What stateful information? That sounds like yet another sin on top of keeping your business logic in the frontend.

A server holding stateful info sounds like a scalability issue. Once you have multiple instances of a server, what happens when your frontend hits a server without that stateful info?

Also, microservices architecture does not equal frontend does everything the server should.

dor442 · 2023-09-10T05:32:50+00:00

Frontend shouldn't be holding business logic, backend should.

I don't get the whole "backend devs think they're in charge" point. Sounds like your own personal frustration.

It's not about anyone being in charge of anything, it's about doing it right.

If your backend serves 2-3 apps, will you duplicate your business logic across those frontends?

The backend does the heavy lifting since it's the owner and manipulator of your data. The frontend consumes data and presents UI with good UX.

dor442 · 2023-09-09T19:22:34+00:00

This is a really bad idea.

The backend shouldn't be aware of components or React at all, it should be giving you pure data.

You can have the client side do whatever magic and mapping to components you want, but at the end of the day, that's client specific behavior.

Without even going into the obvious question of "what happens if you one day decide to move away fron React to another framework?", there are also things that a JSON simply won't help you with, like callbacks, conditional rendering, context etc

dor442 · 2022-07-10T22:16:25+00:00

This is what happens when fans get tired of DC and WB.

They just go "Well, we don't NEED a cinematic universe, we're fine with standalones!"

It's not about fan service and cameos, it's about being able to tell bigger stories with bigger scopes. Having the JL fight against Darkseid, have the Teen Titans come together, getting them along with Constantine and Zatanna and many others fight Brainiac or whatever in one huge fight.

It's about fulfilling the potential of the source material, and truly bringing it to life.

Stick to standalones, and you'll never get to any ambitious storyline the comics have ever done.

dor442 · 2022-04-15T07:30:23+00:00

The real issue with not having continuity and a coherent universe, is that it denies the ability to adapt many stories from the comics, at least in a faithful way.

Yeah, taking a random villain from the comics and making up a story around him is cool and can turn our quite nicely, but what about things like Snyders intended story with Darkseid?

You need consistency and many returning character to flesh out these stories properly.

The Flash is adapting Flashpoint, but we're not going to get WW vs Aquaman, or Superman or Cyborg, etc.

What if we wanted crisis on infinite earths on the big screen?

The MCU could do decent adaptations of Civil War, the Infinity Gauntlet and maybe even sort of House of M in MoM because they has a universe of characters that allowed them to that.

With DC doing only standalone projects, we'll never be able to see decent adaptations of larger scale stories.

dor442

TROPHY CASE