pistoriusp

The big focus will be ensuring that you're not stuck on our implementation of RSC (we wrote a custom vite plugin); so we'll be moving over to the version from the Vite team.

It's not that we think our implementation is worse, it's just that we don't want you to be locked into our framework.

We will also launch something like ActiveRecord and a Convex like experience.

So happy that we have the opportunity to give those students fundamental web development knowledge.

Love that you're here, thanks!

> With LLMs able to generate the "magic" with ease, I can see the role of frameworks shifting a bit. Instead of hiding complexity, it's surely more beneficial to expose the primitives clearly enough that both you and an LLM can follow the request lifecycle.

100%.

I kinda feel like we've fooled ourselves into creating these domain specific languages for frameworks, where we glue things together using magic, and just dealing with the features of the language, the browser and the network make a lot of sense in the AI world. And our framework is actually much less complicated than I think a lot of them are...

> I suppose there's not much of an escape hatch if you ever needed one?

I of course don't want to be vendor locked in, so I've started working on something called open durable objects, and I have a concept for something called open bindings.

these are the two core technical solutions that the framework really needs from Cloudflare. This does not include durability in the same way you get it from Cloudflare: it will run on a single machine.

This runs on both bun and node.

https://github.com/redwoodjs/sdk/pull/969

Hey everyone, Peter here. I'm one of the humans behind RedwoodSDK.

This is the second time I’ve built this framework.

The first version was a collaboration with Tom Preston-Werner. When Tom asked me to become the steward of RedwoodJS, I realized we had a massive opportunity to take what we’d started and make it bulletproof.

I brought my experience from my own startup to the table, specifically the scars , to ensure this version allowed you to iterate rapidly.

Here's the journey: https://rwsdk.com/blog/redwood-v1-getting-out-of-the-weeds

You're confusing "freedom and speech" and democracy. They're not the same. You cannot even give someone the middle finger in Germany.

> showing the middle finger (Stinkefinger) is illegal in Germany and considered a criminal offense under Section 185 of the Criminal Code (StGB). Known as an insult (Beleidigung), this gesture can lead to fines, or in severe cases, up to a year in prison.

The product isn't the software, it's your data. The VC's didn't give Dohmke $60m to build a new frontend for Git/ GitHub... They're going to capture your conversations and code with AI (The outcomes) and use that to train better models which they'll rent back at you.

Thanks, but I am not at Supabase! I ended up going back to building RedwoodJS and took over the project, and now have a consultancy.

Hey! Snaplet founder here. Want to clarify that it was not acquired by Supabase; I shutdown the startup and found roles for some of the team at Supabase.

The code remains:

- https://github.com/supabase-community/seed - https://github.com/supabase-community/copycat - https://github.com/supabase-community/snapshot

This looks like a great project, wishing them all the best on the journey.

Do you use a local/ free model?

I saw a meme that I think about fairly often: Great apes have learnt sign language, and communicated with humans, since the 1960's. In all that time they've never asked human questions. They've never tried to learn anything new! The theory is that they don't know that there are entities that know things they don't.

I like to think that AI are the great apes of the digital world.

I wrote this last week:

> We spent a decade rebuilding the browser by hijacking routing, manually syncing state, rebuilding forms and transitions in JavaScript to match native app expectations. Now the browser has caught up. It's time to stop the hacks and build on the web again, but properly.

We've been "holding the browser wrong" for the past 10 years.

So this is an outsiders perspective, and I would love to give you a first hand account. I've invited you to chat on a video-call.

redwoodjs.com has a very clear letter of intent on the homepage. Our community forum has a description. Our document has a header that describes this.

I'm not sure that you really appreciate that RedwoodJS is open source, and if you cared as much as you're pointing out to care, then you would have opened a bunch of PR requests to help us out. I'm still open to that, so please why don't you help us?

I guess it would be heplful for me to understand what you're basing it on, then I can guide you in the most appropriate direction!

Thank you! We're getting a lot of love! Just need to solve distribution. ;P

Good point, I think I should add that to the article.

Dead serious.

We should chat. We're busy building a store for source code.

RedwoodSDK is the successor to RedwoodJS. We've rebranded RedwoodJS as "Redwood GraphQL" and built this new thing from scratch. We are the same people with the same ambitions, but more focused. With a narrow niche. I believe that a framework requires a platform to be competitive today.

Because of AI, the difficulty in writing code is greatly reduced. And because of platforms, the difficulty of shipping to production is greatly reduced.

That combination can be really great for your velocity when trying to build a business.

if you've made it to 10 years, that's a really nice problem to have (or maybe a really boring problem to have). But if you're just starting out, I want to prevent you from making all those decisions when you could really be focusing on your startup instead.

So I'm trying to encourage you to consider picking a platform and just sticking with the tools of the platform rather than bundling it yourself together.

Thanks! I think you summarized exactly what I was saying, and pointing out that I had a clickbait title. My goal here is if you're starting out with something new, consider reaching for a platform rather than a bunch of services.

The reason why I really love Cloudflare is because of their bindings. A lot of the time you are simply using fetch, so request and response to interact with their services. It feels as if fetch has become like the Unix pipe of the web.

You're right, I read it a few years ago, and my knowledge is incorrect. I thought the fine was only a percentage of revenue if you're above $10M, or something along those lines.

> But as a business owner, this is a stupid reason to choose a solution. Choose solutions that will support the business and give it flexibility to change over time.

I agree with you. If you're starting out, if your business is not profitable, don't pick SaaS. Don't take the time and pay those 5 taxes. Rather just use the platform, and if you're scalable and profitable and growing, pick some other technology that supports you in the long run.

This is exactly how I'm thinking of monetizing the framework.

> locking yourself in even more, tying everything to one platform?

I'm saying that if you don't want to use a platform because it's "lock-in," but then use SaaS... then the argument doesn't hold true, especially if you consider the "taxes" of using SaaS.

Ok, that's fair. I think I might have approached this from a typical JavaScript/ TypeScript developer - where using SaaS is the norm. I'm wondering what you developing in? Not wishing to invalidate your point, just curious?

It's so rare, and apparently so unimportant, that I've never seen it as part of the marketing strategy.

Edit: I am wrong.

AFIAK GDPR only applies if you're profitable, otherwise a fine on revenue ... pre-revenue isn't applicable.

That's the dream right, how often is that true? Seems like this should be a leading indicator for picking a SaaS!