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!
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?
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.
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.
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!
Did you happen to notice the link at the bottom of the page to this article?
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!