Maybe this isn’t the intention of this forum (or maybe it is), but it will probably fall in-front of the right eyes to bring me up to speed.
What was the reasoning behind the team’s choice to roll with emberjs/Ruby/Postgre?
I have no doubt that Discourse is for sure going to cause a stir in the ‘forum industiry’/‘online community industry’ given the people behind it and the innovative new concepts it brings to the table.
Wouldn’t it have been better built in PHP/MySql. Don’t shoot me. I know that probably sounds blasphemous to the ‘purist’ (or ‘moderately competent’ ) programmers out there, but think about it. The PHP community dwarfs the Ruby community, as a result of which the availability of web hosts offering PHP/MySql at ‘small business prices’ dwarfs those supporting the technology stack for Discourse.
Or was it a business desicion? Will you sell more of your upcoming hosting offerings by using a more obscure technology stack?
(Or I’m guessing the real answer is it’s probably the language the founding members were more profficient in - aside from Jeff, as I read in his blog… or on the about page… somewhere).
tl;dr - Wouldn’t the uptake have been quicker in terms of both community input and Discourse installations if Discourse were written in a more popular technology stack (e.g. Php/MySql).
I’m not a PHP advocate nor trying to start a holy war, just curious.