Buffalo – MVC Web Framework for Go
gobuffalo.io
Buffalo – MVC Web Framework for Go
1–10 of 46 posts
Re: Buffalo – MVC Web Framework for Go
#2Re: Buffalo – MVC Web Framework for Go
#3Re: Buffalo – MVC Web Framework for Go
#4For large projects, using a framework and writing code the way the framework wants you to means that it's much easier to get new team members up to speed, meaning they contribute sooner and with less draw on other team members to teach them the nuances of your weird custom stack.
For small projects, and side projects especially, you can't/don't want to lose steam in analysis paralysis deciding on every little library and thing you want to use. Just pick up the framework that has made most of those decisions for you and focus on the business logic.
Rails nails this. Laravel is pretty good at this. Lots of others do this too (rails and laravel are where I spend my time). Sure, they might not be "exciting" but they are productive, and that, to me, is most important.
Re: Buffalo – MVC Web Framework for Go
#5Re: Buffalo – MVC Web Framework for Go
#6Not a mobile friendly website? Please it's 2017
It's open source. Why don't you contribute?
Re: Buffalo – MVC Web Framework for Go
#7Not a mobile friendly website? Please it's 2017
That's a pretty negative attitude. It's open source. Why don't you contribute? https://github.com/gobuffalo/gobuffalo
Does it personally bother me? No. But I think the expectation is reasonable.
Re: Buffalo – MVC Web Framework for Go
#8Re: Buffalo – MVC Web Framework for Go
#9I always defer to frameworks when working on any project, large or small, so this looks really cool to me as we have been debating on breaking out some of our high volume components into microservices at work and Go is an option. For large projects, using a framework and writing code the way the framework wants you to means that it's much easier to get new team members up to speed, meaning they contribute sooner and…
Re: Buffalo – MVC Web Framework for Go
#10I always defer to frameworks when working on any project, large or small, so this looks really cool to me as we have been debating on breaking out some of our high volume components into microservices at work and Go is an option. For large projects, using a framework and writing code the way the framework wants you to means that it's much easier to get new team members up to speed, meaning they contribute sooner and…
Depending on how micro your microservice is and if it really is high volume (not sure what high volume means to you) then I would recommend just stick with the standard library to start and grabbing other libs as you need. I wrote a simple internal microservice handling ~400k req/s at peak with no framework and it works great. I can see the appeal of the framework in getting something up and running really fast with…