That's really fun, but to be sufficiently poe-faced for HN, it does maybe highlight some of the issues that cause people to grouse about web apps vs native apps (not that many apps are truly native these days). The set of controls apps use has changed over time and some of the old "power user" controls just aren't there anymore. I think this is maybe part of what people get at when they express a preference for native UI. Classic desktop OS widget toolkits like ComCtl32, Cocoa, Swing, JavaFX, Qt etc were built up over very long periods of time and thus have a lot of very powerful controls and subtle behaviors that helped you be productive.<p>In contrast, HTML5 has an absolute poverty of UI controls. The web community ended up settling on React + "design systems" to try and patch their way out of this, but because theming and widget toolkits get blended together in this approach the widgets are constantly being reinvented and end up half baked compared to desktop UI frameworks, which separate theming from widget behavior and thus get way more investment in the core feature set.<p>This shows up in a lot of subtle ways, and a few not so subtle ways. For example there are some controls common in Win95 apps that are conspicuously missing here:<p>• Virtualized list view with resizable/movable headers. There doesn't seem to be a list view control at all, in fact. The control they call list is actually a menu!<p>• Yet there's no menu bar, and the menu ("list") doesn't seem to be a real context menu. Right click an item in the tree view and you get the browser context menu, which is useless.<p>• There's no tree table view.<p>• The range control doesn't have notches or the ability to see the value you're sliding.<p>etc. And of course you can forget about all the little features Win95 widgets had like proper keyboard support (try using the up/down arrows in the tree view, it doesn't work).<p>Now obviously this is just a fun hobby project. It's not meant to be an actual widget toolkit competitive with Windows 95, so the criticism above isn't "real" criticism, it's just a springboard for a bit of technical observation: it's 2023! Why does the web still not have a UI framework competitive with an OS that came out nearly 30 years ago? If you wanted to make a Win95 theme for Qt or JavaFX then it would be quite easy and you would actually be able make apps that were competitive with Win95 apps in terms of UI features. But the React+DOM approach can't manage that because the effort required to flesh out the widgets is split between a thousand design systems. That seems wrong and is part of why web UI feels kinda dumbed down compared to what we once had.