Explore >> Select a destination
|
You are here 
|
infinitedigits.co | ||
| | | | |
peter0x44.github.io
|
|
| | | | | Cross compilation is a common task during development, but different compilers and programming languages handle it in their own ways, and I wanted to write about the various flavors of trade-offs and design decisions that you will find across different tooling. I feel like I have absorbed a lot of information about how cross compilation works across different targets, tools and languages, so I figured it was time to condense my knowledge into a blog post. This is not a tutorial, but it still contains practically applicable knowledge. I don't claim to get every detail correct, merely explaining how things work to my understanding. | |
| | | | |
www.screamingatmyscreen.com
|
|
| | | | | Timo Zimmermann talking about software engineering, leading teams, consulting and start ups. | |
| | | | |
prashamhtrivedi.in
|
|
| | | | | Introducing First CLI I made using Golang. | |
| | | | |
www.updatecli.io
|
|
| | | Time flies, and It's time for another successful experiment to go out. Shareable Update Policies A recurring problem over time has been, how to reuse the same Updatecli manifests for different projects. From the beginning of the Updatecli project, it was possible to parameterize Updatecli manifests using values or secrets files, but still, we had to copy the same Updatecli manifest over and over. This led to duplication, maintenance burden, and ultimately, It didn't scale well. | ||
