Next.js Reviews

GraphQL Cache Reviews

Next.js mentions (1068)

• What I learned building my first AI Agent – Part 1

  After refining the user interface and doing some tests, I had a minimal functional AI agent capable of answering questions about Figma features . Since I was using Next.js, I decided to host my app on Vercel, since it was the platform that provided me the easiest and most intuitive way to do it. I was very happy with the result, even though the application was simple, in just a few days I managed to learn about... - Source: dev.to / about 24 hours ago

• We Fell Out of Love with Next.js and Back in Love with Ruby on Rails

  3. Load personalized data (json) But usually step 1 and 2 are served from a cdn, so very fast. On subsequent requests, 1 and 2 are usually served from the browser cache, so extremely fast. SSR is usually not faster. Most often slower. You can check yourself in your browser dev tools (network tab): https://www.solidjs.com/ vs. https://nextjs.org/ So much complexity and effort in the nextjs app, but so much slower. - Source: Hacker News / 4 days ago

• 25+ Top UI frameworks & libraries for Next.js

  If you are overwhelmed with dozens of UI frameworks and libraries available, you are not alone as a developer. With so many UI Frameworks for Nextjs each claiming to be the best it’s tough to decide which one truly fits your project. - Source: dev.to / 6 days ago

• Build a Job Application and Interview App with Next.js, Stream & Firebase

  In this tutorial, you will learn how to build a job application and interviewing platform using Next.js, Stream, and Firebase. This app will allow recruiters to post job openings, review applications, and schedule interviews. Job seekers can also apply for jobs and communicate with recruiters. - Source: dev.to / 14 days ago

• Next.js Localization: How to Build a Multilingual Website with Next-Intl

  In this section, you will learn how to bootstrap a basic Next.js application. - Source: dev.to / 15 days ago

GraphQL Cache mentions (4)

• What are the Differences between GQL and REST?

  'id' data type and field to help support caching: https://graphql.org/learn/caching/. Source: over 2 years ago

• GraphQL Is a Trap?

  > Take a look at this. I repeat: client-side caching is not a problem, even with GraphQL. The technical problems regarding GraphQL's blockers to caching lies in server-side caching. For server-side caching, the only answer that GraphQL offers is to use primary keys, hand-wave a lot, and hope that your GraphQL implementation did some sort of optimization to handle that corner case by caching results. Don't take my... - Source: Hacker News / about 3 years ago

• GraphQL Is a Trap?

  > Checkout Relay.js: https://relay.dev/ Relay is a GraphQL client. That's the irrelevant side of caching, because that can be trivially implemented by an intern, specially given GraphQL's official copout of caching based on primary keys [1], and doesn't have any meaningful impact on the client's resources. The relevant side of caching is server-side caching: the bits of your system that allow it to fulfill... - Source: Hacker News / about 3 years ago

• Designing a URL-based query syntax for GraphQL

  This is clever! Can anyone help me understand how this lines up with the original value proposition of GraphQL? I was under the impression that the Big Idea behind GraphQL was, amongst other things, client-side caching[1]. I’m probably missing some nuance here, so bear with me: if your GraphQL client is caching properly, then what would this syntax give a developer that a URL query parameter parser couldn’t? [1]... - Source: Hacker News / almost 4 years ago