3 ms·

"Don't use a web framework" definitely isn't something I would tell developers. I really think good web frameworks is one of the reasons why the web has progre

• peterevans 11y ago
  I don't think the post here is actually asserting not to use a web framework; just that you should not use a specific framework, named Revel, that aims to be Rails-esque. It brings up an interesting point for me about what is really possible (or desirable) in a framework written in a statically-typed, compiled language like Go compared to a dynamically-typed, interpreted language like Ruby.
• acheron 11y ago
  "progressed"
• jerf 11y ago
  In Go, "don't use a web framework" translates to something like "net/http is already a 'web framework' much like web.py or other 'minimalistic' frameworks". Unlike, for instance, Python, where you "have to" use a web framework because the standard library doesn't ship with much (http.server is too basic on its own [1]), the base net/http is enough for many non-trivial usages. (Of course Python has a few dozen good 3rd-party choices.) [1]: https://docs.python.org/3/library/http.server.html https://docs.python.org/3/library/http.server.html