3 ms·

Mozilla seems to really want this.

• goldfeld 13y ago
  I can completely see why Adobe (Edge Code/Brackets) and Mozilla want this. It's a missing piece for coding completely in the browser. But I think it goes way beyond this, and once people start playing around with having git sandboxed inside the browser we're gonna see some really, really interesting ideas come out of it. I was sad that his second funding wasn't seemingly headed for success, and it's pretty awesome Mozilla laid down $25k to revert that.
  • Jonovono 13y ago
    What are some interesting ideas you can think of that could come out of this?
    • shawndumas 13y ago
      from the site: ChromeOS IDE for developing on Chromebooks. Node.JS blog engine with git as the database. Custom Git hosting using custom storage back-ends. GIT CLI for restricted environments. Standalone GIT GUI desktop app. Git based deployment tools. JavaScript package management for server and client. Whatever else you come up with.
      • reflectiv 13y ago
        As a guy that works for one of the major banks in the US as a developer...the restrictions placed on even our development boxes is rediculous...HOWEVER they don't seem to give two craps about javascript...so this would be a GREAT capability for me to have and extend my workstations capabilities in a myriad of ways... I can't wait for this! I might have to try and contribute if I can actually...
    • bergie 13y ago
      We're also very interested in having this for http://noflojs.org/ http://noflojs.org/. Our current git components just run the CLI version, but obviously pure JS library would give us more control.