3 ms·
There is something really strange about a lot of recent Go projects including this one. I can't put my finger on, but the combination of the author and the type
by soheil 5y ago
There is something really strange about a lot of recent Go projects including this one. I can't put my finger on, but the combination of the author and the type of problem they choose to tackle oftentimes seems baffling to me. Most projects seem to be solving a problem that is often misidentified or otherwise badly solved, but somehow the focus ends up being on the code architecture or the UI design. It's like they're trying to solve a problem just for the sake of writing some code and the correct way to use Go idiomatically or something and don't really care about the problem or how well the solution actually works.
- jrm4 5y agoYeah, as a bit of an old-timer, I'm trying to learn to stop worrying and learn to love watching everybody reinvent wheels? For me it's "why are you people doing that in Javascript?" that continually comes up in my own head, but I suppose I should try to be patient and see if anything comes of it.
- asdff 5y agoI think projects like this are just resume builders. Everyone says "show a project on github," well here is one of these projects. The dev is probably hoping this helps land them a job offer. Its fine if the project is ultimately "lame" in some way, since its not the job description of a developer to make a cool unique app, but to follow orders from the project manager and write code, which is what this project shows this dev can do.
- amirGi 5y agoOP here! Actually, I don't care about this landing me a job lol, I wrote this purely for fun and to (hopefully) be able to use it :)
- amirGi 5y agoOP here, I'm not claiming to be a Go expert, in fact I'm far from it! I used Go as my backend because I didn't want to use Node - it's very likely that I might be using it in ways it might not be intended, please do let me know if so!