Great product. Them deciding to rebrand from Zeit to Vercel was one of the worst branding decisions ever made.
Next.js 9.5
21–30 of 40 posts
Re: Next.js 9.5
#22Earlier quoted context omitted.
You're not totally wrong, but think of it this way. You have native support in your application stack for this static 'caching' along with one-click edge distribution. Which means you can write extremely complex, interactive markup (it's just React) on top of this very simple distribution system. And you don't have to build a whole magic caching system or deal with web servers at all. I've worked with similar systems…
Hosting is separate from the framework, and the static site hosts you mentioned are just webserver + CDN packaged together with optional build/CI layer and some extra APIs to handle form submissions and user logins. Considering the number of CDNs and 1-click hosting, and the ease of putting them together, it's all pretty much the same. The big difference is that these static site frameworks are using React/Vue/etc fo…
Sort of, but not always.
My blog at https://www.silviogutierrez.com is React+Django strictly server side. I like JSX that much. Try loading it with JS disabled.
Same at my business site: https://www.joyapp.com.
It was a huge ordeal getting it setup (with React SSR, etc), but it's definitely doable. I've open sourced it but it sorely needs documentation (incoming):
https://github.com/silviogutierrez/reactivated
Basically, despite the tooling (not because of it), once you get going with JSX, TypeScript and the like, nothing else comes close. At least in my experience.
But again, none of the above stops me from dumping that output into a single cache key per request. It's still dynamic, just cached robustly.
Re: Next.js 9.5
#23Earlier quoted context omitted.
You're not totally wrong, but think of it this way. You have native support in your application stack for this static 'caching' along with one-click edge distribution. Which means you can write extremely complex, interactive markup (it's just React) on top of this very simple distribution system. And you don't have to build a whole magic caching system or deal with web servers at all. I've worked with similar systems…
Hosting is separate from the framework, and the static site hosts you mentioned are just webserver + CDN packaged together with optional build/CI layer and some extra APIs to handle form submissions and user logins. Considering the number of CDNs and 1-click hosting, and the ease of putting them together, it's all pretty much the same. The big difference is that these static site frameworks are using React/Vue/etc fo…
Not quite. Next allows you to dynamically generate static content both at build time – and with this latest update – at _runtime_ as well. It generates code-split bundles for each page, enabling extremely thin pages to minimize the amount of content loaded with zero configuration. You nailed the big advantage though, more eloquently than I was able to articulate: a unified code-base for both initial rendering and interactivity.
Next _also_ supports rendering things on the server if you'd like. So you're not giving up anything at all, there's no trade-off with respect to rendering patterns, unless you just prefer to use another language to build your 'frontend'.
Hosting is 'separate', but the framework snugly fits into a modern hosting paradigm in a way that most others do not.
Re: Next.js 9.5
#24Great product. Them deciding to rebrand from Zeit to Vercel was one of the worst branding decisions ever made.
Curious, why do you think that?
Any rebranding will have backlash. It solved the issue of ZEIT Now being one _product_ whereas Vercel is the _platform_. It also brought a new focus on Jamstack and front-end developers.
I'll admit I'm biased though, as I'm a Vercel customer.
Re: Next.js 9.5
#25Incremental Static Site Regeneration is really compelling, I wonder what the gotchas are. For instance, I have a project where the front page gets server-side-rendered for logged out users. We can't do client-side-rendering because we care about SEO. And we can't do static-generation at build time because the content of the front page regularly changes (it summarizes activities of other users). But with incremental s…
I haven't really kept up to date in this area so would love to hear some experts weigh in here: Do search engines (or really just Google) still penalize sites that are pure SPAs on that fact alone? Or does it have more do do with properties generally associated with SPAs like large bundle sizes or slow time to first interaction? I'm mainly wondering if you can build a SEO-friendly SPA marketing page today using techn…
If its important that your sites content will be shared on social media then SSR is a must due to meta tags Facebook/Twitter use to create the posts preview.
Re: Next.js 9.5
#26Beautiful release!
Re: Next.js 9.5
#27i love vercel and use it for all my projects, right up until i need to add auth/api, at which point I switch off of it immediately for security reasons because there are no static IPs unless you're an "enterprise" customer it's unclear why they're rolling out performance features while this critical security hole persists. no doubt i'll get flamed for it, but, it's a really bad idea to use dynamic IPs to connect to y…
I guess you’re talking about Vercel.com instead of Next.JS, right?
Yep
Re: Next.js 9.5
#28Earlier quoted context omitted.
Hosting is separate from the framework, and the static site hosts you mentioned are just webserver + CDN packaged together with optional build/CI layer and some extra APIs to handle form submissions and user logins. Considering the number of CDNs and 1-click hosting, and the ease of putting them together, it's all pretty much the same. The big difference is that these static site frameworks are using React/Vue/etc fo…
Sort of, but not always. My blog at https://www.silviogutierrez.com is React+Django strictly server side. I like JSX that much. Try loading it with JS disabled. Same at my business site: https://www.joyapp.com . It was a huge ordeal getting it setup (with React SSR, etc), but it's definitely doable. I've open sourced it but it sorely needs documentation (incoming): https://github.com/silviogutierrez/reactivated Basic…
I'm a fellow django + react developer. What are your thoughts around moving to Next.js?
Re: Next.js 9.5
#29Earlier quoted context omitted.
Sort of, but not always. My blog at https://www.silviogutierrez.com is React+Django strictly server side. I like JSX that much. Try loading it with JS disabled. Same at my business site: https://www.joyapp.com . It was a huge ordeal getting it setup (with React SSR, etc), but it's definitely doable. I've open sourced it but it sorely needs documentation (incoming): https://github.com/silviogutierrez/reactivated Basic…
I'm a fellow django + react developer. What are your thoughts around moving to Next.js?
In my opinion: nothing, and I do mean nothing, comes close to the productivity of Django + Forms + FormSets + Admin. I've tried everything under the sun[1]
The model->form and presentation layer is so intuitive and robust that I'm surprised no JS framework has rebuilt it. Too much is focused around REST instead of domain specific inputs / outputs.[2]
So yea, I've focused on making Django more React-friendly. I want to stick to it.
[1] Ok, maybe Rails comes close.
Re: Next.js 9.5
#30i love vercel and use it for all my projects, right up until i need to add auth/api, at which point I switch off of it immediately for security reasons because there are no static IPs unless you're an "enterprise" customer it's unclear why they're rolling out performance features while this critical security hole persists. no doubt i'll get flamed for it, but, it's a really bad idea to use dynamic IPs to connect to y…
Can you expand on what the static IPs give you?