jlarky2012

Hey, one of the authors of B2B SaasKit here :)

B2B Saas Kit is the main product - the goal is help you deliver a baseline app very quickly and to modify it to your needs. Prompts with Friends is just an example app - we hope featureful enough to understand the promise of the kit.

In the FAQ we talk a bit about the fact that a lot of companies are in Fogbender's position where they want people to use their product as early as possible, so in a sense any of the serverices we feature (Stripe, PropelAuth, Doppler, Vercel, Supabase, Posthog) could have created a starter like this. There's nothing special about Fogbender here, though of course we'd be happy if more folks knew of its existence.

"Instructional bundle" - it's a project (git repo) that you can clone and get running (we might create a CLI down the road). It does contain enough documentation in the README and our /setup page to get you going if you have some experience with modern frontend development. We do plan to add more documentation and tutorials later on, once we see some demand for it.

At the moment, we only use Supabase as the SQL database, but it should be pretty easy to integrate their BaaS. Our backend consists of API endpoints written in TypeScript (serverless), that use traditional REST or type-safe tRPC protocols. Because Astro is a pretty flexible platform, we have multiple examples of how to use React, one is using the SPA model that we have on https://promptswithfriends.com/survey (with the tRPC backend) and the main one - at https://promptswithfriends.com/app - is a more modern full stack app with SSR (also leveraging tRPC). We do plan to have more examples on backend architecture, we just started with this one because it has the fewest number of moving parts.

At Fogbender use Elixir on the backend, but it felt like a harder sell to people who are not familiar with it (which is most people).

I really apprecate your questions - we have some of them answered on the https://promptswithfriends.com/eject page, but it's not 100% written yet, and questions like yours help us understand what we need to do to explain things better.

I wrote this. React Experimental has added `useFormStatus` hook, which might be unintuitive if you are coming to this from something like Remix where you use something like this:

const navigation = useNavigation(); // navigation.state === "submitting"

that code works in a "global" scope, but useFormStatus only works if your component is a child of the form you want to get the status for. In practical terms, this means that you can create, say, a submit button component and use it there, but you can't easily use that state higher up, for example, if you want to add class to a pending form.

This is a pretty simple utility that will give you more control over where that state can be accessed

remix loaders are similar to trpc procedures and provide type safety, but you have to have a bit of a boilerplate there (15 extra characters) when you use it:

const data = useLoaderData<typeof loader>()

deployed version https://b2b-saaskit.vercel.app/setup source code https://github.com/fogbender/b2b-saaskit/blob/44ae552d6093a9...

it is possible! I've been playing with Astro and shoelace library downloaded from CDN for a use case like that.

Congrats guys. Astro+SolidJS is the future :)

I was going to post exactly the same. Bonus point you can make it work like that in GitLab (but not GitHub)

my thought exactly! At least add work of proof to fight with spam :)

I use LastPass because I can access it on mac/linux/windows and android. I especially like it on andorid in terms on usability, since you can set up fingerprint login

People also reported that Hillary would win. In reality so far I don't see how 15->16 is different than 14->15

Those are great points, my solution don't use Redux, Mobx and React Router and webpack if you can. React itself is great thought, but for some reason it's surrounded by over-engineered yet popular projects.

How fault-tolerant is your web server when datacenter has power outage? You can't build fault-tolerant system with one computing node by definition.

That means that if you planning to provide proper availability you want to work with system of applications, not just one. That means you should look into creating networking architecture that can handle all of that.

Most of the time it means that people just use tools that solve that for you, like load balancers. But it doesn't mean that somehow all modern applications are immune to failures.

That's actually interesting topic :) Right now we use gulp and gulp-typescript. So far, I like approach that is used in https://github.com/Microsoft/TypeScriptSamples/tree/master/e... but I'm not sure if we are going to use it any time soon. As far as gulp config, what we use is pretty much close to gulp-typescript README examples

I'm afraid it has nothing to do with Mumble, since it uses webrtc for voice calls