4 ms·

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 b

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...

JustSomeNobody 8y ago
> ... but there is chance it will be found... Doesn't this completely ignore YAGNI?
- andai 8y ago
  It does, but so does almost all of mathematics :)
- steveklabnik 8y ago
  It's often true that you're not gonna need fun, but that's not really the relevant metric. That is, not every bit of software is created for business purposes, or with good software engineering principles, or anything else. Sometimes, you do things just because you can. Some might even call this "the hacker spirit".
- krapp 8y ago
  We do what we must because we can.
greggyb 8y ago
> (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 storage options. Now you can put git directly in browser, too. Heck, you could make a SPA and save the whole source as a file on your cloud storage - just open that up in any browser and access other files in that account (or others). Don't even carry a USB around, and still have your custom dev environment on any PC.
- komali2 8y ago
  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.
  - minieggs 8y ago
    Heck, that sounds like a fun gig.
    - deleted 8y ago
      [deleted]
bartread 8y ago
> even though meaningful use case is yet to be shown, but there is chance it will be found I don't get the Rust-port-hate, but I think you nailed the JS case with this comment. A few years ago my immediate reaction to JavaScript ports (or equivalents) used to be something roughly akin to, "what the eff is the point of that?!?" Still, enough times now I've found myself needing one of these things later on - the most recent example being something that can play Amiga mod files in a browser - that I've become a bit more broad-minded. Plus, of course these things can be fun learning exercises and, after all, why not? Really, one of the most canonical examples, for me, has to be Google Docs, which is basically a cut-down Microsoft Office in a browser. Back in the day I thought this was a terrible idea but, you know what? I've used Google Docs quite a lot over the past few years. It's still hasn't replaced MS Office, and probably never will because (as far as I can see) Excel simply can't be beat. Our main current Google Docs use case is running retros. We have a few remote team members, plus a fairly strong WFH culture, so a shared GDocs drawing makes a great canvas/virtual whiteboard. Granted it's not as good as a dedicated virtual whiteboard app, but it's a very cost effective way of giving everyone write access to a shared drawing/post-it surface on an occasional/periodic basis. The problem with virtual whiteboards is they tend to charge per user, which makes sense if everyone uses them all the time, but becomes cost prohibitive when most people only need the app once every couple of weeks. There are also plenty of examples for me that still don't seem to make much sense (online IDEs) but, whatever, some people clearly do, and that's cool.
Boulth 8y ago
> (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.
Ajedi32 8y ago
> even though meaningful use case is yet to be shown There are two existing use cases listed in the README: https://github.com/isomorphic-git/isomorphic-git#who-is-using-isomorphic-git https://github.com/isomorphic-git/isomorphic-git#who-is-usin...

JustSomeNobody 8y ago

> ... but there is chance it will be found... Doesn't this completely ignore YAGNI?

andai 8y ago
It does, but so does almost all of mathematics :)
steveklabnik 8y ago
It's often true that you're not gonna need fun, but that's not really the relevant metric. That is, not every bit of software is created for business purposes, or with good software engineering principles, or anything else. Sometimes, you do things just because you can. Some might even call this "the hacker spirit".
krapp 8y ago
We do what we must because we can.

greggyb 8y ago

> (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 storage options. Now you can put git directly in browser, too. Heck, you could make a SPA and save the whole source as a file on your cloud storage - just open that up in any browser and access other files in that account (or others). Don't even carry a USB around, and still have your custom dev environment on any PC.

komali2 8y ago
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.
- minieggs 8y ago
  Heck, that sounds like a fun gig.
  - deleted 8y ago
    [deleted]

bartread 8y ago

> even though meaningful use case is yet to be shown, but there is chance it will be found I don't get the Rust-port-hate, but I think you nailed the JS case with this comment. A few years ago my immediate reaction to JavaScript ports (or equivalents) used to be something roughly akin to, "what the eff is the point of that?!?" Still, enough times now I've found myself needing one of these things later on - the most recent example being something that can play Amiga mod files in a browser - that I've become a bit more broad-minded. Plus, of course these things can be fun learning exercises and, after all, why not? Really, one of the most canonical examples, for me, has to be Google Docs, which is basically a cut-down Microsoft Office in a browser. Back in the day I thought this was a terrible idea but, you know what? I've used Google Docs quite a lot over the past few years. It's still hasn't replaced MS Office, and probably never will because (as far as I can see) Excel simply can't be beat. Our main current Google Docs use case is running retros. We have a few remote team members, plus a fairly strong WFH culture, so a shared GDocs drawing makes a great canvas/virtual whiteboard. Granted it's not as good as a dedicated virtual whiteboard app, but it's a very cost effective way of giving everyone write access to a shared drawing/post-it surface on an occasional/periodic basis. The problem with virtual whiteboards is they tend to charge per user, which makes sense if everyone uses them all the time, but becomes cost prohibitive when most people only need the app once every couple of weeks. There are also plenty of examples for me that still don't seem to make much sense (online IDEs) but, whatever, some people clearly do, and that's cool.

Boulth 8y ago

> (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.

Ajedi32 8y ago

> even though meaningful use case is yet to be shown There are two existing use cases listed in the README: https://github.com/isomorphic-git/isomorphic-git#who-is-using-isomorphic-git https://github.com/isomorphic-git/isomorphic-git#who-is-usin...