>Doesn't look radically different to how a GUI app that targets a native framework would look today

Modern "Native" frameworks are part of the problem. I cant comment on Windows current state as I havent used Windows since I moved my gaming rig from Windows 7 to Linux many, many years ago but even then Windows frameworks were a complete mess

Take Libadwaita for example. I migrated an old, very simple disk image manipulation utility app last year from GTK2 to modern gnome. No change in capabilities, a simple clone in GTK4 / Libadwaita. It went from using ~19MB to ~185MB without any additional functionality simply by switching the "Native" framework

Sometime in the late 90s there started a fundamental change in the software development process. We changed from optimising software for the end user (development is difficult) to optimising the software development process for the developer at the expense of user resources

The fact that we are celebrating that a chat app only uses 300MB ram at launch instead of 1GB seems absolutely ludicrous to me

The early versions of Skype used about 30MB RAM while in a video call and by the early 2000s standards it was bloatware. Before that we used WebEx in the 90s which was a browser ActiveX or Java applet and RAM use was about 6MB in a video call. In the early / mid 90s I used CU-SeeMe for video calls and its RAM footprint was just over 2MB on Mac System 7

Something has clearly gone very wrong in the software development process in the last 2-3 decades and while Im encouraged to see that some people are interested in reversing that trend I still find the resource wastage has me shaking my head sometimes

Its an interesting comparison that Im not sure reflects positively on the RISC-V C906 core when you factor in core area and process nodes and core area, 22nm vs 250nm. Even if we choose the worst case scenario for the P3 cores to compare which would be the Katmai core. We are basically look at ~parity with a 30 year old core design

C906 core only @ 22nm = ~0.6 mm2

C906 core only @ 250nm = ~78 mm2 (geometric transform)

P3 core only @ 22nm = ~0.5 mm2 (geometric transform)

P3 core only @ 250nm = ~76 mm2

Apologies if this is messy and badly formatted. Im currently at a wedding, sat waiting between the ceremony and the after party and Ive quite a few beers. I responded because its something I looked at previously with RISC-V cores and I already had the answers in my head

I cant see it. I was in the embedded dev world from the early 90s to mid 2000s before I moved into infrastructure architecture. The mostly homogeneous world we currently live in is just not even close to what we had in the 90s. At one point I had a Next Cube, an IBM RS/6000 (AIX 4.x Unix), a BeBox (BeOS), an OS/2 system (PPC), a Sun SparcStation and 2 x NT 3.x system (x86 and PPC) all sat in my office at the same time. The diversity of hardware and operating systems is just not comparable to today. It was an exciting time of rapid development and change and we were aware of it. Much different to what we have now where we just like to pretend we are in a time of rapid development and change but the reality is incremental change and small increments at that outside of AI

I havent found anything in the IT world to excite me for close to 20 years. The expanding core counts were interesting to start with but soon got boring. The introduction of ARM was hardly an excitement. RISC-V is dead as far as performance designs go though its a great micro controller arch. Software is abstraction layer piled on top of abstraction layer piled on top of abstraction layer. There is almost nothing new and hasn't been for a long time