3 ms·

So I can develop offline using nothing more than a browser. I clone a repo from github to my browser when I'm online. Then I'm offline in a bus or on a plane,

So I can develop offline using nothing more than a browser. I clone a repo from github to my browser when I'm online. Then I'm offline in a bus or on a plane, but I can still work because browsers have file storage now. When I'm done working, I can go online and push my changes back to github. And all this will work anywhere that has a browser, ChromeBook, Surface RT, iPad, etc.. Obviously, it's mostly of use to web developers since JS is the only runtime, but I also have other later projects attacking that problem. But for now, JS only is a pretty big market.

nicholassmith 14y ago
Hey, thanks for the reply! Couple of things, repos can get pretty big, how are you planning on storing things? Using the HTML5 storage? Kicking it down the drive? If it's with HTML5 storage after that guy found a work around allowing sites to completely burn through a drive browser devs might start putting a cap onto the limit of storage that you can use. I don't know, I'm a big fan of getting tools to everyone, but I'm still wondering if this sounds like a great idea, without actually being a great idea. EDIT: that last line might be a little overly harsh looking back on it, it's not that I don't think it's a good idea (definitely is!) but I'm wondering if it's a great idea that's worthy of a Kickstarter.
- creationix 14y ago
  Like I said, my main use case is mine. I want to develop on my new ChromeBook Pixel (if it ever gets here) without being forced to use an Ubuntu chroot. Packaged apps have much larger size quotas and most my code repos are small anyway. As far as the education aspect, I have future plans to create a new programming language aimed at learning to program that compiles to javascript. Combined with a proper in-browser IDE, this would allow any kid to learn to program on any machine that has a browser. It obviously won't replace native dev tools, but it will make web-based stuff a whole lot more powerful and that's something I and many others feel is worth paying for.
  - nicholassmith 14y ago
    You know what, more power to you. It doesn't fit a use-case for me, but damn do I love seeing tools made more accessible. Although I'm really interested in hearing about how you're going to port the incredibly 'Linus' C code into Javascript, there's a huge amount going on and it's often not, well, that awesome to read.

nicholassmith 14y ago

Hey, thanks for the reply! Couple of things, repos can get pretty big, how are you planning on storing things? Using the HTML5 storage? Kicking it down the drive? If it's with HTML5 storage after that guy found a work around allowing sites to completely burn through a drive browser devs might start putting a cap onto the limit of storage that you can use. I don't know, I'm a big fan of getting tools to everyone, but I'm still wondering if this sounds like a great idea, without actually being a great idea. EDIT: that last line might be a little overly harsh looking back on it, it's not that I don't think it's a good idea (definitely is!) but I'm wondering if it's a great idea that's worthy of a Kickstarter.

creationix 14y ago
Like I said, my main use case is mine. I want to develop on my new ChromeBook Pixel (if it ever gets here) without being forced to use an Ubuntu chroot. Packaged apps have much larger size quotas and most my code repos are small anyway. As far as the education aspect, I have future plans to create a new programming language aimed at learning to program that compiles to javascript. Combined with a proper in-browser IDE, this would allow any kid to learn to program on any machine that has a browser. It obviously won't replace native dev tools, but it will make web-based stuff a whole lot more powerful and that's something I and many others feel is worth paying for.
- nicholassmith 14y ago
  You know what, more power to you. It doesn't fit a use-case for me, but damn do I love seeing tools made more accessible. Although I'm really interested in hearing about how you're going to port the incredibly 'Linus' C code into Javascript, there's a huge amount going on and it's often not, well, that awesome to read.