rules_go | statik | |
---|---|---|
6 | 6 | |
1,331 | 3,721 | |
-0.2% | - | |
9.0 | 0.0 | |
9 days ago | 7 months ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rules_go
-
When to Use Bazel?
There’s an issue I reported (along with a proof of concept fix) over 4 years ago, that has yet to be fixed: building a mixed source project containing Go & C++ & C++ protocol buffers results in silently broken binaries as rules_go will happily not forward along the linker arguments that the C++ build targets (the protobuf ones, using the built in C++ rules) declare.
See https://github.com/bazelbuild/rules_go/issues/1486
Not very confidence inspiring when Google’s build system falls over when you combine three technologies that are used commonly throughout Google’s code base (two of which were created by Google).
If you’re Google, sure, use Bazel. Otherwise, I wouldn’t recommend it. Google will cater to their needs and their needs only — putting the code out in the open means you get the privilege of sharing in their tech debt, and if something isn’t working, you can contribute your labor to them for free.
No thanks :)
-
Caculating Go type sets is harder than you think
Bazel in theory maintains its own directory of generated code that your IDE should refer to. Back when I last used Bazel, there was a bug open to make gopls properly understand this ("go packages driver" is the search term). Nobody touched this bug for a couple years, so I gave up.
Here's the bug: https://github.com/bazelbuild/rules_go/issues/512
I basically wouldn't use Bazel with Go. Go already has a build system, Bazel is best for languages that don't ship a build system, like C++.
-
Buf raises $93M to deprecate REST/JSON
`proto_library` for building the `.bin` file from protos works great. Generating stubs/messages for "all" languages does not. Each language does not want to implement gRPC rules, the gRPC team does not want to implement rules for each language. Sort of a deadlock situation. For example:
- C++: https://github.com/grpc/grpc/blob/master/bazel/cc_grpc_libra...
- Python: https://github.com/grpc/grpc/blob/master/bazel/python_rules....
- ObjC: https://github.com/grpc/grpc/blob/master/bazel/objc_grpc_lib...
- Java: https://github.com/grpc/grpc-java/blob/master/java_grpc_libr...
- Go (different semantics than all of the other): https://github.com/bazelbuild/rules_go/blob/master/proto/def...
But there's also no real cohesion within the community. The biggest effort to date has been in https://github.com/stackb/rules_proto which integrates with gazelle.
tl;dr: Low alignment results in diverging implementations that are complicated to understand for newcomers. Buff's approach is much more appealing as it's a "this is the one way to do the right thing" and having it just work by detecting `proto_library` and doing all of the linting/registry stuff automagically in CI would be fantastic.
-
Why does Bazel not get more love?
This can be ugly in some languages. There’s decent go support in VSCode if you follow these copy & paste instructions here https://github.com/bazelbuild/rules_go/wiki/Editor-setup
- GOPACKAGESDRIVER support for Bazel's rules_go, fixes Bazel + gopls
-
What is the preferred way to package static files (html/css/js) along with your standalone binary in 2020?
Bazel go_embed_data
statik
-
Creating JavaScript GUI and GO backend for multiplatform desktop app
Yep and to avoid having the front-end files in the distributable I use https://github.com/rakyll/statik to bundle them into the main binary.
- Belajar dan Berkenalan dengan Go Embed
-
REST Servers in Go: Part 1 – standard library
> I've had this a few times, most recently with "how do I add this data file to my binary". At least that one made it to master now, and will be in 1.16!
And before 1.16, there is statik: https://github.com/rakyll/statik.
-
Going Places: How I used Golang for literally every part of an IoT system
Aren't our web assets part of the system as well? So to make it completely Go, we've gotta some how make them part of the Go code. The most obvious choice for that is to turn them into binaries and embed right inside our backend code. This task is relatively simple with a wide range of tools to choose from. For this project, I went with statik, and simply generate the embeddings with this command.
-
OpenPokémonRed - An Go re-implementation of Pokémon Red
It seems it's using https://github.com/rakyll/statik -- probably some assets?
-
What is the preferred way to package static files (html/css/js) along with your standalone binary in 2020?
statik - https://github.com/rakyll/statik
What are some alternatives?
go-bindata - A small utility which generates Go code from any file. Useful for embedding binary data in a Go program.
go-bindata - A small utility which generates Go code from any file. Useful for embedding binary data in a Go program.
go - The Go programming language
packr - The simple and easy way to embed static files into Go binaries.
edotool - edotool: simulate keyboard input and mouse activity
go-embed - Generates go code to embed resource files into your library or executable
statics - :file_folder: Embeds static resources into go files for single binary compilation + works with http.FileSystem + symlinks
go.rice - go.rice is a Go package that makes working with resources such as html,js,css,images,templates, etc very easy.
buildtools - A bazel BUILD file formatter and editor
vfsgen - Takes an input http.FileSystem (likely at go generate time) and generates Go code that statically implements it.
aegis - Linux, FreeBSD, NetBSD, OpenBSD and Windows debugging detection library. With support for C and Go.
esc - A simple file embedder for Go