I want to start radically experimenting with the entire concept of hotkeys in Linux on the Web[1]. It's just that I've been a one-man operation since I started working on it over 6 years ago, so it takes awhile to get any one thing done. Since the system is now coming into its own, I will be spending more time on HN, trying to build interest in what seems to be a potentially exciting new paradigm that blends together the ideas of traditional general computation and more modern, highly portable web-based approaches.
I have a similar kind of functionality in Linux on the Web, but dealing with parsing wasm (web assembly) files. There is a desktop environment, but I think it is best to use the shell environment at https://linuxontheweb.org/shell.os.
First, do this:
$ cp /site/root/system/wasms/games/binjgb.wasm .
The system is built around the concept of command libraries. You are going to need to import the wasm library like this:
$ import wasm
This loads a fairly powerful command called parsewasm.
To get an informational printout of the toplevel sections in that file, run the command:
$ parsewasm --toplevel binjgb.wasm
There are lots of other subcommands in parsewasm, but the coolest part is that you can list out the names of exported functions and then dump out the code bodies of whatever functions you want to inspect.
The problem with this starts with the word "we". How do, for lack of a better word, "we" get some kind of authentic sense of we-ness going in this modern age of increasing social atomization? Here's how I do it... when I'm not busy hacking away on the next generation of (potentially planet saving) general computation[1], I am performing my solemn duties in the real world as "the peace guy"[2].
I hate the concept of money. It needs to die a painful death. Business-as-usual is killing the planet and all future generations. Starting up a planet-saving model of business-as-unusual is why I started hacking on "Linux on the Web" [1] over 6 years ago. It is now quietly starting to take over. I think we all knew Linux was going to eventually do that anyway.
I guess the reason why I started working on what is now called "Linux on the Web" [1] was to exactly counter all of these existential issues that professional developers tend to face. I've never programmed for money.
IMO, the desktop environment in "Linux on the Web" [1] is a very sexy usage of modern web standards (including some non-standard stuff like the Chrome-only HTML5 FileSystem API)
> put some text and images online where people can see it.
I agree with this sentiment. My "backend view" [2] is just for things like that.
That's kinda funny when you consider where Mozilla came from... the ashes of a thing called Netscape... who tried to rule the world while a couple grad students were busy plugging away at Stanford, doing it the right way.
No. He (or she) is saying that he (or she) has finally found "Linux on the Web", and he (or she) has seen the light.
Seriously though... my baby is starting to come alive. I've been banging away on it since 2012. The above phrase should allow you to find it if you know about modern search practices :)
We can start putting ML frameworks galore in LOTW, and have it all start being in service of the people.
Or how about this... a return to GOFP (Good Ol' Frickin' Programming)... possibly using numbered lines and goto statements, like we did back in the day, copying fun little snippets into the old TRS-80!
(LOTW is a new kind of client side paradigm. Actually, it is a return to the same old paradigm of something I would call "immediate mode programming", where all of the resources are simply right there in front of you. There is just a little bit of help from our friends who build and maintain the back-end infrastructure to allow all of the resources to get conveniently shipped in.)
This and this, to the last two sentences. "Linux on the Web" (my baby) will be taking over in short order to rectify the situation (see my recent post history for more info). Been joyously hacking away on it almost nonstop since 2012. I've never felt a need or desire to work for anybody. That's all I do (when I'm not doing that thing I do when I'm out on the town).
Hi, yes, that stuff is from quite awhile ago, seeing that NaCl/PNaCl is quite dead, and WASM is now all the rage. I previously had actual vim running via NaCl, but the current (better IMO) version is just a fairly small JS clone (about 70kb). The whole system is rapidly stabilizing right now, what with the entire gui framework being fleshed out, both conceptually and technically.
I try to stay away from the above kinds of sweeping generalizations about the whole thing nowadays. It is best to let it speak for itself and evolve in its own good time.
Did you try the "desk.os" link that is link number 3 on that page... https://linuxontheweb.appspot.com/desk.os ?
I can really only guarantee that things work on a relatively recent version of Chrome (like within the last few stable releases). The version that is live now is a couple weeks old. I'm working on some really cool features for the modular synth app right now. I'd love to start sharing this stuff with you guys!
Also, link number 5, at https://linuxontheweb.appspot.com/shell.os is for people who just want to poke around the deep system internals via a command line. For that, you need to use the "import" command in order to pull in libraries of commands. For instance, running a command like:
I started building something I like to call "Linux on the Web" (LOTW) 6+ years ago in order to start working on this problem (it's live on the web right now). Just like with node.js applications, the smallest legal file size for an app running inside of LOTW is precisely 0 bytes. I've tried to shave that down even more, but I seem to be running into physical limits :)
I experienced a kind of dyslexia when reading this headline. I couldn't fathom what a C framework could have to do with a "web application" outside of the world of web assembly, so I wondered why the phrases "web assembly" or "wasm" were nowhere to be found. FWIW, I spend almost all of my working hours immersed in the logic of the client side!
My Linux Distro of choice is a random <$300 Chromebook in developer mode with crouton installed... it always works like a charm for my CLI-centric use cases.
Edit: Whenever Linus talks about the possibility of "the year of the Linux desktop" nowadays, it seems like he always brings up ChromeOS as the most likely contender.
"Energy technology" is a contradiction in terms. Energy (as we know it) comes from undifferentiated organic matter that is easy to burn while technology (as we know it) is based on the novel kinds of arrangements that can arise out of inorganic kinds of materials like metal and silicon.
The point is that better technologies rely on the burning of lower amounts (calories or joules) of energy.
There is irony here. The notion of a tech sector is entirely an equal and opposite reaction against actual Malthusian Traps (exponential population growth vs linear food supply growth) that are caused by depleting resource bases. See "The Limits to Growth", a 1972 MIT study by Meadows et al., funded by The Club of Rome.