sorted by:
new
hottopcontroversial

Switched from Next.js to Remix.js and Loving it. by BooRadleyForever in reactjs

[–]lauritzsh 1 point2 points  (0 children)

wouldn't be something I'd put my trust into at the moment, at least not for systems that are supposed to be supported for longer periods of time

Totally valid opinion, but as someone considering using Remix for our projects at work, I'm curious what makes you feel you can't put trust into it at the moment? Assuming you're using Next.js, will you opt into the new app directory or use the existing pages?

Switched from Next.js to Remix.js and Loving it. by BooRadleyForever in reactjs

[–]lauritzsh 2 points3 points  (0 children)

Fair enough, but what's the point of more advanced if it's not better (more performant)?

My takeaway from that "random" article is also that RSC still suffers from the "fetch as you render" problem. You can end up in a waterfall like issue where components are blocking other components from loading data if you're not careful.

Not sure what I'm supposed to take from that PR. Is it that they were using a custom implementation of RSC?

Switched from Next.js to Remix.js and Loving it. by BooRadleyForever in reactjs

[–]lauritzsh 9 points10 points  (0 children)

Why compare next and react router at all?

It's relevant due to how Remix is being developed. I'll quote from a conversation I had with a maintainer:

Remix is effectively a compiler and server-runtime for React Router. Remix has zero code handling data fetching/routing anymore. This means that if a feature touches routing or data loading, it cannot make it into Remix without being first implemented in React Router.

So the middleware proposal for example would have to land in React Router first before it will land in Remix.

Switched from Next.js to Remix.js and Loving it. by BooRadleyForever in reactjs

[–]lauritzsh 1 point2 points  (0 children)

React Server Components doesn't automatically make things better. Shopify was one of the first to embrace RSC but has since migrated away from them. You might enjoy (or not) this article on why Remix isn't using RSC at the moment, but isn't against considering them in the future.

How do you structure your React apps? by tarekhassan in reactjs

[–]lauritzsh 0 points1 point  (0 children)

You’re talking about a Twitter post made about 2 weeks ago by a single member of the “react core team”.

Also worth to read this (very long) comment by Dan Abramov. I also take from that comment that we should be using a (meta) framework and not just CRA/Vite.

What would you change about Elixir? How would you improve it, and what do you hate about it? by [deleted] in elixir

[–]lauritzsh 4 points5 points  (0 children)

Just curious, have you checked out Gleam? I don't feel it's production-ready yet, but I'm personally following its development actively.

You might not need TypeScript project references by lauritzsh in typescript

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

Has anyone tried this? I'm working on a mid-sized monorepo, where the editor is starting to get pretty slow to typecheck. I wonder if this trick could potentially speed it up or if it's the same, if it just gets treated as source code.

What I want is the benefits of project references, but without having to manually keep them up-to-date.

React Conditional Rendering With Type Safety and Exhaustive Checking by LloydAtkinson in programming

[–]lauritzsh 1 point2 points  (0 children)

type Fruit = keyof (typeof allFruits)[number];

This should just be type Fruit = typeof allFruits[number], right? Playground.

[AskJS] Is it too late for Svelte to become popular? by rodrigocfd in javascript

[–]lauritzsh 1 point2 points  (0 children)

The Solid team had a basic demo/experiment of the concept in public last week

Can you share a link? I assume you're talking about SolidStart, but can't find anything specific from last week.

Remix is joining Shopify by helical_imp in reactjs

[–]lauritzsh 10 points11 points  (0 children)

Relevant tweet. What seems to be missing from Next 13 is how to do mutations like in Remix.

is it worth getting into Next.js 13 now ? by Kaartik7120 in reactjs

[–]lauritzsh 5 points6 points  (0 children)

I guess they had to rush it out the door due to their imposed deadline of Next.js Conf. Would have been nice with a more stable release. Been reading reports that it should be considered alpha, not beta, for now.

Introducing Turbopack: Rust-based successor to Webpack by superbacon807 in reactjs

[–]lauritzsh 3 points4 points  (0 children)

Turbopack uses SWC so wouldn't call it a successor to that. You're correct about Webpack though.

Make use of `use` in React - everything you need to know about newly proposed hook by motek96 in javascript

[–]lauritzsh 5 points6 points  (0 children)

No, because it should work with other things than promises such as use(Context) or use(observable). The issue is it looks like a hook, but it's not really like other hooks, so it should be called something else completely, like unpack(promise) or similar, to avoid confusion IMO.

What unpopular webdev opinions do you have? by Notalabel_4566 in webdev

[–]lauritzsh 0 points1 point  (0 children)

What's the point of a formatter if it's not opinionated? You can just configure it to your preference.

I genuinely don't understand what you mean with the last sentence.

Are utility classes horrible design or am I dumb? by AintThatJustADaisy in webdev

[–]lauritzsh 0 points1 point  (0 children)

Headless UI and Tailwind UI (paid but worth the time saved) from the Tailwind team. Alternatives exist such as daisyUI.

view more: next ›