The go modules message is kind of an eyesore and use of modules seems to be nearly ubiquitous at this point... Seems like this could safely be moved to a small note in the Install documentation instead?
Having this notice from over a year ago on every page just makes the project feel abandoned... As a new user, before I really dug into buffalo, I had reservations because of this.
Ultimately, I found that buffalo was the easiest way to deploy a golang + web app as a single binary without any other dependencies, and hot code reloading to make that process very simple. Perhaps "Deploy your entire app as a single binary" may be worth adding to the homepage...
The go modules message is kind of an eyesore and use of modules seems to be nearly ubiquitous at this point... Seems like this could safely be moved to a small note in the Install documentation instead?
Having this notice from over a year ago on every page just makes the project feel abandoned... As a new user, before I really dug into buffalo, I had reservations because of this.
Ultimately, I found that
buffalowas the easiest way to deploy a golang + web app as a single binary without any other dependencies, and hot code reloading to make that process very simple. Perhaps "Deploy your entire app as a single binary" may be worth adding to the homepage...