pocl VS isomorphic-git

https://github.com/avodonosov/pocl

The unused javascript code can be removed (and loaded on demand). Although I am not sure how valuable that would be for the world. It only saves network traffic, parsing time and some browser memory for compiled code. But js traffic in the Internet is neglidgible comparing to, say, video and images. Will the user experience be signifiqanty better if browser is the saved from the unnesessary js parsing? I don't know of a good way to measure that.

> for such a small piece of work

Don't take the example too literally, some functions calls can be here.

Running computations in parallel is often valuable. Or run computations in parallel with waiting for external resource - why does not the code in the article compute something while waiting for a, b and c?

Anyways, if async functions are so good, why not have all functions async?

The article says this a kind of "documentation" that tells you what functions can wait for some external data and what functions are "pure computation". If it was so, it would be OK. Such a documentation could be computed automatically based on the called function implementations and developer is hinted: "these two functions you call are both async, consider waiting for both in parallel". In reality, the async / await implementations prevent the non-async functions from becoming async without code change and rebuild. This restriction is just a limitation of how async / await is implemented, not something useful.

As other commenter says, the article "embraces a defect introduced for BC reasons as if it's sound engineering. It really isn't."

When my code is called by a 3rd party library, I can not change my code to async. That's the most unpleasant property of today's async / await. What yesterday was quick computation tomorrow can become a network call. For example, I may want to bodies of rarely used functions to only load when called first time (https://github.com/avodonosov/pocl).

The article suggest we have to decide upfront, at the top-level of the application / call stack, which parts can be implemented with as waiting blocks and which should never wait for anything external. This is not practical.

> It's almost always faster to do them in parallel if possible.

A microcosm of the wasm issue was captured in this thread about implementing a web based git in JavaScript from scratch vs. compiling libgit

https://github.com/isomorphic-git/isomorphic-git/issues/268

I think one big missing part still with static sites is how you host the CMS to edit it.

Correct me if I'm wrong but Decap CMS (previously Netlify CMS) runs in the browser and makes reads/edits via GitHub which can then trigger rebuilds and deploys, but it still needs a small server/proxy I think because CORS stops your browser communicating directly with the GitHub API. Netlify hosts a GitHub backend that proxies requests for you but now you're tied to Netlify.

GitLab and BitBucket will have the same issue I think: https://github.com/isomorphic-git/isomorphic-git#cors-suppor...

Is there a simple solution here with minimal configuration?

ssh isn't supported on mobile for technical reasons

This article is an attempt to classify knowledge about using git in a nodejs environment. Particularly, this is going to tell about isomorphic-git library and how to implement it in web applications.

I recently had to implement git cloning into a full stack project and I found a very useful library OP can use. isomorphic-git which would solve this issue and allow them to clone into a virtual filesystem which can help save speed, storage, and possibly keep it secure. Plus if the memfs package is used the OP can just dumb the JSON of the Volume object into the request.

I always wanted to make a command line interface/prompt but didn't actually start it till a few months ago. I decided to go with Xterm.js for the basic terminal interface along with a modified local-echo to add basic required functionality. Then I set about duplicating every command I could find. I was able to link the terminal directly to the file system so all commands show real information. You can run help to view all commands/aliases. I've also included things such as Git, Python & Wapm.io support.