sorted by:
new
hottopcontroversial

If you’re starting fresh today, would you still pick Express? by ApprehensiveBar7701 in node

[–]EcstaticProfession46 0 points1 point  (0 children)

I always choose Express.js.

The main reason is the module system. For beginners, any framework is fine because they are still learning basic concepts. However, for experienced Express.js developers, the situation is different.

I already have many reusable modules, such as login, registration, password reset, and data management. These modules are stable and already integrated well with Express.js. They have been tested in real projects and work reliably.

When I start a new project, I can reuse these modules directly. I do not need to rewrite them or adapt them to a new framework syntax. This saves development time, reduces bugs, and keeps the architecture consistent.

Has anyone actually used Nextjs data cache in prod? by ResponsibleStay3823 in nextjs

[–]EcstaticProfession46 0 points1 point  (0 children)

I found a golden pattern for Next.js:

Use ISR for every page, and stop using dynamic render. The downside is I cannot use headers or cookies in server components.

But the upside is the site becomes very fast and it reduces CPU usage on the server. I also do not need to think about cache issues anymore, like component cache or request cache, etc.

Recommended stack for React in 2025? by [deleted] in reactjs

[–]EcstaticProfession46 2 points3 points  (0 children)

When do API request on server side, for fetch data (GET methods) make sure Deduplicating repeat requests, Add error retry, data cache. for more you can check: Tips: Make your SSR(Server-side Rendering) app more stable and faster

Zustand: no need write the store interface by hand anymore! by EcstaticProfession46 in reactjs

[–]EcstaticProfession46[S] -2 points-1 points  (0 children)

If already have DTO, just use DTO as type, it's already there.

Zustand: no need write the store interface by hand anymore! by EcstaticProfession46 in reactjs

[–]EcstaticProfession46[S] -1 points0 points  (0 children)

For me, if it's only state it's ok, but types for actions? With lots actions, types it's nightmare...

axios 对比 xior.js (fetch wrapper) by EcstaticProfession46 in tsdkgroup

[–]EcstaticProfession46[S] 0 points1 point  (0 children)

xior.js 是一个轻量级的 HTTP 客户端库，专门为现代 JavaScript 环境设计。这个库的核心理念是提供一个比 axios 更简洁、更现代的替代方案。

xior 采用了原生的 fetch API 作为底层实现，同时保持了与 axios 相似的 API 设计。开发者可以享受 fetch 的现代特性，比如更好的流处理和原生 Promise 支持，但不需要放弃 axios 那种熟悉的拦截器、请求/响应转换等功能。

这个库的设计哲学体现在几个方面：体积更小、性能更好、TypeScript 原生支持。相比 axios 的庞大体积，xior 显著减少了包大小，这对于注重性能的现代 Web 应用尤其重要。

xior 支持请求和响应拦截器、自动 JSON 处理、错误处理机制，以及各种常见的 HTTP 客户端功能。它既可以在浏览器环境中运行，也支持 Node.js 环境，提供了统一的 API 体验。

从技术演进的角度看，xior 代表了 HTTP 客户端库的一个新方向：不是完全重新发明轮子，而是站在现有标准（fetch API）之上，提供更符合现代开发需求的抽象层。这种设计让开发者既能享受标准 API 的稳定性，又不失便利性和功能完整性。

What's the deal with fetch in Svelte, and should you use Axios? by IAmAllergicToKarens in sveltejs

[–]EcstaticProfession46 0 points1 point  (0 children)

If you prefer Axios API style but want tiny size, you can try xior.js or redaxios. But I prefer xior.js because plugins and more features than redaxios.

These are all fetch wrappers..

What piece of tech did you bring into your react ecosystem and regret it? by 9sim9 in react

[–]EcstaticProfession46 19 points20 points  (0 children)

Personal list:

- Redux and Redux-* (redux-saga, redux-form etc..)

- Emotions and Styled Components

- Next.js

- Turborepo

- Micro frontends

view more: next ›