Yeah, I'm not sure if "partnerships" is what my project would be looking for either. I'm honestly curious on the purely conceptual level of how you think the corporate world might approach the concept of "very stateful" clients. FWIW, most of my interest is in enabling DIY/hobbyist and academic research use cases that would in fact want as much client-side statefulness as possible.
I guess I don't really understand the idea of macros extremely well. In your system, is it basically a function that's dynamically generated from the interface that is bound to a context-sensitive keyboard shortcut?
Well, GNU/Linux, as such might not, but the various desktops that run atop it most certainly should care.
Re: ACK! THBBFT!: Just my personal ode to Bloom County which I feel must certainly be regarded as the greatest comic strip ever. (I need to wait for others to start coming on board with the project before I worry about doing things for any other reason than pure self-amusement.)
As long as web applications are necessarily embedded inside of SCRIPT elements, which are themselves necessarily embedded inside of HTML elements, then documents will always have priority over applications.
I don't see the "binaryification" of the web platform happening any time soon (if ever). The web is (and should remain) fundamentally about the transmission of documents. Javascript+DOM allows for the dynamic updating of said documents, and this is what the main thread (asynchronous event loop) is all about. For all "heavy lifting," the logic should go into worker threads, where there isn't any DOM access anyway. I think a decent rule of thumb is that WASM modules should generally only be used in these kinds of off-the-event-loop types of worker threads.
(See https://linuxontheweb.github.io/ for my implementation of a new kind of web application platform where these kinds of ideas can start becoming a reality.)
I'd love to start working with anyone who wants to turn the web into a solid platform for application development with Linux on the Web. It has been over a decade in the making, and is starting to become quite stable. It is almost entirely written in Javascript. Try it online at https://linuxontheweb.github.io/. The github repo is https://github.com/linuxontheweb/linuxontheweb.github.io
Well, although I certainly can get enjoyment through never-ending hours of coding, I am mainly doing this project to get something to actually work.
I would tend to look at this project as an implementation rather than an emulation.
The current implementation of the shell is certainly in a highly bare bones state, but that can definitely change over time if that is in fact where the development process leads. If it gets to the point of being able to quack like a POSIX shell, then who's to say that it isn't really one?
Well, there is technically no such thing as an "actual Linux system." There are mainly GNU/Linux systems. If one is using the word "Linux" from a high-level systems theoretical perspective, the they are speaking about a certain philosophy related to how they approach the question of performing general computations. So, it is from the "Unix philosophical" point of view that I use the word "Linux." This also seems to be the generally accepted way of using that word, because most people use it as a shorthand for something with much more cultural significance (i.e. the open source alternative to the Windows or Mac ecosystems) than the kinds of technical facts to which you are referring.
Everything is mainly just my own handcrafted Javascript. There is only one wasm module included so far (binjgb) to allow for the playing of gameboy games.
I've previously tried to implement all of those sorts of POSIX-isms, but I've recently been wanting to make the tradeoff where code simplicity and understandability trumps all other considerations. Then, when others start coming on board the project, we can start making determinations about what kinds of "proper" shell functions to support.
So, at this point, "bare yet dependable" is what I'm going for! You can actually get more feedback about the filesystem through the desktop interface. You can show an icon cursor by pressing the 'c' key, and then move it over a file icon. Then, just press the 'p' key to show the properties of the file.
Ahh... my two favorite tech-related subject matters: Linux distros and the politics of browser choice. I'm currently trying to invert this entire discussion by putting a well-oiled Linux distro inside of the browser [1].
[1] For whoever doubts that a proper Linux distro can be created through pure Javascript running in a browser, you obviously haven't tried out https://linuxontheweb.github.io/ yet!