Explore >> Select a destination
|
You are here 
|
flameeyes.blog | ||
| | | | |
jmmv.dev
|
|
| | | | | This is a rare post because I don't usually talk about Google stuff here, and this post is about Bazel: a tool recently published by Google. Why? Because I love its internal counterpart, Blaze, and believe that Bazel has the potential to be one of the best build tools if it is not already. However, Bazel currently has some shortcomings to cater to a certain kind of important projects in the open source ecosystem: the projects that form the foundation of open source operating systems. This post is, exclusively, about this kind of project. | |
| | | | |
bernsteinbear.com
|
|
| | | | | For small projects, you can DIY Ninja files instead of using CMake or Meson! | |
| | | | |
blog.oestrich.org
|
|
| | | | | Developer blog for Eric Oestrich | |
| | | | |
hjr265.me
|
|
| | | I began the weekend writing a silly program: MGHSIAC. It's the elegant abbreviation of "My GitHub Status Is A Clock". It turns my GitHub status into a working clock. You can read more about it here. But as silly as it is, I am now committed to keep it running. I have an always-on Raspberry Pi with Portainer running on it already. If I could make a Docker image and host it on Docker Hub, I could easily pull it to that Raspberry Pi and have it continuously update my GitHub status with clock emojis and messages. | ||
