gopherjs VS Testify

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?

Ah this is interesting. I've been blindly using this library for the past 6 years: https://github.com/stretchr/testify.

testify is a testing toolkit that adds better assertions, mock capabilities, and test suite support on top of Go’s built-in testing package. It’s commonly used for simplifying test logic and improving test readability.

Testify simplifies writing unit tests in Go. The standard testing package is fine, but Testify adds assertions, mocking, and suite support, making tests more readable and maintainable.

I prefer to use the Go library testify, which significantly simplifies the code:

nil is returned initially, as we're creating user_test.go and using Testify to create tests as we shape the behavior of PostUser. We don't have a DB wired up yet, so the responses will simply be hard-coded structs of what we expect the API to respond with for now to pass the tests.

Bonus: Testify

Testify: Popular framework with assertion functions and mock objects.

Testing: unit and integration tests using Testify and formatted test output using gotestsum

We’ve integrated the excellent testify library with its “assert” functionality to allow for smoother test implementation:

This article is too basic and does not introduce anything you'd encounter in a typical Go project. If you want introduction to Go testing I recommend just reading the official docs https://pkg.go.dev/testing and understanding how to write table driven tests - https://go.dev/wiki/TableDrivenTests.

Going beyond what's built in, get familiar with https://github.com/stretchr/testify as that's used a lot.