A few years back, the company I’m currently at started working on NodeGit because a pure JavaScript implementation they tried (not this one? Idk I wasn’t there) was far too slow. Right now, we’re working on a git server in rust that takes commands and passes data over TCP that ideally could enable git usage in the browser for like hosted development environments and such.
A pure JavaScript implementation of Git for Node and browsers
61–70 of 203 posts
Re: A pure JavaScript implementation of Git for Node and browsers
#62I think it's interesting how there's two phenomena that seem to be related to me that get posted here and seem to get treated with different responses. One the one hand, we have software originally written in C/C++ being rewritten in Rust (not often, sometimes just conceptualized), and there's often a real push back by some people about how it's a waste and not useful. On the other, we have software rewritten in Java…
Arsene Wenger put it quite well recently:
"Once you are not a danger any more, people love you."
Re: A pure JavaScript implementation of Git for Node and browsers
#63With something like this, GitHub will soon become my web app’s database (pending that PR). So awesome...
Re: A pure JavaScript implementation of Git for Node and browsers
#64I think it's interesting how there's two phenomena that seem to be related to me that get posted here and seem to get treated with different responses. One the one hand, we have software originally written in C/C++ being rewritten in Rust (not often, sometimes just conceptualized), and there's often a real push back by some people about how it's a waste and not useful. On the other, we have software rewritten in Java…
Understand your frustration. But on positive hand, javascript opens new opportunities like using git in the browser (even though meaningful use case is yet to be shown, but there is chance it will be found). On other hand rust implementation brings "just better security" (using sarcasm here for brevity). Yes, it probably could be ported to js (wasm) too, but until somebody does that...
> (even though meaningful use case is yet to be shown, but there is chance it will be found)
One use case is having a repository UI completely in a browser so the backend can be a pure git server with no specialized backend code to display commits, blobs etc.
This way a browser becomes just another git client.
Re: A pure JavaScript implementation of Git for Node and browsers
#65I think it's interesting how there's two phenomena that seem to be related to me that get posted here and seem to get treated with different responses. One the one hand, we have software originally written in C/C++ being rewritten in Rust (not often, sometimes just conceptualized), and there's often a real push back by some people about how it's a waste and not useful. On the other, we have software rewritten in Java…
Arsene Wenger put it quite well recently: "Once you are not a danger any more, people love you."
Maybe it should be, "Once you are not in danger any more, you love people."
Re: A pure JavaScript implementation of Git for Node and browsers
#66I think it's interesting how there's two phenomena that seem to be related to me that get posted here and seem to get treated with different responses. One the one hand, we have software originally written in C/C++ being rewritten in Rust (not often, sometimes just conceptualized), and there's often a real push back by some people about how it's a waste and not useful. On the other, we have software rewritten in Java…
Re: A pure JavaScript implementation of Git for Node and browsers
#67I think it's interesting how there's two phenomena that seem to be related to me that get posted here and seem to get treated with different responses. One the one hand, we have software originally written in C/C++ being rewritten in Rust (not often, sometimes just conceptualized), and there's often a real push back by some people about how it's a waste and not useful. On the other, we have software rewritten in Java…
IMO, this is because there's a general attitude about porting to Rust that porting to Rust, by itself, makes a material improvement in the quality of the software (e.g. reliability, performance, readability), and that these improvements that can't be achieved in C/C++. Entrenched C developers then rise to the debate to defend their language. This debate has happened often enough that any time someone ports something…
The only attack I feel is calling C/C++ a language. It's two languages and we don't like each other very much. People who spend a lot of time trying to write good C++ avoid much of C's bread and butter like malloc and free, and the general hatred of C++ from C developers is well-documented.
I happen to prefer C++ to C and D to both.
Re: A pure JavaScript implementation of Git for Node and browsers
#68Earlier quoted context omitted.
> (even though meaningful use case is yet to be shown, but there is chance it will be found) A thought is a browser-based IDE, with a cloud filestore (OneDrive, Dropbox, Google One/Drive (my new preferred stylization of their product)) for repo and dev environment. Think of it like a browser-ified version of what you might do with a server and SSH. We've got a couple JS-based editors/IDEs. We've got many cloud storag…
I'm on a team whose primary project is a browser-based IDE. We are considering this for exactly the reason you said. Probably won't implement it because the whole "choose your own FS, also it doesn't work on github" thing, but we might plug it into our node server and writeup an API for our client to use.
Heck, that sounds like a fun gig.
Re: A pure JavaScript implementation of Git for Node and browsers
#69Earlier quoted context omitted.
I'm on a team whose primary project is a browser-based IDE. We are considering this for exactly the reason you said. Probably won't implement it because the whole "choose your own FS, also it doesn't work on github" thing, but we might plug it into our node server and writeup an API for our client to use.
Heck, that sounds like a fun gig.
[deleted]
Re: A pure JavaScript implementation of Git for Node and browsers
#70I think it's interesting how there's two phenomena that seem to be related to me that get posted here and seem to get treated with different responses. One the one hand, we have software originally written in C/C++ being rewritten in Rust (not often, sometimes just conceptualized), and there's often a real push back by some people about how it's a waste and not useful. On the other, we have software rewritten in Java…
Arsene Wenger put it quite well recently: "Once you are not a danger any more, people love you."
or this: "once you don't look as if you are in danger all the time, people love you"