Wasn’t Reddit originally in python? That’s what I think the GitHub was when I last looked at it.
But python and Go are languages you just don’t find many people with free time willing to work on. So, if you want to be in a situation like Putt and do all the work then go for it.
Votenco is already up and running, a solid framework which has a community that is possibly more vibrant than ruby these days and you could benefit by lots of possible people willing to help out.
Plus you also need to consider the front end coding. I hate js but today, I would run the front end on it using something like vue.js and then do everything with API calls making the backend almost agnostic. No, I would not run the backend on any js framework.
The current voat front end is cluttered and has a few mobile issues.
The core voat code is easily replicable to another language but it’s all the minor details that will start to slow development down.
The last topic is scalability. Is voat behind a load balancer? Is the DB on a separate slice and how many core machines does it run on. Probably 1 machine which in reality more than enough but if you do get big, this part of the architecture needs to be thought of.
view the rest of the comments →
WhiteRonin ago
Wasn’t Reddit originally in python? That’s what I think the GitHub was when I last looked at it.
But python and Go are languages you just don’t find many people with free time willing to work on. So, if you want to be in a situation like Putt and do all the work then go for it.
Votenco is already up and running, a solid framework which has a community that is possibly more vibrant than ruby these days and you could benefit by lots of possible people willing to help out.
Plus you also need to consider the front end coding. I hate js but today, I would run the front end on it using something like vue.js and then do everything with API calls making the backend almost agnostic. No, I would not run the backend on any js framework.
The current voat front end is cluttered and has a few mobile issues.
The core voat code is easily replicable to another language but it’s all the minor details that will start to slow development down.
The last topic is scalability. Is voat behind a load balancer? Is the DB on a separate slice and how many core machines does it run on. Probably 1 machine which in reality more than enough but if you do get big, this part of the architecture needs to be thought of.