There is a paper linked on Wikipedia stating that studies conducted in Germany showed that "Water fluoridation was followed by a decrease of caries, and interruptions in fluoridation were followed by increasing caries levels." but also "There was a significant caries decrease down to the lowest DMFT (2.0) since 1959 in spite of the fact that only F-poor water was available over years [...] explained by changes in caries-preventive and environmental conditions."
If I have a specific task the workflow for me looks like that: 1. Search through Google, Github, Unheap, npm, bower, jster and so on. 2. Compile a list of useful packages and tutorials for every one of them. 3. Select the best package for the task.
So I created this list to not have to go through step #1 and #2 every time.
Exactly, something like that. I think nowadays we have enough little projects to choose from, so we can create a distribution with central package management and plugin architecture (based on npm?) and a list of curated packages + documentation/tutorials on how to tie everything together. So for example there could be bootstrap + angular + express.js on node + mongodb + debian. Building + testing + deployment infrastructure should come out of the box.
Meteor is trying to create something like this, but I feel the focus should be more to integrate community projects (they say they do, but in reality they don't), not building everything from the scratch.
What project details would you like to see for each item on the list?
It's tough because :
1. There is a lack in uniformity: you have CSS solutions, jQuery extensions, node.js packages, articles, books, videos and so on.
2. Every bit of information you include makes the list bloated. I think it's enough to have the category, a link, and maybe a short description. If I need a template engine for a project, I will click on every link and look through them anyway.
Please make a suggestion how you would like this list to look.
If you are coming from the microsoft world you will have lots of surprises until you realize that the open source world (the unix philosophy) is completely different. You have lots of small tools which are designed to work together and be replaceable, not a huge monolithic product curated by a single entity.
The idea was to have a list of somewhat high quality resources out there. It's not a complete stack you can install and use out of the box (like debian). You still have to do the work and choose what's right for your project.
If you think something is missing, please send a pull request.
I think you are absolutely right, we are now ready to build a "debian for web development". We have lot's of high quality little packages we can unite under one well tested system.
https://onlinelibrary.wiley.com/doi/abs/10.1034/j.1600-0528....