<div><span style="color: rgb(160, 160, 168);">On Friday, 20 February 2015 at 14:39, e@bestmx.net wrote:</span></div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><blockquote type="cite"><div><blockquote type="cite"><div><div>yaws or mochiweb?</div><div>mnesia or mongoDB?</div><div>chicago boss or ...?</div><div>XML or JSon?</div><div>intellij idea or eclipse?</div><div>and before i buy a server, Win or Linux or ...?</div></div></blockquote><div><br></div><div>If I had freedom of choice and problem notwithstanding:</div><div><br></div><div>Webmachine or Cowboy for the web server. Proper RESTful approaches are too</div><div>good to leave up.</div></div></blockquote><div><br></div><div>if it is "Webmachine or Cowboy?"</div><div>then, no doubt, Cowboy.</div><div><br></div><div>i was using both, and it is clear to me that webmachine loses every </div><div>comparison.</div><div><br></div><div><br></div><blockquote type="cite"><div><div>Postgresql for smaller databases (up to 5-10 terabytes in size roughly).</div><div>After that, it depends on the CAP theorem and if you lean CP or AP. For the</div><div>latter, Riak.</div></div></blockquote><div><br></div><div>Postgresql is an application server in its own right,</div><div>Erlang renders Postgres useless -- Postgres renders Erlang useless.</div><div>Doing Erlang+Postgres is like doing the same job twice.</div></div></div></span></blockquote><div>Care explaining why do you consider postgres “an application server”?</div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;"><span><div><div><blockquote type="cite"><div>Never pick a "framework", since they always limit you in the long run.</div></blockquote><div><br></div><div>I couldn't agree more!!!</div><div>there is no room for a "frameworks" in a well designed system, using </div><div>appropriate tools.</div></div></div></span></blockquote><div><br></div><div>Really? Do you write everything from scratch for every new project? Your own grid system? Your own reactive css? Your own, I don’t know, deployment tools? Do you use OTP?</div><div>I think there’s a common misconception between “a framework” and “a library”.</div><div> </div>