gopherjs VS sqlx

I decided to try using Golang on the PSP and explored several approaches, including porting Clang, using TinyGo, and compiling Golang to JavaScript with GopherJS. Then, I came across a user named aethiopicuschan on the PSP homebrew Discord, who was attempting the same goal using WebAssembly. His example worked on PPSSPP but not on actual hardware.

IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here

Release notes have all the details. For now it is just compatibility with the 1.18 standard library, but generics support is planned.

Why not use https://github.com/gopherjs/gopherjs with jMonkeyEngine as-is?

When I wrote my first project in this year, I don't even planed to used blazor. But my childlike curiosity directed me on that path. I wanted to know, haw hard will be port game from desktop to web browser in .net. And I found out is not that hard. But I have experience with similar tools before. I used gopherjs and emscripten. Thanks to that I know what must to do, to communicate c# with javasrcipt. I made working blazor port pretty fast. Not only server side but webassembly to. Of curs create port for different platform always generate some problems. Most weird problem I have in blazor is how floating point number behave. I received in some cases NaN values. This problem I resolve adding value like 0.0001 in calculation.

If you're already building the backend in go and you don't like the prospect of coding in JavaScript it might be worth trying out https://github.com/gopherjs/gopherjs

Maybe this is were https://github.com/gopherjs/gopherjs will truly shine? Has anyone ever seen Go used for this?

> The sane middle ground is libraries that give you nicer ergonomics around SQL without hiding it (like Golangs sqlx https://github.com/jmoiron/sqlx). Engineers should be writing SQL, period.

The blog suggests that an ORM for OLAP would do exactly that

sqlx builds on Go’s database/sql and adds useful features like named queries, struct mapping, and scanning slices.

SQLx isn’t a migration tool per se, but it’s a powerful library for working with SQL in Go. You can build a custom migration system using SQLx to execute migration scripts, giving you ultimate flexibility. This approach is best for teams who want full control over their migration logic.

4. Infrastructure Layer — internal/infra/ This layer implements database logic using go-jet and sqlx. It satisfies the interfaces defined in the domain layer.

### When to Use Viper Use Viper for **applications with complex configurations**, like microservices or CLI tools. For simple scripts, environment variables alone might suffice. ## Comparing the Libraries Here’s a quick table to help you decide which library fits your needs. | Library | Use Case | Key Feature | Performance | Learning Curve | |---------|----------|-------------|-------------|----------------| | Gin | Web APIs | Routing | High | Low | | Testify | Testing | Assertions | N/A | Low | | Zap | Logging | Structured | High | Medium | | GORM | Databases| ORM | Medium | Medium | | Viper | Config | Flexibility | N/A | Low | ## Tips for Getting Started - **Start Small**: Try one library at a time in a side project. - **Read Docs**: Each library has excellent documentation (linked above). - **Join Communities**: Check GitHub issues or Go forums for tips. - **Experiment**: Use the example code as a base and tweak it. ## What’s Next? These libraries are just the tip of the iceberg. Once you’re comfortable, explore others like [Cobra](https://github.com/spf13/cobra) for CLI tools or [sqlx](https://github.com/jmoiron/sqlx) for lightweight database access. The Go ecosystem is vast, and combining these tools can help you build robust, scalable applications. Pick one library, try the example, and see how it fits your workflow. Happy coding!

Go offers quick database interactions that result in fast performance. It provides both native database drivers and sqlx for simplified querying. As you have seen in this article, you have used native database driver, SQL just by importing a package straight from GitHub. Similarly, you can use sqlx to have reduced boilerplate and more built-in features like struct mapping.

sqlx for the database driver.

We've always used https://github.com/jmoiron/sqlx which is just the standard package + mapping to/from structs.

You can use this https://github.com/jmoiron/sqlx