Skip to content
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

Open
lewtds opened this issue Jul 10, 2013 · 12 comments
Open

Move gokien.org to a dynamic web framework #63

lewtds opened this issue Jul 10, 2013 · 12 comments

Comments

@lewtds
Copy link
Contributor

lewtds commented Jul 10, 2013

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?

@cmpitg
Copy link
Member

cmpitg commented Jul 12, 2013

+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.

@tuanta
Copy link
Member

tuanta commented Jul 12, 2013

I suggest we use Drupal. It's the best open source CMS/Framework for building dynamic web.
Lot of FOSS community website are currently using Drupal too.

@cmpitg
Copy link
Member

cmpitg commented Jul 12, 2013

-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/

@tuanta
Copy link
Member

tuanta commented Jul 12, 2013

Hating PHP is just your opinion :).
I can not change the fact the Drupal is widely used all over the world, including a lot of FOSS community sites; and the fact that, there are over 800,000 developers is working on Drupal now.

I personally don't think (see) maintaining a Drupal website is too costly.
All we need to do is keep Drupal core and additional modules up-to-date. That's an easy task, 1-2h per week only.

@cmpitg
Copy link
Member

cmpitg commented Jul 12, 2013

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.

@lewtds
Copy link
Contributor Author

lewtds commented Jul 12, 2013

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.

@tuanta
Copy link
Member

tuanta commented Jul 12, 2013

If you believe that @cmpitg, we should make a range voting.

@fuzzysource
Copy link

I think we should submit prototypes before voting. :))

On Fri, Jul 12, 2013 at 8:16 PM, Truong Anh Tuan
[email protected]:

If you believe that @cmpitg https://github.com/CMPITG, we should make a
range voting.


Reply to this email directly or view it on GitHubhttps://github.com//issues/63#issuecomment-20875593
.

Đàm Tiến Long
Email: [email protected]
Twitter: https://twitter.com/#!/fuzzysource
Homepage: http://fuzzysource.github.com

@cmpitg
Copy link
Member

cmpitg commented Jul 14, 2013

Prototype?

@fuzzysource
Copy link

A sample :D

On Sun, Jul 14, 2013 at 7:03 PM, Nguyễn Hà Dương
[email protected]:

Prototype?


Reply to this email directly or view it on GitHubhttps://github.com//issues/63#issuecomment-20935397
.

Đàm Tiến Long
Email: [email protected]
Twitter: https://twitter.com/#!/fuzzysource
Homepage: http://fuzzysource.github.com

@myguidingstar-zz
Copy link

I think we should close this issue as we don't need it right now.
IMO proposals should come from bottom up, not top down with pure prediction. Anw, not many people want to learn web programming (Doing both frontend + backend is a huge learning curve!)

@lewtds
Copy link
Contributor Author

lewtds commented Jul 17, 2013

Why should we close it? The non-critical tag is for issues like this.
btw, I want.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants