Back when REST was a new hot buzzword and people were debating its true meaning, I remember thinking that some of the arguments for HATEOAS only really made sense if your client apps were going to be some kind of AI graph navigators. So I wonder if being particular about HATEOAS makes more sense now?
How does any of that apply to this particular article? Isn't a broader historical perspective exactly what's needed if you want to be free from the immediate hype cycle?
One of my biggest irritations with HN comment sections is how frequently people seem to want to ignore the specific interesting thing an article is about and just express uninteresting and repetitive generic opinions about the general topic area instead.
IIRC the last couple of releases had some new/overhauled features they said were built for both from the same code, so they seemed to be starting down the path of slowly converging them, before they changed their minds and discontinued the Mac version I guess.
It's really something I know nothing about so I googled WinUI3 and the 3 first results are microsoft website and github, and the next two are "is winui3 dead ?" and "Oh winui3 is really" dead. So it doesn't inspire confidence :)
I suppose it was incorrect of me to say it hasn't "officially" launched then. But one would certainly seem to get that impression, considering it's missing major features (data table support?) isn't anywhere near feature parity with either WPF or winforms, and doesn't even have a visual editor (which should be table stakes for a modern 1.0 release from a company as large as Microsoft).
Wow. This is amazing. I can't say how happy I am that you posted this. I've never seen this site before... and I explicitly went looking for something like this a while back, and somehow did not find this. I've been fascinated by the FGCS stuff for a long time, and had always thought there must be an archive of that body of knowledge somewhere, but other than a few books on Concurrent Prolog I had not managed to scare up much of it.
Now, I find that more or less all of it is online and available? All the Technical Reports, all the Technical Memoranda, and even the software? Amazing. Now if only I read Japanese...
Also, RAM, CPU and disk space are shared resources on PCs. If your computer is slow you don't necessarily attribute it to any particular program, let alone website. As Terry Crowley says here https://terrycrowley.medium.com/software-ecology-bb4653046fd...
"... the cost of bloat is not directly borne by the those introducing it. Individual efforts to reduce bloat have little effect since there is always another bad actor out there to use up the resource and the improvements do not accrue to those making the investments."
"The classic response to accusations of bloat is that this growth is an efficient response to the additional resources available with improved hardware. That is, programmers are investing in adding features rather than investing in improving performance, disk footprint or other efforts to reduce bloat because the added hardware resources make the effective cost of bloat minimal. The argument runs that this is in direct response to customer demand.
It is most definitely the case that when you see wide-spread consistent behavior across all these different computing ecosystems, it is almost certainly the case that the behavior is in response to direct signals and feedback rather than moral failures of the participants. The question is whether this is an efficient response.
The more likely underlying process is that we are seeing a system that exhibits significant externalities. That is, the cost of bloat is not directly borne by the those introducing it. Individual efforts to reduce bloat have little effect since there is always another bad actor out there to use up the resource and the improvements do not accrue to those making the investments. The final result is sub-optimal but there is no obvious path to improving things."
Web pages/applications are probably even worse in this regard because I'm not sure users even conceptualize them as using resources on their local computers, so they don't get blamed for it (people seem to attribute resource usage only to the web browsers, not the sites themselves)
