News for hackers. Stuff that matters.

A comment on .NET 5.0. Parent comment

Re:.NET 5.0 by ClumsyPilot on Tuesday November 10, 2020 @12:54PM (#25048808)
I fail to see how this is sensible in the slightest - you then have to re-write the code if you want the application to scale. Otherwise you are wasting memory, trashing GC, spawning all these extra threads.All awaitable operations like network requests, disk reads, etc, should be async. Why would you write potato code?
[ Parent | on HN ]
Re:.NET 5.0 by nullsense on Tuesday November 10, 2020 @02:36PM (#25050620)
>Why would you write potato code?

Side note: this gave me a good laugh. I just pictured it being used as a sign off on PR reviews.

Is it a technical term? If it's not I think it should be, and if it is I want to know what the exact nature of potato code is, so I can call it out when I see it in the wild.

[ Parent | on HN ]
Re:.NET 5.0 by Scarbutt on Tuesday November 10, 2020 @09:53PM (#25055036)
you then have to re-write the code if you want the application to scale.

Scaling machines (VMs, containers) is a solved problem and very easy to do today.

[ Parent | on HN ]