flybayer

11 ms·

61.
by flybayer 5y ago
We just launched Flightcontrol[1] last month which provides the DX of Heroku (arguably better actually), but deploys all the resources to your own AWS account. Git push to deploy fargate containers + automatic CDN + easy custom domains + au
62.
by flybayer 5y ago
Yes, definitely different takes on the same problem! We could make a comprehensive list of all the differences, but the end result is that you can use all three (four if you include Next.js) to build any web app imaginable. At the end of th
63.
by flybayer 5y ago
We are working on this right now at https://Flightcontrol.dev
64.
by flybayer 5y ago
Blitz is getting tons of traction. Thousands of businesses all around the world are using it in production including Algolia and GraphCMS. Over 400 new projects are being created every day. Keep in mind, Blitz is still pre-1.0, so there&#x2
65.
by flybayer 5y ago
That's a really good point I hadn't considered. Thank you
66.
by flybayer 5y ago
Yeah we'll remove it at some point. Initially we feel it best communicates what we are building
67.
Flightcontrol – Next Generation Heroku that runs on your own cloud(flightcontrol.dev)
10 points by flybayer 5y ago|4 comments
68.
by flybayer 5y ago
npm i prisma@latest @prisma/client@latest
69.
by flybayer 5y ago
Update: Upgrading to latest prisma fixes this. I'm fixing our new app template as we speak.
70.
by flybayer 5y ago
We are still pre 1.0. Obviously lots of room for improvment still :)
71.
by flybayer 5y ago
This is because Prisma doesn’t yet work with Node 16. So not something specific to Blitz. We have speed improvements on the way.
72.
by flybayer 5y ago
Yep, nothing new. It’s abstractions all the way down :)
73.
by flybayer 5y ago
> your existing view has tons of data access logic embedded right in it. This is not at all how Blitz is set up to function. Your data access logic is clearly separated into query resolvers that run on the server. What the "Zero-API
74.
by flybayer 5y ago
The magic is very minimal and easily inspectable via the network tab of browser dev tools. We essentially just provide a transparent pipe between client and server. Whatever you return from the function on the server is exactly what comes o
75.
by flybayer 5y ago
Devs who use it are reporting it's 5-10 times more productive than alternative stacks. It's still pre 1.0, but we already have thousands of production Blitz projects from users all around the world. Many startups are choosing Blit
76.
by flybayer 5y ago
Yes. Here’s what Blitz adds: https://blitzjs.com/docs/why-blitz
77.
by flybayer 6y ago
It definitely includes eslint! Our boilerplate generation is currently optimized for folks building real production apps. We'll be adding a minimal boilerplate option here at some point (PRs welcome!)
78.
by flybayer 6y ago
No. Blitz doesn't work in places that requires "next export"
79.
by flybayer 6y ago
> because you lose stability and reliability I respectfully disagree with this. Next.js is extremely stable and reliable, so no issue there. Now without Blitz you would be cobbling together libraries on your own. What do you think will b
80.
by flybayer 6y ago
I'm genuinely curious in what ways you feel Redwood is more in the spirit of Rails than Blitz? Maybe there's some things we can improve.
81.
by flybayer 6y ago
Currently you can’t deploy them separately, but that’s something we could probably add.
82.
by flybayer 6y ago
We’re still in beta, yo! We’ll get there. :) Currently I’m using an instance of Prisma studio in production as an admin interface for the database.
83.
by flybayer 6y ago
Currently sessions are database-backed, but that can still scale a lot, especially if you use Redis. However we do plan to add JWT-based auth at some point.
84.
by flybayer 6y ago
Yes, good idea!
85.
by flybayer 6y ago
Ha, thank you! > Re: recipes You don't have to use recipes. Recipes simply package a number of manual steps into a single automated command. Recipes let you install a library without looking up the install docs. Recipes are roughly
86.
by flybayer 6y ago
It works the same as any other fullstack web app (possibility for discrepancies). We'll add a hook/API that allows you to easily detect if a new version is deployed and handle this gracefully by e.g. notifying the user. I'd a
87.
by flybayer 6y ago
There's a bit of overlap with Supabase because they are positioned as "open-source firebase". But you can just use Supabase as the DB provider for your Blitz app. In general, I'm way more in favor of owning your entire s
88.
by flybayer 6y ago
We expect only minimal breaking changes to Blitz from here on. 1.0 is expected in April. The biggest difference between Blitz and Redwood is that Redwood makes the API layer easier with conventions and APIs, whereas Blitz abstracts away the
89.
Blitz.js Now in Beta (Batteries Included Framework Built on Next.js)(blitzjs.com)
262 points by flybayer 6y ago|78 comments
90.
From Hello World to a production app in 5 days: The magic of Blitz.js(kitze.io)
12 points by flybayer 6y ago|0 comments

More ›