Would love to see it as a map/graph, where parts that "go together" (or are often used together) being linked. It'd probably be tricky to find the right threshold, but the result would be really useful (and fun to see).
Show HN: Stack Parts - a way to find possible parts for your stack
21–30 of 49 posts
Re: Show HN: Stack Parts - a way to find possible parts for your stack
#22Would love to see it as a map/graph, where parts that "go together" (or are often used together) being linked. It'd probably be tricky to find the right threshold, but the result would be really useful (and fun to see).
gotcha, will add that to the todos.
Re: Show HN: Stack Parts - a way to find possible parts for your stack
#23What I would be more interested is interconnectivity between these elements of the stack, which rdbms have an API for the language I have selected for example.
we have some of that.
eg:
connects python to mongo?
we're not sure what to tag these as. bindings?
Re: Show HN: Stack Parts - a way to find possible parts for your stack
#24Interesting 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…
good idea.
Re: Show HN: Stack Parts - a way to find possible parts for your stack
#25Add cherokee under webserver. Lovely configuration, fast, flexible.
submitted the form. hasn't showed up on the homepage yet.
Re: Show HN: Stack Parts - a way to find possible parts for your stack
#26Add cherokee under webserver. Lovely configuration, fast, flexible.
submitted the form. hasn't showed up on the homepage yet.
doesn't happen automatically. we have a bunch of work to do to make that happen. just goes to google docs for now.
the implementation is the absolutely simplest we could come up with.
Re: Show HN: Stack Parts - a way to find possible parts for your stack
#27Earlier quoted context omitted.
submitted the form. hasn't showed up on the homepage yet.
doesn't happen automatically. we have a bunch of work to do to make that happen. just goes to google docs for now. the implementation is the absolutely simplest we could come up with.
understood :) just putting it out there in an attempt to avoid dupes.
thanks joshua!
Re: Show HN: Stack Parts - a way to find possible parts for your stack
#28I noticed there is no Common Lisp or Scheme. Both are great languages for apps/web.
Re: Show HN: Stack Parts - a way to find possible parts for your stack
#29Nice 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.
Re: Show HN: Stack Parts - a way to find possible parts for your stack
#30I maintain something like this personally, in the form of private structured notes, and I know other engineers that do as well. Except we go beyond listing all possible things that can fit into a given category, into instead making quality and suitability judgments about them. What's "best" or the no-brainer/default for a given role, either in the general case or in various special cases. It's a very useful professio…
I like that page, thank you for setting it up. Now I wonder what the 'rest of us' are using, it would be great to see this same list with a larger number of people and what their reasons for picking one technology over another in the same segment are.
That could probably ignite the flamewar thread of the century.