4 ms·

Really great way to present a new tool, congrats! However, I still don't know what exactly is this tool supposed to do :( Care to explain a bit more? (Just for

by mweibel 13y ago

Really great way to present a new tool, congrats! However, I still don't know what exactly is this tool supposed to do :( Care to explain a bit more? (Just for the record: I know bower, npm, requirejs etc.)

shortstuffsushi 13y ago
I was about to reply exactly the same way. I'm well aware of the pain of trying to 'prettily' share things you've created (all the configs, etc for very little code), but I'm not really getting what this is doing to resolve that? The demonstration video actually confused me more than the lead up textual explanation. Which is by no means saying I don't like the idea. I agree it's a problem, but how are you solving it?
- williamcotton 13y ago
  One thing I'm just now realizing is that I'm not very good at making screencasts! Did you happen to notice the link at the bottom of the page to this article? http://williamcotton.com/another-way-to-publish-code http://williamcotton.com/another-way-to-publish-code I'm thinking I might need to move a lot of elements from that article to the front-page of CorsLIT! If you did read the follow-up article, I apologize for not being able to present a clear explanation of how lit attempts to solve the problems presented in the original article! I'm also realizing that I should make a longer form screencast, say about 5 minutes in length, that shows how I use lit on a daily basis to build applications while sharing as much modular code as I can, with as little friction as possible!
  - neon_electro 13y ago
    I too didn't really understand what Lit/CorsLIT is supposed to do, but your writing and awesome marketing did get me excited. Definitely interested in a longer article or screencast!
  - mweibel 13y ago
    The article I didn't really see (actually I saw the link but thought it goes back to the introductionary article, didn't read properly enough). I got now a better understanding at what you're trying to solve. What I didn't quite get yet is: How is this supposed to help regarding bower/npm json files? Or am I on the wrong track here?
    - williamcotton 13y ago
      Dude, no worries, I've realized I didn't do the best job of presenting the information or highlighting that link. You were not alone in your confusion, haha. My ultimate goal is to not have to use server-side tools for managing front-end dependencies. I would like to leave bower and npm out of it completely. Making node or any other full language stack a dependency for front-end development is the wrong way to go about it, in my opinion. There's just too much friction between filesystems and the browser.
  - shortstuffsushi 13y ago
    Sorry for not replying, I never keep up with my comments on here. I did see the article, and that helped a bit. Again, not trying to bash it -- seems like a great idea, and I'll definitely be keeping an eye on it.

by mweibel 13y ago

shortstuffsushi 13y ago

I was about to reply exactly the same way. I'm well aware of the pain of trying to 'prettily' share things you've created (all the configs, etc for very little code), but I'm not really getting what this is doing to resolve that? The demonstration video actually confused me more than the lead up textual explanation. Which is by no means saying I don't like the idea. I agree it's a problem, but how are you solving it?

williamcotton 13y ago
One thing I'm just now realizing is that I'm not very good at making screencasts! Did you happen to notice the link at the bottom of the page to this article? http://williamcotton.com/another-way-to-publish-code http://williamcotton.com/another-way-to-publish-code I'm thinking I might need to move a lot of elements from that article to the front-page of CorsLIT! If you did read the follow-up article, I apologize for not being able to present a clear explanation of how lit attempts to solve the problems presented in the original article! I'm also realizing that I should make a longer form screencast, say about 5 minutes in length, that shows how I use lit on a daily basis to build applications while sharing as much modular code as I can, with as little friction as possible!
- neon_electro 13y ago
  I too didn't really understand what Lit/CorsLIT is supposed to do, but your writing and awesome marketing did get me excited. Definitely interested in a longer article or screencast!
- mweibel 13y ago
  The article I didn't really see (actually I saw the link but thought it goes back to the introductionary article, didn't read properly enough). I got now a better understanding at what you're trying to solve. What I didn't quite get yet is: How is this supposed to help regarding bower/npm json files? Or am I on the wrong track here?
  - williamcotton 13y ago
    Dude, no worries, I've realized I didn't do the best job of presenting the information or highlighting that link. You were not alone in your confusion, haha. My ultimate goal is to not have to use server-side tools for managing front-end dependencies. I would like to leave bower and npm out of it completely. Making node or any other full language stack a dependency for front-end development is the wrong way to go about it, in my opinion. There's just too much friction between filesystems and the browser.
- shortstuffsushi 13y ago
  Sorry for not replying, I never keep up with my comments on here. I did see the article, and that helped a bit. Again, not trying to bash it -- seems like a great idea, and I'll definitely be keeping an eye on it.