News for hackers. Stuff that matters.
Re:The Frontend Treadmill by cyberax on Thursday March 20, 2025 @03:01PM (#43427504)
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.

Re:The Frontend Treadmill by wolvesechoes on Thursday March 20, 2025 @05:26PM (#43429168)
Yes, saying that calling Win32 APIs is not the most ergonomic approach to writing UIs would be an understatement, but if any software can be called stable, this is it.
Re:The Frontend Treadmill by icar on Thursday March 20, 2025 @06:57PM (#43430021)
I would compare win32 API to vanilla JS. Whatever framework you might want to use on top of win32 is what's comparable to the criticized web tech in the article.
Re:The Frontend Treadmill by lenkite on Thursday March 20, 2025 @05:56PM (#43429434)
Your win32 app would have been much faster with much less memory hogging though. I would prefer to run that compared to your React app.
Re:The Frontend Treadmill by cyberax on Friday March 21, 2025 @12:37AM (#43431896)
The choice really is between React and nothing. React (and Electron) enabled a lot of apps to be written that would not have existed otherwise.
Re:The Frontend Treadmill by pjmlp on Friday March 21, 2025 @07:59AM (#43434594)
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.

Re:The Frontend Treadmill by Quiark on Monday March 31, 2025 @09:57AM (#43535140)
I liked it in the Jurrasic park