flybayer

9 ms·

31.
by flybayer 3y ago
https://Flightcontrol.dev is a relatively new one that provides a PaaS-like experience on your own AWS account *I'm cofounder & CEO
32.
by flybayer 3y ago
https://Flightcontrol.dev
33.
Flightcontrol (YC W22) is hiring Developer Advocate (remote/fulltime)(jobs.flightcontrol.dev)
1 points by flybayer 4y ago
34.
Flightcontrol (YC W22) is hiring first Developer Advocate(jobs.flightcontrol.dev)
1 points by flybayer 4y ago
35.
by flybayer 4y ago
Flightcontrol | Developer Advocate | REMOTE (overlap 10a-12p EST) | Full-time Flightcontrol provides the deployment experience of a Platform-as-a-Service but without the limitations, since it uses your own AWS account. We're a 5 person
36.
by flybayer 4y ago
Blitz actually came first, so trpc is an alternative implementation of RPC. Blitz auth was developed at the same time as next auth, and takes a more imperative approach which allows you to build more custom auth flows.
37.
by flybayer 4y ago
Unless I'm missing something, Blitz RPC add's zero TS overhead. So the limitation will be the total amount of TS code you have which is not related to Blitz.
38.
by flybayer 4y ago
In simple terms: If you want to use GraphQL, use Redwood. If you want type safe client-server communication without GraphQL, then use Next.js + Blitz
39.
by flybayer 4y ago
Fair point. Messaging is so hard, we're still working on it. Here's a side-by-side comparison to GraphQL from some time back: https://twitter.com/flybayer/status/1256957956270120960
40.
by flybayer 4y ago
Thank you! It's still early for Flightcontrol and we have so much to improve. But we already have a non-trivial amount of production customers (including some very high traffic sites) and solid monthly growth. We're planning to sw
41.
by flybayer 4y ago
The whole idea is that you can do that, but we still have a bit more work to clean up internal package dependencies to make that nice. The goal for beta was to reach Next.js production feature parity with legacy Blitz. Now we can turn to cl
42.
by flybayer 4y ago
> with the "everything is a magic compiler" philosophy Blitz RPC has 1 minimal magic step, which is a webpack step to replace the resolver imports in client code with a fetch function and to add resolvers to the server-side API
43.
by flybayer 4y ago
> I'd strongly suggest having a direct comparison vs. tRPC page in the documentation Yes, it's coming. > does that mean it can be used with Vite? Yes, but we do have a bit more work to clean up our internal package dependenc
44.
by flybayer 4y ago
Slowdown with Typescript and IDE completion. Not runtime.
45.
by flybayer 4y ago
> (Blitz wraps NextJS wraps React) Again I repeat, that is what Blitz used to be . Blitz no longer wraps Next.js. It's no longer a framework.
46.
by flybayer 4y ago
> 1. Does the Blitz RPC thing work the same way as TRPC? Depends what you mean by "same way". Yes in that both provide fully typesafe client-server communication. No in that the Blitz implementation is a tiny fraction of the si
47.
by flybayer 4y ago
Everyone love's a skeptic :) If you properly build a large codebase using patterns like Clean Architecture, then tools like Next.js or Blitz should be fully isolated away from your app logic. If you need auth in Next.js, your options a
48.
by flybayer 4y ago
Sorry, bad wording. Just updated that. Blitz does not replace anything of Next.js. Rather, it compliments it's minimalism. To build a full app, you need to add a lot of things on top of Next.js. Blitz provides some of those libraries.
49.
by flybayer 4y ago
That's sort of what Blitz used to be, but not anymore
50.
by flybayer 4y ago
Blitz is very different. Next.js and Remix are comparable, but Blitz is a toolkit you can use with Next.js (and also Remix once we finish a bit more work). Blitz picks up where Next.js leaves off, providing libraries like a type safe RPC la
51.
by flybayer 4y ago
Hello, I'm the creator of Blitz.js [Feb 2020]: First announced. [Apr 2020]: First alpha release. [Feb 2021]: First beta release. [Dec 2021]: Decided to do major pivot. Today the Blitz.js 2.0 pivot to a modular Next.js toolkit reached B
52.
Flightcontrol (YC W22) Is hiring a back end TypeScript engineer [Own-cloud PaaS](flightcontrol.notion.site)
1 points by flybayer 4y ago
53.
by flybayer 4y ago
:) Mainly because we don't have a good mobile app story yet, although some are making it work. However this is top priority after our new 2.0 release.
54.
by flybayer 4y ago
Any of those, including RedwoodJS, will all give you plenty of performance! I highly recommend you build it in a monolithic approach, because it will make it a lot easier and faster to build. Since you are mobile app heavy, I would probably
55.
by flybayer 5y ago
Blitz doesn’t use GraphQL, one of the unique things about it.
56.
by flybayer 5y ago
No, DX will still be almost exactly the same on the user side.
57.
by flybayer 5y ago
It’ll be similar. Same result, but very different DX flavor. Also, new Blitz includes a plugin system, that allows you to easily integrate multiple modules, for example auth and RPC and have them work together seamlessly. And have things ju
58.
by flybayer 5y ago
The zero-API model doesn’t prevent specialization at all. You can add as many distinct domain layers as you want with different teams responsible for different layers.
59.
by flybayer 5y ago
What reliability issues did you have with Blitz?
60.
by flybayer 5y ago
Blitz is not becoming less opinionated. It’s just the implementation that is changing. The internals are significantly less complex now. Before, Blitz was a fork of Next.js, and dealing with that was a nightmare. Contributions dropped off s

More ›