4 ms·
How is this setting things up "quickly" when OP is asking to limit complexity? You're suggesting: 1. Server side in Go 2. Cross-compiling it 3. sftp'ing and re
by kvm 8y ago
How is this setting things up "quickly" when OP is asking to limit complexity? You're suggesting:
1. Server side in Go
2. Cross-compiling it
3. sftp'ing and restarting the service everytime
4. postgres
5. ansible
6. Makefiles
7. Webpack
8. Babel
9. React
- IshKebab 8y agoWriting web servers in Go is extremely easy. https://golang.org/doc/articles/wiki/ https://golang.org/doc/articles/wiki/ Cross-compiling with Go is done by setting two environment variables. That's it. This is not like the mess of C++ cross-compiling. In LiteIDE it is simply a matter of choosing Linux from a drop-down: https://www.wut.de/pics/screenshot/e-505ww-07-pide-000.png https://www.wut.de/pics/screenshot/e-505ww-07-pide-000.png SFTP is not exactly hard. Nor is `nohup ./server &`. From 5 on I agree though - is that 4 build systems? Insanity. I would just make a static web page with normal HTML forms or whatever and Go templates. If you really need client-side Javascript, I'd just use jQuery, or something similar and lightweight like minifiedjs.
- marcus_holmes 8y agoyeah, I use straight HTML wherever possible. But for some things it isn't possible, or suitable. I'd love a simpler client-side environment. Any suggestions welcome... I'm looking at Vue.js now, recommended from comments here.
- timlyo 8y agoI've enjoyed using Elm for client side development.