-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move gokien.org to a dynamic web framework #63
Comments
+1 for this A simple web framework, moving slowly, add things only needed is my prefered method. I suggest Nitrogen for damn good fault tolerant, scalability, best architecture and performance (Nginx's design is based on Nitrogen), decent API, but takes time to learn if you don't know Erlang. It doesn't matter for me since we don't need to move in a flash, though. My second choice is Goliath for stability, good performance, and decent APIs. |
I suggest we use Drupal. It's the best open source CMS/Framework for building dynamic web. |
-1 on Drupal We'll need more than just a CMS. And PHP is horrible[1], making extending and maintaining process damn costly. I personally hate PHP with a passion. [1] http://me.veekun.com/blog/2012/04/09/php-a-fractal-of-bad-design/ |
Hating PHP is just your opinion :). I personally don't think (see) maintaining a Drupal website is too costly. |
It's not just my opinion but all the current dev in our project too ;-). Popularity doesn't reflect quality, especially in comparison to resources. We have limited resource right now. |
I'm practically blind in this matter. Whatever you guys choose will do for me. That PHP criticism is awesomely hilarious. Anw, after some introduction to Erlang, I've found it to be very similar to Haskell. |
If you believe that @cmpitg, we should make a range voting. |
I think we should submit prototypes before voting. :)) On Fri, Jul 12, 2013 at 8:16 PM, Truong Anh Tuan
Đàm Tiến Long |
Prototype? |
A sample :D On Sun, Jul 14, 2013 at 7:03 PM, Nguyễn Hà Dương
Đàm Tiến Long |
I think we should close this issue as we don't need it right now. |
Why should we close it? The |
Sooner or later, we'll need a dynamic web framework. Things like interface translation is not easily done with static web. Who knows what we may also need in the future?
The text was updated successfully, but these errors were encountered: