<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web Framework on Farid</title><link>https://polymatx.dev/blog/tags/web-framework/</link><description>Recent content in Web Framework on Farid</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 06 Jul 2026 00:00:00 +0300</lastBuildDate><atom:link href="https://polymatx.dev/blog/tags/web-framework/index.xml" rel="self" type="application/rss+xml"/><item><title>GoFrame: A Batteries-Included Go Web Framework I Built for Real Projects</title><link>https://polymatx.dev/blog/posts/goframe-batteries-included-go-web-framework/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0300</pubDate><guid>https://polymatx.dev/blog/posts/goframe-batteries-included-go-web-framework/</guid><description>&lt;p&gt;Every Go service I&amp;rsquo;ve built over the years started the same way: pull in a router, wire up GORM, write the Redis connection helper &lt;em&gt;again&lt;/em&gt;, copy the RabbitMQ consumer boilerplate from the last project, glue a JWT middleware together, and spend the first two days of a new project rebuilding the same plumbing I built last time.&lt;/p&gt;
&lt;p&gt;Go&amp;rsquo;s standard library and ecosystem are excellent — that&amp;rsquo;s not the problem. The problem is that &amp;ldquo;lightweight and composable&amp;rdquo; means every team composes a slightly different stack, and the glue code between the pieces is where the bugs and the boredom live.&lt;/p&gt;</description></item></channel></rss>