31–40 of 49 posts
I noticed there is no Common Lisp or Scheme. Both are great languages for apps/web.
i should write up the file format so people who are so minded can just send me a file to upload.
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.
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?
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.
Also, no Source Control (Git/SVN/etc) or Configuration Control (Chef/Puppet/etc)?
Have you considered including a set of metrics which measure the maturity and status of each project? How about listing noteworthy uses in production? Also, recency and quantity of commits, bug fixes etc.
If things go wrong (and they invariably do), I can sleep safer at night knowing that there is a thriving community behind the project, which can provide guidance on any issues.
Admittedly what I have suggested presents some UI difficulties, at least on the home page. It would also need to be updated quite frequently. That could be partially automated by pinging public version control servers, for instance.
Still, a great job. Looking forward to seeing how it progresses.
Also, you could avoid the spatial UI problems nesting may cause if there's a tooltip with meta data & links on rollover.