mojombo

21 ms·

1.
by mojombo 3mo ago
I created and named the Grit library that used to power GitHub. Scott Chacon (fellow GitHub cofounder, now CEO of GitButler) specifically asked my permission to re-use Grit as the name of this project, which I gladly granted. R is for Ruby.
2.
Managing Multiple Claude Code Sessions Without Git Worktrees(blog.gitbutler.com)
8 points by mojombo 1y ago|1 comments
3.
by mojombo 1y ago
With Claude Code's new lifecycle hooks, GitButler auto-sorts simultaneous AI coding into separate branches. Write three features, get three clean branches.
4.
by mojombo 2y ago
Oh, and we have a video version of the walkthrough in case that's more your style! https://youtu.be/5IZv3khsx0o
5.
by mojombo 2y ago
Hey, Tom Preston-Werner, co-creator of RedwoodJS here. We've been working hard on React Server Components support in RedwoodJS and really happy to finally have a bare-bones working implementation ready! Redwood is a framework for quick
6.
React Server Components Now in RedwoodJS(redwoodjs.com)
36 points by mojombo 2y ago|10 comments
7.
Major Version Numbers Are Not Sacred(tom.preston-werner.com)
51 points by mojombo 4y ago|13 comments
8.
by mojombo 4y ago
Thanks, Will! It's awesome having you in the Redwood startup community, and blown away by the work you're doing at Everfund!
9.
by mojombo 4y ago
Thanks, Orta! I'm especially keen to get money in the hands of under-represented developers that would otherwise not have a chance to spend time on getting a startup off the ground. Hopefully we can be first money in at a time that tru
10.
by mojombo 4y ago
Tom Preston-Werner here, I'm behind the Redwood Startup Fund as an extension of my work on RedwoodJS. I also do a lot of angel investing, and this fund finally combines my great loves of Redwood and investing! I'm happy to answer
11.
The Redwood Startup Fund(tom.preston-werner.com)
17 points by mojombo 4y ago|10 comments
12.
by mojombo 4y ago
Explanation and link added!
13.
by mojombo 4y ago
Right now there is no business model, on purpose. This is why I'm personally supporting it. I think what David meant is that we are sustainable because I am committed to sustaining the project. Our goal is to find a properly sustainabl
14.
by mojombo 4y ago
Did you look at the main website? https://redwoodjs.com It is indeed a web app framework, based on React, GraphQL, Prisma, Storybook, Jest, and with many integrations for auth, logging, etc.
15.
by mojombo 4y ago
It is unusual, perhaps, but as Redwood has evolved, it's been natural for us to really offer support for startups using our tools. Redwood is a more complex, more integrated, and more aligned with long term maintainability than most of
16.
by mojombo 4y ago
These were state of the art tools when we started work on Redwood more than two years ago. We're investigating other more modern alternatives, but swapping them out is a finicky and time consuming project and we've been focused on
17.
by mojombo 4y ago
RedwoodJS has been about long term maintainability from the very beginning. This is part of why we chose GraphQL as a core component. It's more complex at first, but in the long run it gives you multi-client capabilities without rewrit
18.
by mojombo 4y 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
19.
by mojombo 4y ago
Thanks! Our mission is to help more startups explore more territory, more quickly. We're hoping to achieve this by integrating all the bits you need up front so you have less work to do on your framework, and can spend your precious ti
20.
by mojombo 4y ago
You are correct, if you're not careful with your data fetching you can get into a waterfall situation. This is something we're keen to address in coming versions. Because we can get in the middle of your data fetching flow if you
21.
by mojombo 4y ago
The golden path is to use GraphQL, but you are free to do data fetching to other data sources in the normal way you would in a React app.
22.
RedwoodJS 1.0 and $1M Funding(tom.preston-werner.com)
7 points by mojombo 4y ago|0 comments
23.
by mojombo 4y ago
Glad you appreciate it! My number one goal for launch week and the new homepage and this event reminder site is to drive the "tutorials taken" number. For me, that is success.
24.
by mojombo 4y ago
Yes, the new website we launched today is built with Redwood (except docs are done with Docusaurus). We're still doing some optimizations, but you are indeed looking at a Redwood app!
25.
by mojombo 4y ago
Core team member here. Several reasons: 1. Redwood tightly integrates more of what you'll need as your app evolves: Storybook, Jest, Auth, Deploy, Logging, and a lot more. 2. A first class GraphQL experience so you can start from day o
26.
by mojombo 5y ago
Fun to see this on HN! I originally created Gollum to power GitHub's wiki system and wanted to see if we could use Git to make our wikis more powerful AND more open. I thought it would be cool if you could just clone your GitHub wiki a
27.
by mojombo 6y ago
I think this is true for any specific moment, but as we are creatures of the 4th dimension, we must also care about how we change our code over time. When code complexity is managed, users can enjoy better versions of a piece of software mo
28.
by mojombo 6y ago
TOML is my true legacy. =)
29.
by mojombo 6y ago
Author here. Fun to see this come up on HN again, every so often. Readme Driven Development still serves me well (that’s how we drove RedwoodJS early on) and we even expanded that into Tutorial Driven Development, where we wrote the Redwood
30.
by mojombo 7y ago
Your understanding is accurate. We do plan to support pre-rendering on a route-by-route basis, which will perhaps be more inline with what JAMstack tends to mean today. But Redwood is still all about JavaScript (client) and APIs (backend),

More ›