flybayer

Update: Upgrading to latest prisma fixes this. I'm fixing our new app template as we speak.

We are still pre 1.0. Obviously lots of room for improvment still :)

This is because Prisma doesn’t yet work with Node 16. So not something specific to Blitz.

We have speed improvements on the way.

Yep, nothing new. It’s abstractions all the way down :)

> 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" does is in practice is handle all the HTTP stuff for you. So as a developer all you are thinking about is "function calls". The function call happens to occur over the network, but as the dev you don't have to think about the details of how that happens.

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 out on the client. We don't interfere with that. All we do is handle all the HTTP stuff for you.

Some have expressed the same concern, but after using it they’ve had zero issues.

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 Blitz because of the fast product iteration speed it enables.

We even are seeing adoption in the enterprise. Algolia now has two internal Blitz apps. They first tried to use AWS Amplify for these projects but switched to Blitz and haven't looked back. And there's a big US university going to production with Blitz shortly.

Here’s a thread of things folks are saying after using Blitz: https://twitter.com/flybayer/status/1361334647859384320

Yes. Here’s what Blitz adds: https://blitzjs.com/docs/why-blitz

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!)

No. Blitz doesn't work in places that requires "next export"

> 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 be more stable and reliable, your own homegrown thing or Blitz which has a sizable and growing community that's always making it better?

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.

Currently you can’t deploy them separately, but that’s something we could probably add.

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.

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.

Yes, good idea!

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 "install dependencies + codemods". So for example the `chakra-ui` recipe installs the needed dependencies and adds the theme provider to your app root.

There's currently zero coupling with recipes. The end result is exactly the same as if you did everything manually.

> Re: API-only

Currently you can do that. You can use the API routes (which give you direct access to Node req, res objects. And don't add any pages (or just a few, as you want).

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 also like to go even further and add some type of detection to the build that would notify you of potential issues.

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 stack, like Ruby on Rails and Laravel vs relying on a third-party service for the core of your app.

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 entire thing into a compile step. So working with Redwood requires working with APIs like normal. But with Blitz you can almost forget an API is even there.

Great alternative if you don't care about Next.js and you absolutely want to use GraphQL.

I'm super excited about Prisma 2! I feel like we finally have a database client that (1) is/will be very powerful and (2) is very approachable and easy for beginners to learn.

It certainly doesn't replace the need to know some SQL, but it does delay that which is great for so many people.

I'm definitely using this instead of any ORM for every project I can.

I really love having the fully typed interface for Typescript. Both for static type checking and for code completion in your editor.

We are using Prisma 2 as the default database client for Blitz.js [1] which results in a super nice stack. Especially because the Prisma DB types flow all the way into your React components.

[1] https://blitzjs.com

This is literally the first listed feature :)

Yes, let’s talk! Assuming you dropped your email on my website, just reply to the automated signup email and we can take it from there.

There are 3 types of bookmarks:

1) Read-later

Something interesting you want to read. Items in this category should be automatically removed after a certain period of time, so it doesn't get out of hand. New RSS feed items would also fit into this category.

2) Save-for-later

Something you're sure will be useful down the road. This should be retrieved first and foremost using a powerful full-text search engine. Minimal tagging can also be very helpful. Lastly, it's critical these items are archived by the bookmark manager so you always have the content even if the website shuts down.

3) Todo

Something you need to take action on. For example, buy this product, try this new open-source library, install an app, etc. These should have optional reminders to alert you at a certain day or time.

Currently my system is a terrible mess: I email myself for read-later and todo but put save-for-later in Pocket. This is very frustrating because there's tons of bookmark manager options but none support all 3 types, most have terrible search, are slow, and don't have full-text search or archival.

So last year I started building what's going to be the Superhuman of Bookmark Managers:

https://AcornBookmarks.com

It will be 100% open-source and available as a hosted service.

I'm focusing on the fundamentals: speed, performance, robustness. I'm using PouchDB, so all your data is 100% offline which makes it very, very fast. Of course, it'll support all 3 bookmark types, have full-text search and archival. It'll run on all browsers and platforms, including mobile apps built in react-native. It's UI is going to be fun, geeky, and beautiful sci-fi with multiple light/dark color themes.

If this sounds interesting, sign-up on the site — I'd love to chat with you about this.

Oh my goodness yes!! This is the truth.

Shameless plug: I’m currently building https://AcornBookmarks.com for all the reasons you stated.

Nice, congrats on the launch!! I expect to switch over from YNAB once you enable automatic bank import.

This is why that's not a good answer: http://www.wheatbellyblog.com/2013/02/is-gluten-on-the-incre...

Haha, we thought about calling it that!

Your suggestions are great, and I totally agree with them. We just launched 3 weeks ago, so those items haven't been top priority. But they are on my list.

Thank you! :)

Purchase links are added a few different ways. We're an affiliate for Nuts.com, so we have access to their entire product list. It takes a bit of manual work to match up the data, but I'll be able to automate it as soon as it makes sense to do so.