4 ms·
This is so true. I love go so much, because deployment is so easy, but using it for end-user web content is a real PITA.
by sacado2 8y ago
This is so true. I love go so much, because deployment is so easy, but using it for end-user web content is a real PITA.
- mbrumlow 8y agoWhat makes it a PITA? I use go for building websites and it was the first time web development really made any sense. All the other systems out there require tons of tools, and lock you into doing things their way. So, what makes GO so much of a pain? Maybe ignorance is bliss for me?
- apta 8y ago> All the other systems out there require tons of tools, and lock you into doing things their way. Nothing is stopping you from writing everything yourself in any other language. You can do the same in Java or .NET. Then you start finding out you need routing, validation, security, DB access, etc. which golang lacks and ends up making it much more verbose than other mature frameworks.
- sacado2 8y agoI made a very simple webapp a few months ago, where students are proposed assignments and can rank them. For that, you need authentication, and DB management: a subject table, a student table, and a ranking table. You have to do all of that manually in go, while other languages have frameworks that take care of it. Still did it in go because it was a very simple webapp and deployment is so easy with go, but for a more complex task I'm not sure I'd have used it.
- mbrumlow 8y agoI hear this argument a lot. I like to ask, are you writing software or using frameworks? I am not saying you need to write all your software but if your app is on the lines of declaring a few statements and running a command to generate the rest then I have to ask what you really are doing. On top of that you have to ask how you will approach changing your program using frameworks to the specs of the task at hand? Also, can you go into what is "manual" about autentication, db management in go? Compared to other languages? Did you mean framework?