Hi Axel I agree on the suggestions you give on the article, even I have another view of the "epidemic".
To be short: almost none of the "Basic/Simple/lightweight http rest/mux/routers/socallframeworks" is supposed to have a real usage. Sometimes I have the task (I'm the lucky guy) to do technical interview with people applying for my company, and I see that almost EVERYBODY has , in the resumee, a "personal project" to show. Seems good? Uhm.... In my experience, ~80% of that projects are "*Basic* something", "*Simple* whatever", piece of code. Meaning they are very primitive, incomplete, not ready, but.... they create a new entry in the Resumee or Linkedin. Nothing I would call "a product", neither close to it. Lot of Resumee also mentions how many forks their projects has, so the best way to have forks is to write "libraries" and "API". So that, some softwares in use by the HR are confirming "sure, this guy is very famous for his Basic HTTP proxy". (Until you don't try to use it, I mean. But no software in use by the HR is able to do it. Hope the AI will, someday.). I am not a developer (I work as a system architect), nevertheless I find golang very good for prototyping. Many times I've hit my head on those "libraries", "so call frameworks" and "API". 100% of times I implemented my POC following instructions and documentation (when given. ~90% has no decent documentation), just to realize that the "framework" was barely able to fit 1/2 use-cases an inexperienced Junior was able to imagine. So I ended up to rewrite everything from scratch. Fortunately golang has this amazing feature of Interfaces, so I just needed to change "the meaning" of a specific call. Anyhow, I think you are worrying for code which is not written to be useful, neither utilized, and not even taken in consideration : is written for some Human Resource office here and there. According with github, there is a plenty of good software written in golang. When you exclude the "Simple", "Easy", "Basic" stuffs, (=unfinished/incomplete) you find an amount of "ready+complete" software which is still impressive, but.... much smaller. The epidemic of "simple this/easy that/basic whatever" , regarding API / libraries /proxy /routers (written in golang or others) will not finish even if/when you convince everybody this is not useful: none of that software* is supposed to be useful. * They are just another line on the Resumee/Linkedin. Just my two cents, of course. Besides, nice article. FEM On Monday, 19 June 2017 00:02:37 UTC+2, Axel Wagner wrote: > > Hey gophers, > > in an attempt to rein in the HTTP router epidemic, > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
