The Frontend Treadmill

Post by kerkeslager » Wed, Mar 26, 2025, 3:08 PM UTC

agos wrote: post #636

kerkeslager wrote: post #318

Earlier quoted context omitted.

> If it's a 5 year old project, you probably shouldn't be building it with the current versions of tools. Bold of you to assume I have worked in React for this long and somehow didn't know about this brittle solution to a problem which shouldn't have existed in the first place. How does your solution handle packages that no longer exist? Let me guess, we back up the packages? Okay, so these packages don't run on new…

wait, what package does no longer exist? is it something that has been unpublished from NPM?

https://en.wikipedia.org/wiki/Npm_left-pad_incident

People arguing with me here don't seem to remember this breaking like 1/2 the JS builds in existence for a few days.

Post by Quiark » Mon, Mar 31, 2025, 1:57 PM UTC

pjmlp wrote: post #590

cyberax wrote: post #296

Earlier quoted context omitted.

On the other hand, I can write a very complicated graphics-related app in React+tons_of_libs within _days_. It took me months to do that in Win32 API in 2005. The developer velocity enabled by React is insane.

Calling Win32 directly was already old fashion when Windows 95 came out in 1994, let alone 2005 when .NET was four years old. The only folks already doing Win16 development with pure C code, instead of a C++ framework (OWL, MFC, VCL), VB or Delphi, were stuck in jurassic park. The only valid reason for raw Win32 applications are games.

I liked it in the Jurrasic park

Re: The Frontend Treadmill

Re: The Frontend Treadmill