It's a simple http router, it just filter requests and assign them to an handler, it's hardly a framework like Symfony, Laravel, Django, Rails or Spring. People need to stop calling http routers "frameworks".

People are going to write code for multiple reason. You can't complain about people writing opensource code, you're not forced to use it.

It happens anytime a language has the web tooling built in so a framework largely becomes arranging parts to your preference and naming it.

See PHP and JavaScript.

The languages that don't have all the web stuff built in tend to have a single dominant framework.

This framework has been around forever and not really. Most people use the standard library unless they need better routing than the standard library provides.

There are actually very few web frameworks that provide much other than a router in Go. Most of the frameworks are actually just packages that can be used for all sorts of things. e.g. Beego by astaxie

Well I wasn't commenting on age of particular projects. I had not heard of Beego so now I still feel there is a bit of over growth. Leads to confusion over what to use when you do want better routing which I think is pretty much every project. Perhaps routing will continue to improve in the standard library such that it does not feel like I need to pick a package or roll my own.

A lot of web developers learned it, and a very natural tendency is to use a new medium in service of the old paradigm. The first tv broadcasts were a bunch of guys sitting at a table, reading the news just like they did on the radio.

There are a lot of web developers (aka full stack developers) out there!

Can we stop this language to become the next JS ?