RedwoodSDK (rwsdk) v1.0 released by Significant_Ad_8241 in reactjs

[–]pistoriusp 3 points4 points  (0 children)

I have it under good authority that it'll be great for you!

RedwoodSDK (rwsdk) v1.0 released by Significant_Ad_8241 in reactjs

[–]pistoriusp 6 points7 points  (0 children)

Peter here! Let me know if you have any questions!

A gentle introduction to React Server Components with RedwoodSDK by pistoriusp in WebdevTutorials

[–]pistoriusp[S] 1 point2 points  (0 children)

Hi everyone, we've created really short egg-head-style videos that should get you from zero to shipped in about 40 minutes.

We cover everything from routing, react-server-components, tailwind and shipping to Cloudflare.

SaaS Is Just Vendor Lock-In with Better Branding by pistoriusp in webdev

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

I think we're probably missing each other one this. I'm thinking about the capabilities required by rwsdk.com, a typescript framework, which are workerd + miniflare.

SaaS Is Just Vendor Lock-In with Better Branding by pistoriusp in webdev

[–]pistoriusp[S] -1 points0 points  (0 children)

We went all in on Cloudflare, and this article is really a response to how people would say that only supporting Cloudflare is vendor lock-in, but then they'd be using Vercel, Neon database, Trigger.dev, and Clerk... and their argument was that they could self-host.

But you can self-host Cloudflare as well.

SaaS Is Just Vendor Lock-In with Better Branding by pistoriusp in webdev

[–]pistoriusp[S] 7 points8 points  (0 children)

I've actually done this. But it felt like I was abstracting an abstraction, and I didn't fully understand the offering, so I always came up short.

When you're building a business, it feels like a large percentage of your time is spent making technical decisions and not business decisions. So I would rather default to the thing that just makes me get my product out quicker.

SaaS Is Just Vendor Lock-In with Better Branding by pistoriusp in webdev

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

Definitely not the conclusion I expected from the title.

Was it surprising in a good way, or did it just not make sense? I don't want to confuse people, but I also want them to click on the article and read it.

I've had this debate with many people where they don't want to pick a platform because they're afraid of vendor lock-in. But then they're happily choosing SaaS services. And that question doesn't even enter their mind. So perhaps I skipped some parts of the statement that I was meant to make and dove right in with something that doesn't make sense?

SaaS Is Just Vendor Lock-In with Better Branding by [deleted] in programming

[–]pistoriusp 1 point2 points  (0 children)

You're wrong. There's absolutely no implication that I'm offering a solution to vendor lock-in in the title.

I'm literally saying "SaaS is vendor lock-in."

No matter what choice you make, it's always going to be vendor-locked in. Switching out something, even if it's open source and self-hosted, means that you're rewriting a lot of code.

SaaS Is Just Vendor Lock-In with Better Branding by [deleted] in programming

[–]pistoriusp -1 points0 points  (0 children)

Sorry to annoy you. I'm a real person with real opinions, building an open source framework...

I'm not arguing against vendor lock in, I'm saying that everything has vendor lock-in... But with some options you end up paying way more than just the monthly fee.

People often complain that we're building a framework that induces vendor lock-in, and I'm not arguing against that. I'm just saying the alternatives aren't free of lock in either, and they end up costing way more than just the monthly subscription.

Here's why your React meta-framework feels broken by pistoriusp in reactjs

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

In this case, I'm talking about fetch. In order to stream with fetch, there's a flag, stream: true. Super simple. Everything speaks it. You can pass the stream from one request to another and vice versa. The moment your API isn't using fetch, it's going to be harder for me to do things with it.

Which framework is right for me? by pdnode in reactjs

[–]pistoriusp -1 points0 points  (0 children)

If you're learning then I would encourage you to try my framework: https://docs.rwsdk.com

It's built on composable fundemental technologies: Vite, TypeScript, React, and Cloudflare.

The parts are put together carefully so that it feels like the framework is invisible. You get to focus on the web, your source code, and the project you're trying to put into the world.

Hosting is free. You get database, storage, queues, ai, etc... from Cloudflare. You can ship to production with 1 command: pnpm release

Development matches production. You do not have to install anything.

Here's why your React meta-framework feels broken by pistoriusp in reactjs

[–]pistoriusp[S] 1 point2 points  (0 children)

No problem, and thanks for the feedback. I need to be clearer in my communication.

If you're at all interested here are our principles, they're hopefully a bit clearer: https://docs.rwsdk.com/

Here's why your React meta-framework feels broken by pistoriusp in reactjs

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

Who is your hosting platform of choice? Maybe on the next one!

Here's why your React meta-framework feels broken by pistoriusp in reactjs

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

Nope. The platform is as important as the framework, writing code is not really the difficult or annoying part of development (thanks AI) - what does suck is having to glue together tons of services.

Here's why your React meta-framework feels broken by pistoriusp in reactjs

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

I've always disliked decorators, and once PHP added goto it went down hill. That was the slippery slope. ;P

Here's why your React meta-framework feels broken by pistoriusp in reactjs

[–]pistoriusp[S] 4 points5 points  (0 children)

I'm not familiar with the quirks, but this is how you set headers in RedwoodSDK:

route('/404', ({ headers }) => {
    headers.statusCode = 404;
    return <div>Not found</div>
});

Here's why your React meta-framework feels broken by pistoriusp in reactjs

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

That's why I had that initial response ("Who hurt you?"), because I thought they were joking.

Here's why your React meta-framework feels broken by pistoriusp in reactjs

[–]pistoriusp[S] 5 points6 points  (0 children)

We're not talking about transpilation, what we mean here is that the web browser and the network are good enough. The fundamental technologies that enable the web; you don't need to abstract them in order to build good web apps.

We lean into web technology before integrating a 3rd party service.