Goravel: A Go framework inspired by Laravel

Positioning and “Laravel‑inspired” Messaging

• Several commenters say the site should briefly explain Laravel and why it’s appealing, especially if “Laravel‑inspired” is meant to attract Go developers without PHP/Laravel experience.
• Others argue the primary audience is existing Laravel users moving to Go, who can get Laravel background elsewhere.
• There’s some pushback that relying on Google instead of clear on-site positioning is a poor product marketing choice.

Do Go Developers Need a Laravel‑Style Framework?

• One camp says Go’s “way” is stdlib + a few small libraries; large, batteries‑included MVC frameworks are unnecessary and eventually obstructive.
• The opposing camp notes that other ecosystems (Rails, Django, Laravel, Spring, ASP.NET) prove demand for full‑stack frameworks with routing, ORM, auth, queues, email, caching, admin, docs, etc., bundled coherently.
• Some think there is space in Go for such a framework, but cloning Laravel’s API/terminology too literally may deter adoption.

Frameworks vs. Standard Library and Small Libraries

• Pro‑stdlib voices list what Go already provides: HTTP routing/middleware, templates, DB access, logging, JSON, crypto, etc., supplemented by focused libs (routers, auth, metrics).
• Critics respond that this is like “Raspberry Pi vs iPhone”: yes, you can build everything, but a cohesive framework saves all the glue work, centralizes docs, and standardizes patterns.
• Some describe internal scaffolding tools that effectively play the role of a light framework, even if not branded as such.

ORMs and Data Access

• Strong anti‑ORM sentiment: generated queries are opaque, harder to debug, can be slow, and add layers of complexity; raw SQL or thin helpers (sqlx, sqlc, Scany, Dapper‑style) are preferred.
• Others argue ORMs dramatically speed up CRUD and large schemas, with escape hatches for hand‑written SQL. Claims that ORMs are always bad are labeled as a “red flag” by some, as they can slow delivery of business value.

Team Productivity, Conventions, and Enterprise Needs

• Supporters of big frameworks emphasize conventions, predictable structure, faster onboarding, and easier maintenance across many teams.
• Enterprise concerns mentioned include OpenAPI‑driven contract validation, auto‑generated docs/clients, background jobs, rate limiting, and admin panels—areas where Go is seen as more DIY.
• Skeptics counter that large frameworks can themselves become “Frankenstein” systems as teams diverge in how they use them.

Goravel‑Specific Reactions

• Some Laravel‑and‑Go fans are enthusiastic and say Goravel could bring them back to Go.
• Others think porting Laravel concepts into Go adds unnecessary complexity and that people wanting Laravel should just use Laravel.
• Naming and logo are seen by some as awkward or too derivative; one person calls the site’s cookie banner excessively bloated.