rustic_result VS gopherjs

Self promotion moment:

If you enjoy the Result/Either type and API in Rust, I made this project just for this: https://github.com/linkdd/rustic_result

I also made https://github.com/linkdd/rustic_maybe/tree/main for an Option/Maybe type.

NB: Those are not types, but I'm waiting for set theoretic types to update those libs :)

It's missing the Erlang/Elixir pattern of returning a tuple `{:ok, T}` or `{:error, E}`, where we can then use pattern matching, or `with` expressions, etc...

To be fair, it is very similar to a `Result` type, which is why I made this library a while ago: https://github.com/linkdd/rustic_result

I intend to add a pipeline operator similar to Elixir, to be used with an std::result module which will provide functions to ease writing such complex code. I may take inspiration on an Elixir library I wrote a while ago: https://github.com/linkdd/rustic_result

A while ago, I made this library https://github.com/linkdd/rustic_result

I also made a library for working with `{:ok, value}` and `{:error, reason}` in Elixir: https://github.com/linkdd/rustic_result

Thanks to the pipeline operator and pattern matching, it makes pretty easy to read pipelines. It does not completely replace the with statement (that was not the point) but it simplified a lot of code.

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?

You can also write JS in Go with GopherJS, but if you don't fully understand the underlying JS webdev ecosystem, adding this extra layer of complexity is probably a really bad idea, at least at first.