search

actuallyaridan / chirp

a social media project meant to mimic the feel of twitter but be better
https://beta.chirpsocial.net
MIT License
11 stars 16 forks source link

Separate backend from frontend #2

Open DexrnZacAttack opened 4 months ago

DexrnZacAttack commented 4 months ago

I think the backend should be completely separate from the frontend, and the frontend should interact with the backend through JS, with the backend returning JSON data instead of HTML... this allows anyone to make a custom frontend, and it makes the codebase cleaner... using this you can have an easier time implementing an account system, and other stuff that I cannot explain at the moment cuz it's 4 am.

I may be happy to help, depending on the free time I have, but if I were the one doing the backend, I would probably do it in Express. (mainly because that's what I am more familiar with)

parpok commented 4 months ago

I get the idea however I think that this project is in so early stage that complicating it like that isn't really worth it. Maybe when stuff gets real, like really real then it will make sense. For now IMO focusing on providing basic UX should be more important.

DexrnZacAttack commented 3 months ago

I get the idea however I think that this project is in so early stage that complicating it like that isn't really worth it. Maybe when stuff gets real, like really real then it will make sense. For now IMO focusing on providing basic UX should be more important.

personally I think it would be a pain to port it in the later stage though... plus it would be wayyy to intertwined and hell to seperate (as then you have to code wayyy more client side JS.)