4 ms·

This is sort of the boat I'm in now. I've been writing side-project widgets, and just putting them on my blog with commentary. I toyed around with Sourceforge o

This is sort of the boat I'm in now. I've been writing side-project widgets, and just putting them on my blog with commentary. I toyed around with Sourceforge over a decade ago, but just never latched onto it as a platform for publishing code. Recently I've been doing work on Github (same handle there as my HN handle, but I won't link to it here), and had to learn git. I don't test the same way traditional developers (whatever that means) do, so Karma, node, and the rest aren't high on my to-do list. Git and Github weren't hard to learn (in fact the hardest part was to learn what's idiomatic of a Github project), and I'm happily growing my project. I think in some ways I might be your target audience, however I don't immediately see the benefit of using this as an add-on to my project rather than the testing suite, et al. And were you thinking of changing the name? Or at least the logo? I think you're seriously asking for trouble from "the man" if you take a commercial logo and try to use it this way. [Edit - fixed 3rd grade grammar error]

williamcotton 13y ago
So let's say you're working on something and you're looking for a library that will help you out with canvas animations. You find a GitHub project, or a package on bower, and you get the code on to your local system somehow. You then have to wire it up in to your existing code somehow. Even if you just start with a new project to try out the API or something, you still have to do a decent amount of system management to get the thing working. Check out this fiddle: http://jsfiddle.net/williamcotton/fJ4Rv/ http://jsfiddle.net/williamcotton/fJ4Rv/ Instead of trying out a new lib you can easily just bring it to life anywhere with no system dependencies other than the lit library itself. The same ease of consuming code is present in publishing. The goal of lit is to reduce the friction and overhead present in publishing and consuming open-source code in the browser. It can also be used for bigger projects, like (and get out your iOS devices for this) nox: http://nox.neocities.org http://nox.neocities.org If you view the source you'll see it starts by loading this module: http://www.corslit.com/williamcotton/nox http://www.corslit.com/williamcotton/nox: Personally, I've been developing using JUST CorsLIT and the editing all code in-browser and doing the deploys using fully front-end sites like Neocities, JunoJS, and JSFiddle. My personal favorite is Neocities. :) As per the name, well, the actual product is lit, and CorsLIT is a site built on top of the lit API. I plan on retiring the CorsLIT site and developing the second generation site on top of the data and functionality offered by the core of the product. Hopefully the next version can stand on it's own two feet and won't require the song-and-dance to get some attention. :) The CorsLIT name itself was chosen for nothing more than being a funny marketing ploy! I would absolutely love it if it caused enough of a stir to warrant some very expensive lawyers sending me a letter! I'm also a genuine fan of shitty American light beers.

williamcotton 13y ago

So let's say you're working on something and you're looking for a library that will help you out with canvas animations. You find a GitHub project, or a package on bower, and you get the code on to your local system somehow. You then have to wire it up in to your existing code somehow. Even if you just start with a new project to try out the API or something, you still have to do a decent amount of system management to get the thing working. Check out this fiddle: http://jsfiddle.net/williamcotton/fJ4Rv/ http://jsfiddle.net/williamcotton/fJ4Rv/ Instead of trying out a new lib you can easily just bring it to life anywhere with no system dependencies other than the lit library itself. The same ease of consuming code is present in publishing. The goal of lit is to reduce the friction and overhead present in publishing and consuming open-source code in the browser. It can also be used for bigger projects, like (and get out your iOS devices for this) nox: http://nox.neocities.org http://nox.neocities.org If you view the source you'll see it starts by loading this module: http://www.corslit.com/williamcotton/nox http://www.corslit.com/williamcotton/nox: Personally, I've been developing using JUST CorsLIT and the editing all code in-browser and doing the deploys using fully front-end sites like Neocities, JunoJS, and JSFiddle. My personal favorite is Neocities. :) As per the name, well, the actual product is lit, and CorsLIT is a site built on top of the lit API. I plan on retiring the CorsLIT site and developing the second generation site on top of the data and functionality offered by the core of the product. Hopefully the next version can stand on it's own two feet and won't require the song-and-dance to get some attention. :) The CorsLIT name itself was chosen for nothing more than being a funny marketing ploy! I would absolutely love it if it caused enough of a stir to warrant some very expensive lawyers sending me a letter! I'm also a genuine fan of shitty American light beers.