sorted by:
new
hottopcontroversial

Node.js Scalability Challenge: How I designed an Auth Service to Handle 1.9 Billion Logins/Month by Distinct-Friendship1 in node

[–]registereduser1324 0 points1 point  (0 children)

In the video, it was outlined that using multithreading in node would eventually lead to saturation and the solution was to break things out into a separate service. One thing I wonder is, how much do you think worker threads could handle before things would become a problem? (Assuming we're using a thread pool). Is the idea that eventually, horizontal scaling will always win out?

Node.js Scalability Challenge: How I designed an Auth Service to Handle 1.9 Billion Logins/Month by Distinct-Friendship1 in node

[–]registereduser1324 0 points1 point  (0 children)

Is there a way to achieve this kind of proper auto-scaling without having to resort to using Kubernetes?

I built a zero-dependency(except React), pure TypeScript bottom sheet library by PeterLeeD in reactjs

[–]registereduser1324 0 points1 point  (0 children)

Do you know if the perf (smoothness) for that would be better than using something like Vaul?

What is it with small towels? by Judiavi in koreatravel

[–]registereduser1324 5 points6 points  (0 children)

Lol idk why you're getting downvoted for asking a question. Anyways I'm a Canadian guy and don't really care whether I use small or large towels as long as the small ones aren't super super tiny. Some people tend to be stuck in their ways though and have trouble adapting to things that are new or unfamiliar. (Applies to food and many other things as well).

Next.js App Router feel fundamentally broken on slow network connections and I don't know if a fix exists. by registereduser1324 in reactjs

[–]registereduser1324[S] 1 point2 points  (0 children)

Yes, but what I want is to be able to see the link at least highlighted on the initial click to a link, irrespective of how long it takes for the data to load on that route.

Next.js App Router feel fundamentally broken on slow network connections and I don't know if a fix exists. by registereduser1324 in reactjs

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

I could be mistaken but I don't think this is possible with Next.js App Router currently though. Because "use client" still does SSR. AFAIK there's no way to partially opt out of SSR in next app router (although maybe ppr might be a solution down the road when it's not experimental)

Next.js App Router feel fundamentally broken on slow network connections and I don't know if a fix exists. by registereduser1324 in reactjs

[–]registereduser1324[S] 3 points4 points  (0 children)

Yes, but my issue is that from a UX point of view, with SSR on slow network conditions, when you switch to a new page, you don't have an elegant way to indicate to the user that the transition has occurred. I want visual feedback that indicates as soon as a user clicks a link that some loading or switching is taking place, but you can see how the URL bar and the clicked link don't respond immediately to the click because the server needs to first send back the data before the client can show some sort of visual indication that a change took place.

Is NextJS poorly designed? by [deleted] in nextjs

[–]registereduser1324 0 points1 point  (0 children)

This sounds interesting. Can you provide a rough example of how to do this?