41–49 of 49 posts
Interesting that google had this as an internal webpage. I wonder what other really useful tools companies use that could benefit us if it were public.
I can see the value in something like this, especially for more novice web developers who may not know the terms to search for in Google or StackOverflow to find what they need. I understand it's rough, but here are something of the things I was expecting to see while I was browsing around: - Some "category" pages, like dbm, are missing definitions. It would be great if definitions were present on every category page…
Thanks for all your suggestions, will follow up on the rest of the suggestions!
It might be a good idea to tag the age of articles because some may be complaints or has missing features that would get resolved. Also, no Source Control (Git/SVN/etc) or Configuration Control (Chef/Puppet/etc)?
Great. I'd suggest arranging the categories in a rough data flow, so webserver would be near the "outside" (top?), wsqi inside that, frameworks inside that. wsgi might become part of a larger cgi-ish category: app container? app connector? You'd include fcgi and the various php equivalents in there; maybe subcategories. Debatable: firewalls? Virtual environments like virtualenv and whatever the other guys use.
We have added environment managers as a category (virtualenv, rvm, rbenv, bundler)
Interesting idea. Suggestion: sort the categories at the top by how likely a project is to need/use them. Without getting into religious arguments, I think a fair example would be "language" and "webserver" should sort higher than "graph-store" and "mapreduce". Also might be a good idea to define the categories for newbies. Most of the categories will need explanation for newbies. Cool idea, though. I used to use jak…
Cool idea! Definitely makes research a lot easier! Any reason why CSS isn`t on the list of languages? My web stack in the past has included CSS pre-processers, like LESS and Sass.
Nice idea. Could you include an approximation of each components popularity or longevity? This would allow people to know if they are picking mainstream or more obscure/specialised/enterprise/unstable/etc components.
yeah. any ideas on how to measure this?
Interesting idea. Suggestion: sort the categories at the top by how likely a project is to need/use them. Without getting into religious arguments, I think a fair example would be "language" and "webserver" should sort higher than "graph-store" and "mapreduce". Also might be a good idea to define the categories for newbies. Most of the categories will need explanation for newbies. Cool idea, though. I used to use jak…
We have roughly sorted the categories from bottom to top stack order, let us know your feedback :)
- language
- sql
- webserver
- webframework
- sourcecontrol
...
- stuff most people don't use on their projects, like mapreduce and graph-store
Also, the tooltip definitions are helpful but it's not obvious that they are there. I only knew they were there because you said so here. :-)
Good luck!