4 ms·

As far as I know Redwood has no server-side rendering solution. You can do both client-side rendering and static generation (although not as sophisticated as Ne

As far as I know Redwood has no server-side rendering solution. You can do both client-side rendering and static generation (although not as sophisticated as Next.js'), but not server-side rendering. Next.js also has a pretty small API surface and is generally quite unopinionated when it comes to your apps structure, while Redwood chooses more of the stack for you and what tools you should use (Storybook, Jest, Prisma, GraphQL). I would also like to point out that while there are a lot of people rooting for Redwood's success and they seem to have some active core contributors, there is actual financial backing for Next.js and they have large enterprise users. There are some startups that use Redwood listed on the 1.0 update website, but at least I do not know any of them.

mojombo 5y ago
> As far as I know Redwood has no server-side rendering solution. SSR is priority number one for v2. In the meantime, a number of users use Next.js as a client that talks GraphQL to the Redwood backend. It works very well! > there is actual financial backing for Next.js Today I announced I will be providing $1M of funding for future RedwoodJS framework development this year, so now we have funding too. =) https://tom.preston-werner.com/2022/04/04/redwood-v1-and-funding.html https://tom.preston-werner.com/2022/04/04/redwood-v1-and-fun... The truth is, we can both succeed at the same time, there are so many great app ideas waiting to be explored, and different tools will work better for different situations!
- xrd 5y ago
  I'm the author of Svekyll (https://svekyll.com https://svekyll.com) a static blog tool which models the simplicity of Jekyll. Svekyll uses SvelteKit under the hood, but rendering to a static site feels like it is a second class experience in SvelteKit (they are more focused on rendering to cloudflare or netlify or vercel serverless platforms). I would love to experiment with using RedwoodJS as the backend if SSR is a priority; how do I get more information on that work?
  - dac09 5y ago
    Hi! Core team member here, right now we have our hands a little full with the launch week, but will be moving onto v2 very soon! Best way to get more info is to create a post on the forums, or an issue! The discord contributing channel is a great place too. All the links on the main website https://redwoodjs.com https://redwoodjs.com Speak to you over there!
- replygirl 5y ago
  what happens when you get bored of it?
thedavidprice 5y ago
> there is actual financial backing for Next.js and they have large enterprise users We haven't communicate this very well until today. Redwood is funded and will continue to be funded. Just not in a typical "for-profit" business model. See: https://tom.preston-werner.com/2022/04/04/redwood-v1-and-funding.html https://tom.preston-werner.com/2022/04/04/redwood-v1-and-fun... > while Redwood chooses more of the stack for you and what tools you should use (Storybook, Jest, Prisma, GraphQL) Very true! Just know that the overall integration is modular and extensible. - byo DB Client - want to use REST, go for it! - power Next via the multi-client API, lots of startups doing that already > There are some startups that use Redwood listed on the 1.0 update website, but at least I do not know any of them That makes sense because most of them are less than 1 year old. And the funding amount listed was raised in the previous 6 months.
sdesol 5y ago
> they seem to have some active core contributors Looking at merged pull requests, the project is quite healthy as the following shows: https://oss.gitsense.com/insights/github?q=merged%3Atrue%2Bpull-age%3A%3C%3D120&t=crc-insights&tb=closed&v=redwoodjs%2Fredwood%3A%3Agithub%3Aredwoodjs%2Fredwood%3A%3A%3A%3A https://oss.gitsense.com/insights/github?q=merged%3Atrue%2Bp... Next.js is on a whole new level though https://oss.gitsense.com/insights/github?q=merged%3Atrue%2Bpull-age%3A%3C%3D120&t=crc-insights&tb=closed&v=vercel%2Fnext.js%3A%3Agithub%3Avercel%2Fnext.js%3A%3A%3A%3A https://oss.gitsense.com/insights/github?q=merged%3Atrue%2Bp... The number that I'm really interested in, are last commits more than 28 days ago. With this number, you can guesstimate how popular Next.js is with non core contributors and in the case of Next.js, it really is staggering.
- pistoriusp 5y ago
  I'm new to this tool, but can you break down how to correlate the 28 days ago commits with non-core contributors and concluding that it's staggering?
  - sdesol 5y ago
    The basic idea is, if somebody last committed more than 28 days ago, it is likely that they are not a "core contributor" since you would expect "core contributors" to commit more frequently than every 28 days. Hope that makes sense. For Next.js, the percentage of people that last committed more than 28 days ago accounts for 80% of all unique contributors, which is what makes their project quite staggering from a "popularity" standpoint. Assuming everybody that last committed more than 28 days ago are not "core contributors" (which may not be accurate of course) we can see that Next.js had 169 contributors that basically decided to create a pull request that was good enough to be merged. For Redwood they had 23, which is respectable but not on the same level as Next.js Based on my analysis of very popular open source projects, most projects typically only have 50% of their contributors in the +28 days range, while Next.js has 80%. Looking at last commits more than 28 days ago is a very good indicator of community health/interest.
    - 5y ago

mojombo 5y ago

> As far as I know Redwood has no server-side rendering solution. SSR is priority number one for v2. In the meantime, a number of users use Next.js as a client that talks GraphQL to the Redwood backend. It works very well! > there is actual financial backing for Next.js Today I announced I will be providing $1M of funding for future RedwoodJS framework development this year, so now we have funding too. =) https://tom.preston-werner.com/2022/04/04/redwood-v1-and-funding.html https://tom.preston-werner.com/2022/04/04/redwood-v1-and-fun... The truth is, we can both succeed at the same time, there are so many great app ideas waiting to be explored, and different tools will work better for different situations!

xrd 5y ago
I'm the author of Svekyll (https://svekyll.com https://svekyll.com) a static blog tool which models the simplicity of Jekyll. Svekyll uses SvelteKit under the hood, but rendering to a static site feels like it is a second class experience in SvelteKit (they are more focused on rendering to cloudflare or netlify or vercel serverless platforms). I would love to experiment with using RedwoodJS as the backend if SSR is a priority; how do I get more information on that work?
- dac09 5y ago
  Hi! Core team member here, right now we have our hands a little full with the launch week, but will be moving onto v2 very soon! Best way to get more info is to create a post on the forums, or an issue! The discord contributing channel is a great place too. All the links on the main website https://redwoodjs.com https://redwoodjs.com Speak to you over there!
replygirl 5y ago
what happens when you get bored of it?

thedavidprice 5y ago

> there is actual financial backing for Next.js and they have large enterprise users We haven't communicate this very well until today. Redwood is funded and will continue to be funded. Just not in a typical "for-profit" business model. See: https://tom.preston-werner.com/2022/04/04/redwood-v1-and-funding.html https://tom.preston-werner.com/2022/04/04/redwood-v1-and-fun... > while Redwood chooses more of the stack for you and what tools you should use (Storybook, Jest, Prisma, GraphQL) Very true! Just know that the overall integration is modular and extensible. - byo DB Client - want to use REST, go for it! - power Next via the multi-client API, lots of startups doing that already > There are some startups that use Redwood listed on the 1.0 update website, but at least I do not know any of them That makes sense because most of them are less than 1 year old. And the funding amount listed was raised in the previous 6 months.

sdesol 5y ago

> they seem to have some active core contributors Looking at merged pull requests, the project is quite healthy as the following shows: https://oss.gitsense.com/insights/github?q=merged%3Atrue%2Bpull-age%3A%3C%3D120&t=crc-insights&tb=closed&v=redwoodjs%2Fredwood%3A%3Agithub%3Aredwoodjs%2Fredwood%3A%3A%3A%3A https://oss.gitsense.com/insights/github?q=merged%3Atrue%2Bp... Next.js is on a whole new level though https://oss.gitsense.com/insights/github?q=merged%3Atrue%2Bpull-age%3A%3C%3D120&t=crc-insights&tb=closed&v=vercel%2Fnext.js%3A%3Agithub%3Avercel%2Fnext.js%3A%3A%3A%3A https://oss.gitsense.com/insights/github?q=merged%3Atrue%2Bp... The number that I'm really interested in, are last commits more than 28 days ago. With this number, you can guesstimate how popular Next.js is with non core contributors and in the case of Next.js, it really is staggering.

pistoriusp 5y ago
I'm new to this tool, but can you break down how to correlate the 28 days ago commits with non-core contributors and concluding that it's staggering?
- sdesol 5y ago
  The basic idea is, if somebody last committed more than 28 days ago, it is likely that they are not a "core contributor" since you would expect "core contributors" to commit more frequently than every 28 days. Hope that makes sense. For Next.js, the percentage of people that last committed more than 28 days ago accounts for 80% of all unique contributors, which is what makes their project quite staggering from a "popularity" standpoint. Assuming everybody that last committed more than 28 days ago are not "core contributors" (which may not be accurate of course) we can see that Next.js had 169 contributors that basically decided to create a pull request that was good enough to be merged. For Redwood they had 23, which is respectable but not on the same level as Next.js Based on my analysis of very popular open source projects, most projects typically only have 50% of their contributors in the +28 days range, while Next.js has 80%. Looking at last commits more than 28 days ago is a very good indicator of community health/interest.
  - 5y ago