Next.js Reviews

1. Kurslog team

   · Working at Kurslog · 5 months ago

   Next.js has become the de-facto standard for our frontend engineering team when building modern web applications. The Server-Side Rendering (SSR) and Static Site Generation (SSG) are absolutely essential for our product's SEO strategy and fast indexing.

   The transition to the App Router initially required a paradigm shift for our developers, but it ultimately made our architecture much more scalable. We love that the framework handles the heavy lifting—image optimization, code splitting, and routing—allowing our team to focus purely on business logic. It provides a phenomenal Developer Experience that keeps our deployment cycles fast and predictable.

   Competitors: Remix, Nuxt.js, Svelte, Vite

   Pros:    Out-of-the-box ssr and ssg for excellent seo|Superb developer experience with zero-config setup|Built-in optimizations for images, fonts, and scripts|Highly scalable routing via the app router

   Cons:    The app router requires a paradigm shift and learning curve for the team at first|Caching strategies can be tricky to master and debug across a large, dynamic app

stackprof Reviews

Next.js mentions (1145)

• Building a Multilingual Shop with Next.js

  In this article, we’ll look at how to approach these problems in a Next.js application using the App Router. Rather than focusing on the basics of translating strings, we’ll focus on the technical decisions behind the implementation: how the language is detected, how it’s propagated through the application, how translations are loaded on the server and client, and how localized routes are handled. - Source: dev.to / 7 days ago

• What Browserslist Actually Does in Next.js

  We set up three near-identical Next.js 16 projects to answer a simple question: if you set a browserslist target in package.json, does the build change to match it? We tested three targets (ie 11, chrome 116, about 3 years old, and chrome 139, about 1 year old) and compared the compiled output byte by byte. - Source: dev.to / 5 days ago

• We’re all full stack now

  Blurring of the lines. React Server Components (RSC) and associated frameworks such as NextJS involve code executing on both server and client, while HTMX focuses on markup and emphasises use of full-stack/backend templating engines to generate code targetting the browser. Working with these new tools blurs the distinction between the front end and back end skill set. - Source: dev.to / 16 days ago

• The Past Keeps Changing

  What replaced the laptop, before we get to the schema: Health Auto Export now posts straight to a Vercel function on a daily schedule, a scheduled job pulls lifting history from Liftosaur, and both land in TimescaleDB on Tiger Cloud. No files, no iCloud, no Mac. A Next.js app reads it and tells me whether I hit protein, which is a separate post. - Source: dev.to / 18 days ago

• Getting Started with Shadcn Checkbox in React & Next.js

  This guide shows you how to install and use the Shadcn Checkbox component in React and Next.js. - Source: dev.to / about 2 months ago

stackprof mentions (3)

• A Trick For Reading Flamegraphs

  Stackprof can be used alone/by itself to generate flamegraphs for arbitrary Ruby code. - Source: dev.to / almost 4 years ago

• Why do my requests take so much time to complete when View and ActiveRecord are finishing fast?

  I’d use something like stackprof ( https://github.com/tmm1/stackprof ) to see where the time is going. If you already have suspicions you can use it to get information about a specific method / few lines of Ruby but there’s also a rack middleware. Source: about 4 years ago

• Optimizing your tests in 5 steps

  Other profilers, such as stackprof, trace everything that’s happening by line. These types of profilers usually need some instrumentation to be configured, as shown below:. - Source: dev.to / over 4 years ago