Next.js Reviews

1. Kurslog team

   · Working at Kurslog · 3 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

StackGres Reviews

Next.js mentions (1139)

• Ops Assist: AI-Powered Manufacturing Troubleshooting with Gemma 4

  This is a Next.js project bootstrapped with create-next-app. - Source: dev.to / about 1 month ago

• Next.js vs Remix: What's the Difference?

  Anyone who's worked with React knows it's easy to get started with, and you can quickly become quite productive. However, once you move beyond the basics and need full-stack capabilities, like server-side rendering (SSR), selecting a React framework becomes the next step. Two of the most popular frameworks are Next.js and Remix. Both provide powerful tools to build high-performance web applications, but their... - Source: dev.to / about 2 months ago

• Inside a 3-app Turborepo monorepo: parallelism, caching, and CI that stays fast

  Apps/web — authenticated dashboard, Next.js 16 App Router. - Source: dev.to / about 2 months ago

• Typescript Monorepo Development using Docker Compose Watch, Turborepo and PNPM

  This simple project runs a Next.js app which has the Prisma ORM client as a shared package. Prisma was chosen specifically because the client requires code-generation that must be run locally as well as in the container, and setting it up also demonstrates how to configure the environment so Prisma can talk to the Postgresql database from the host as well as when run in the container. - Source: dev.to / about 2 months ago

• How to Set Up NextJS with Tauri

  Const isProd = process.env.NODE_ENV === 'production'; Const internalHost = process.env.TAURI_DEV_HOST || 'localhost'; /** @type {import('next').NextConfig} */ Const nextConfig = { // Ensure Next.js uses SSG instead of SSR // https://nextjs.org/docs/pages/building-your-application/deploying/static-exports output: 'export', // Note: This feature is required to use the Next.js Image component in SSG mode. ... - Source: dev.to / 2 months ago

StackGres mentions (10)

• TimescaleDB compresses time-series data

  At StackGres [1] we find Timescale to be one of the most used extensions. Timescale is quite a successful project! StackGres is actually the first solution recommended by Timescale for self-hosting with Kubernetes operators [2]. So if you are into Kubernetes (or if not, consider it, using something like K3s [3] is quite straightforward and lightweight on resources), this is probably a great option to self-host... - Source: Hacker News / 20 days ago

• Show HN: SQL-tap – Real-time SQL traffic viewer for PostgreSQL and MySQL

  * Latency. Yes, yes, yes, they add "microseconds" vs "milliseconds for queries", and that's true, but just part of the story. There's an extra hop. There's two extra sets of TCP layers being traversed. If the hop is local (say a sidecar, as we do in StackGres) it adds complexity in its deployment and management (something we solved by automation, but was an extra problem to solve) and consumes resources. If it's a... - Source: Hacker News / 5 months ago

• Application Less Containers

  This is conceptually similar to what we did for Postgres extensions at the StackGres [1] project. I gave a talk at a Kubecon about it [2]. However, this scheme is not perfect. Some Kubernetes security solutions enforce immutable containers, and once the agent pulls any additional file into the container, it will be flagged. It's also harder to reason about the security of the image (think CVEs, etc), given that... - Source: Hacker News / 11 months ago

• Pg_lakehouse: Query Any Data Lake from Postgres

  I applaud the decision to use AGPL-3.0. For me, it's a license that provides forward guarantees to the Community: no proprietary forks can happen, so any fork will be an OSS fork from which the upstream project may benefit too, which benefits all users. That's the reason we chose this license for StackGres [1], another project in the Postgres space. [1]: https://stackgres.io. - Source: Hacker News / about 2 years ago

• Keycloak with PostgreSQL on Kubernetes

  This is good and interesting recipe to get Keycloak and Postgres on Kubernetes. There is an important improvement, though: the Postgres deployed here is not production ready (high availability, backups, monitoring, etc). We run Keycloak on StackGres [1] which gives us production-ready Postgres setup (disclaimer: it's dogfooding). Happy to share the YAML manifests used to deploy Keycloak with StackGres. Maybe we... - Source: Hacker News / about 3 years ago