---
title: "Dávid Szabó (@davidszabo) | Hashnode"
description: "Lead Software Engineer @ Suxess Logistic. Read the latest articles by Dávid Szabó on Hashnode."
url: "https://hashnode.com/@davidszabo"
---

@davidszabo

# Dávid Szabó

@davidszabo · Hungary · Joined June 2021

Lead Software Engineer @ Suxess Logistic

[Website](https://daveiscoding.com/)

## Comments

[The caching problem alone was a dealbreaker for us. We built a proof-of-concept in Qwik, Next.js, and Remix. So far, we have had the best experience with Qwik and Remix, but we wanted something closer to Next.js, so we went with Remix. Next.js feels too corporate nowadays. They are pushing their ideas, and I feel like they keep ignoring the community (their users). The caching issue is a perfect example for this.](https://hashnode.com/posts/re-evaluating-nextjs-did-it-go-the-wrong-path/65f8145981fd393af03fe62a/comment/65fbdbbfbd4a90d90edf7bca)

Comment · Article · Mar 21, 2024 · [Re-evaluating Next.js: Did it go the wrong path?](https://hashnode.com/posts/re-evaluating-nextjs-did-it-go-the-wrong-path/65f8145981fd393af03fe62a)

[That would break the compilation because the paths are always relative to the original configuration file. In this case, specifying these paths in the tsconfig.base.json, would mean that the paths are relative to the base file. https://www.typescriptlang.org/tsconfig#extends Properties with relative paths found in the configuration file, which aren’t excluded from inheritance, will be resolved relative to the configuration file they originated in.](https://hashnode.com/posts/nodejs-typescript-monorepo-via-npm-workspaces/62f8e35b69fa1793160c55e8/comment/63e28983cecce1c954ae00e8#reply-63f0ab6a34c25f8061772f7b)

Reply · Article · Feb 18, 2023 · [Node.js TypeScript monorepo via NPM workspaces](https://hashnode.com/posts/nodejs-typescript-monorepo-via-npm-workspaces/62f8e35b69fa1793160c55e8)
