0
1

[–] jsprogrammer [S] 0 points 1 point (+1|-0) ago 

I don't necessarily agree with that definition. Some projects just work and don't need further code at the moment. Others are just experiments.

Maintenance and premature project selection are huge problems. Taking a path necessitates not taking others. I want to get a large view of the landscape, develop ideas, and then execute on the best. If you buckle in to the first project you start, you run a huge risk of myopia. I have been able to move many projects forward this way and now have a large stockpile to draw from. Many of the most important projects are on the verge of public usability, but I have held off so as not to be swamped by having to support something I am not ready to.

0
1

[–] WhiteRonin 0 points 1 point (+1|-0) ago 

Sorry for being so blunt but I was thinking that since you put yourself out there with this thread you deserve honest as possible responses.

Yes, some projects can be mature enough to not need any new commits. I use several js scripts that have had updates to the core code.

You know better than I how fast js is progressing. So, in this respect, having the read me reflect that helps.

I agree about moving too fast. Build and deploy without thought is one of my pet peeves. However, the opposite also exist that you never build or get building and don't deploy. Both sides of this can be evil and detrimental.

I also get the idea of experimenting or building out several different projects to not use them until way later or possibly never.

I'm seeing your idea as a stage 1 candidate for a code-athon or pound it out using a framework over the weekend. This stage 1 would get you up to user auth/athen and basic basic functionality. I already posted early the stages your app would most likely progress through. So why are you worried about investing your life into unless you really don't like the idea?

Deploy stage 1 and see the response of people. Drop Box released a mocked up video before even really working on code.

If stage 1 never gains ground you shut down the site or pass it off to a loyalist. If you keep the source code on but hub people might post pulls or even build it out. However, waiting for a team or even another developer most likely means the project will stay dormant.

0
1

[–] jsprogrammer [S] 0 points 1 point (+1|-0) ago 

Thank you for your honesty, I do appreciate it.

JS does have issues and some things will eventually likely need to be modified slightly to support new environments, however I generally tried to be careful to keep what will need to change from what might not. The biggest thing here in the last several years has been ES6/7/8/2015/2016 and needing to use transpilers and file packers. Those are basically just build steps in my projects, so they can basically just be omitted when they are no longer needed.

I'm actually not even considering user auth right now. I'm going to get up a completely un-walled site fronted by CloudFlare and backed by GitHub hosted sites. I'm going to load an initial database with links to Trump and Clinton videos. The database will be json files that can be updated by pushing to GH.