MadVikingGod
Joined 9 years ago
Joined 9 years ago
[1]: https://www.gnu.org/licenses/agpl-3.0.txt
[2]: https://github.com/ONLYOFFICE/core/blob/master/LICENSE.txt
[3]: https://github.com/ONLYOFFICE/onlyoffice-nextcloud/blob/mast...
What I wonder is if there is a medium between Nix's build everything from the ground up, and the traditional get everything delivered. I've been excited about the Fedora Atomic collections, silverblue etc., as it gives me a lot of the roll back and isolation of nix with the workflow closer to a regular fedora or arch. I'm not saying that everything is roses, but I've been able to use it more than I ever got out of a nix.
Let's look at an example. Let's say your phones main board, which will net a few hundred grams of raw materials. First thing by weight the actual board itself is probably the biggest, if you could perfectly decompose it to it's parts you would have some fiberglass, glue, a few grams of copper, and maybe a trace amount of gold. Next you would have the different components, mostly ICs but let's cover them next. These are mostly plastic with bits of copper, tin, and other more exotic metals. Most of these could be used again, if you can separate them and sort them. There would be a bunch of solder, which maybe could be reused, if you remix it with more flux. Finally, you'll have chips, these could be reused, but only as replacements for the same chip. Getting anything out of these would mostly be removing the bulk of the material which is silicon that's been contaminated with other elements to make the semiconductors. I don't think there is any process right now that could take doped Si and get you anything back. Besides the silicon you have micrograms of gold and other conductors.
Having put all that down, I think there could be an opportunity to take the bulk components off boards, test and sort them, and sell them in bulk.
// code.go
var now = time.Now
// code_test.go
func TestCode(t *testing.T) {
nowSwap := now
t.Cleanup (func() {
now = nowSwap
}
now = func() time.Time {
return time.Date(...)
}
}
Examples
Code: https://github.com/open-telemetry/opentelemetry-go/blob/main...
Test: https://github.com/open-telemetry/opentelemetry-go/blob/490f...I don't know what service is safe, but it seems like the incentives for the companies is not to direct me to what I want, real people performing music.
I prefer to use podman if it’s available on my system but it still hasn’t hit the critical mass needed for it to be targeted and that’s a shame.
Also is there something like a dockerfile for buildah? I’ve tried a few times to understand how to use buildah and just fall back on a dockerfile because I can’t seem to wrap my head around how to put it into something IAC like.
What I would actually like to see is how this performs in a more real world situation. Like does this increase line error rates, causing the transport or application to have to resend at a higher rate, which would erase all savings by having lower latency. Also if they are really signaling these in the multi GHz are these passive cables acting like antenna, and having a cabinet full of them just killing itself on crosstalk?
You now have many choices on how to proceed, but none of them will include A) being able to build old releases, or B) doing so without making changes to all dependencies.
One choice is go to the leaves, C in our example, and make a release on gitlab. Then go to B, and have B depend on the gitlab C. This is fine for rolling forward, but if you want to roll back you would have to rewrite all of C to use the gitlab url, and find all of the equivalent tags and repush all of them. Also tell your users that any binaries you've released now have new hashes. Then repeat this for every repo. It's not a small task.