Why would anyone need a "go web framework"? What is it, gorilla toolkit is not enough anymore?
No. And some developers prefer NodeJS dependencies on Go project, which this framework helpfully provides.
Show HN: ABCWeb – A Go Web Framework
11–20 of 29 posts
Re: Show HN: ABCWeb – A Go Web Framework
#12Install nodejs as a first step... Should not be a requirement of a Go web framework.
Yup, noped the hell out of there.
Re: Show HN: ABCWeb – A Go Web Framework
#13NodeJS is not a horrible dependency and it's not required when creating a new project. It's not like everyone doesn't already have Node or NVM installed for some other project.
How else is the framework going to handle/bundle these two parts together? There is so much code already out there that works for developing rich frontends that it seems silly for a "framework" that is trying to handle everything for you wouldn't handle that.
Re: Show HN: ABCWeb – A Go Web Framework
#14I'm usually the last person to jump to the defense of anything golang related... but people seem to be raising eyebrows about the nodejs dependency. Assuming they're using it for asset compilation etc I really don't see the problem. There's no reason to keep rewriting that stuff in every language.
You don't see a problem with installing nodes for assets compilation? What is the tech world coming to...
Re: Show HN: ABCWeb – A Go Web Framework
#15I'm usually the last person to jump to the defense of anything golang related... but people seem to be raising eyebrows about the nodejs dependency. Assuming they're using it for asset compilation etc I really don't see the problem. There's no reason to keep rewriting that stuff in every language.
You don't see a problem with installing nodes for assets compilation? What is the tech world coming to...
Sincere question: Assuming you're somehow doing web development without it, what is the problem?
Re: Show HN: ABCWeb – A Go Web Framework
#16Install nodejs as a first step... Should not be a requirement of a Go web framework.
To be fair, it's an optional requirement. The authors only recommend that you do.
We realize that some people may not enjoy having a NodeJS dependency so we've made this entirely optional (abcweb new --no-gulp), however we highly recommend using it due to the conveniences it provides.
Re: Show HN: ABCWeb – A Go Web Framework
#17Also checkout go buffalo http://gobuffalo.io/ the claims are nearly the same "Rails for go" . Too bad they didnt collaborate to make a single project better.
> Too bad they didnt collaborate to make a single project better
Building a web framework is one of those things everyone seems to try. Along with writing a CMS and/or message board.
I have no issue with the NIH mentality here just so long as the developers are realistic enough to accept that their pet project might not amount to anything significant in the wider community.
Re: Show HN: ABCWeb – A Go Web Framework
#18Are there any example webapps built with this?
This what I was looking for as well, but with no luck.
Re: Show HN: ABCWeb – A Go Web Framework
#19I'm usually the last person to jump to the defense of anything golang related... but people seem to be raising eyebrows about the nodejs dependency. Assuming they're using it for asset compilation etc I really don't see the problem. There's no reason to keep rewriting that stuff in every language.
You don't see a problem with installing nodes for assets compilation? What is the tech world coming to...
Typically assets involve more than just image and css files esp for any project you're building a full server for (i.e. not done with a static site generator), so yes that makes things more complicated, but their job is to remove the boilerplate from development (i.e. provide a "framework" to develop in) so you can do your existing development more easily in new projects.
And if you already have a better solution, or your solution requires an even more complicated set of tooling, just add `--no-gulp` and it won't bother you.
Re: Show HN: ABCWeb – A Go Web Framework
#20Why would anyone need a "go web framework"? What is it, gorilla toolkit is not enough anymore?
I mean go is nice cause it uses a lot less memory than Ruby/Python/Node and in many cases faster. I use it for side projects on things I'd like/want and I wish sometimes I didn't need to reach for Django just to get the MVP going.