|
Am I the only one who dislikes Go specifically for CRUD webapps? I’ve worked with Go professionally for the past 5 years, and I genuinely like the language. I like the anti-framework philosophy, the simplicity, the resistance to over-abstraction or even worse... bad abstractions, fast builds, the light native binaries, and how easy it is for a team to converge on idiomatic code. But the moment you’re building a normal product app, even “basic CRUD” is rarely just CRUD. You need a database layer, migrations, auth, validation, maybe an OpenAPI spec, background jobs, admin flows, maybe server-side rendering, maybe GraphQL, etc. You can end up with a large codebase full of repetitive boilerplate for an app that does not actually do much conceptually. Maybe some people see a large codebase and feel accomplished, but just because each line of code is readable doesn't mean you know what its doing. |