201–210 of 293 posts
I'm going to be downvoted to hell for this... but the more I see the level of complexity and amount of engineering going into this, the more I miss Rails and how simple things are there, given most of us are just building CRUD apps anyways.
Earlier quoted context omitted.
1. I'm not sure about this premise: "leader of the production-ready frontend-as-a-service space." They def seem like a good fit for some frontends -- but they're certainly not a good fit for ALL frontends generally. (For example, sufficiently small sites should probably just go with static hosting, and sufficiently dynamic web apps still will want a SPA.) 2. At the end of the day, web backends are just a lot more var…
This is a really strong argument. At the end of the day I think it is possible (with iteration) to get the level of abstraction correct for something approaching some semblance of the universality you refer to. I really just want a framework that allows me to: 1) Run locally like Next.js's "npm run dev" 2) Do end-to-end unit tests because the framework provides the abstraction layer 3) Deploy to the cloud via push to…
Earlier quoted context omitted.
I have a system that supports optimized images in SSG that doesn't rely on any third-party services. But it requires custom config (babel macro plugin), though it only works for the most trivial websites. Let's break it down why its hard. If you want responsive, optimized images in a SSG context, without any dependency on 3rd party services, your only option is to pre-generate images at build time. Fair enough, you c…
This argument doesn't really make sense. > That means a whole lot of CPU that you need to burn during build This doesn't makes it hard, and I'd rather spend the CPU once than at every edge server on first request. > uses up loads of storage (that you need to ship to your static web server) Uploading to S3 (for example) is free, and the edge servers need to store the images anyways (because they are slow to generate a…
There are solutions available to all of these problems today. You can pick the ones which you prefer or fit your workflow.
This is really amazing, is the end result here that they are ultimately opting out of webpack in favor of SWC? It also compiles modules and such. Will have to take a look at the underlying infrastructure here! Interestingly I think that’s the major win of SWC over esbuild: you get a Babel like plug-in ecosystem for AST transformations and such. Downside: there currently isn’t a way to run asynchronous transforms, muc…
Earlier quoted context omitted.
Just use Gatsby v4 if you want good image support! v4 brings Gatsby in-line with Next.js because it introduced runtime SSR support like Next.
I assume that Gatsby generates the different widths/formats at build time. How well does that scale? Like if you have a thousand images, what's the build time like?
* like Gatsby Cloud https://www.gatsbyjs.com/products/cloud/
Earlier quoted context omitted.
The Rust compiler is just swc which has been around as another project for ages. Checkout it’s home page. Many people are using it.
Yeah, Deno is using it as well!
If Next.js + Vercel is the leader of the production-ready frontend-as-a-service space, why hasn't a similar leader emerged in the backend-as-a-service space? I would love a clean Vercel-like abstraction on top of standard cloud primitives (functions, queues, events, workflows, etc.) with everything wired up nicely and focused on developer experience. It just seems like AWS is so configuration heavy that it is ripe fo…
I'm going to be downvoted to hell for this... but the more I see the level of complexity and amount of engineering going into this, the more I miss Rails and how simple things are there, given most of us are just building CRUD apps anyways.
Earlier quoted context omitted.
How does it compare to esbuild? Seems they both want to achieve exactly the same thing, but somehow it's two different efforts.
One thing to keep in mind is that SWC is a compiler, whereas esbuild is a bundler. SWC has limited bundling capabilities last time I checked, so if you're looking for something to traverse your code and generate a single file (or multiple files at dynamic import boundaries, etc.) esbuild is what you want. Next.js bundles with webpack, so it uses SWC in lieu of Babel (or the TypeScript Compiler).
Earlier quoted context omitted.
Tried a couple shots at it Go Micro (17k stars) https://github.com/asim/go-micro Micro (10k stars) https://github.com/micro/micro M3O (1.7k stars) https://m3o.com
This appears to be a framework and not a hosted backend service