Replies: 4 comments 10 replies
-
|
Either way you go, HTMX will help significantly. I prefer Go, because the namespace can stay clean with structs and interface reciever functions, and I don't directly have to deal with memory, but I'd be happy to use C too. |
Beta Was this translation helpful? Give feedback.
-
|
Please, I beg of you, not node or any type of JavaScript on the backend. |
Beta Was this translation helpful? Give feedback.
-
|
Since I'm unhinged enough to risk getting perma banned from this repo: I'd suggest Java Swing/AWT on the frontend. |
Beta Was this translation helpful? Give feedback.
-
|
assembly backend. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
howdy! so obv we've got some choices to make here regarding the tech stack. i've got a few things in mind, but wanna get early iterative feedback wherever possible
here's what i've got:
i think that's all i've got for now. so that brings us to the actual question
because this idea is so novel, do we want to go for a full novel approach and do The Based Thing™️ by building gitsoc entirely in C? or do we want to be boring and standard with go/js?
7 votes ·
Beta Was this translation helpful? Give feedback.
All reactions