• 0 Posts
  • 476 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle



  • A decade older when assuming office…

    Obama was one of top youngest candidates though, she is more median

    Pro fracking…

    And she reversed her decision. A lot of things depends on the geopolitical situation. Since Russia decided to invade Ukraine, West placed sanctions on their oil and gas, but problem with energy is that it is inelastic. If there’s not enough the prices will skyrocket.

    So there’s need to satisfy current demand. This is also why push for EVs happened, to reduce our dependence on hydrocarbons.

    Also another option is that US could close the market and stop exporting, not that’s sure way to lose your allies.

    Against M4A…

    He did not manage to pass single payer though, so it is just promises

    And her top performance in a dem primary was 1% of the vote.

    Well trump campaign was hoping Biden stepping down would end up with infighting. This allowed to avoid that.

    It makes more sense as she is VP, she also can use Biden’s funds as it is also under her name and prevented infighting.
















  • It does. it does to this. That’s the docker image not the docker file. You are confusing the spec with the artifact. If you want reproducible dev envs you use a system like compose or any rad of other tools to launch images from your artifact store.

    You use them, make sure they are always pristine and cleaned after use, don’t have network connectivity and other things that could affect the build.

    Or you could use Nix which builds everything this way.

    Notice that you mentioned additional systems to achieve that, you wouldn’t need them if docker was truly providing it.

    LOL. We always have this problem if you have people only using spec files and not the artifacts. You are comparing apples to oranges by comparing the dockerfile to a build rpm package. Let me help you:

    An rpm package == docker image
    An rpm .spec file == dockerfile

    You if you only give people spec files and have them rebuild the package you will get different hashes of the rpm file. Similarly you would likely not change your spec file between releases and know your rpm file is going to be different.

    But that’s the whole point. A developer wants spec file to ALWAYS generate the same artifact. And most devs even believe that and get frustrated when it doesn’t (like in your example).

    Nix basically solves that. It even removes the need for tools like artifactory, because there’s no longer need for it. The code fully defines the final binary. Of course you don’t want to rebuild everything every time, so a cache is introduced.

    Before you say that it is just renaming artifactory. It really isn’t. It actually works like a cache. I can remove any piece of it, and the missing pieces will be rebuild if they are needed. It is also used by the builder, so it doesn’t repeat itself. I especially like it when working on feature branch and it completes the code. I eventually merge it, and if my merge did not modify code it won’t waste time rebuilding the same thing.


  • I see that too. Despite what most people say they aren’t truly interested in learning new things (at least things that would force them out of their comfort zones).

    I mean if team tries to move out then there’s not much one can do.

    Maybe they can look into using some tooling that whole isn’t nix, it uses nix under the hood and still prices some benefits.

    I heard about DevBox and Flox. Those at least try to provide a reproducible dev environment (note, I haven’t used them myself as I feel that the abstraction they do places limits on nix functionality, but then others might see it as a benefit)

    I also am getting impression that as time progresses things are getting smoother over time. With poetry2nix for example the big problem are packages that depend on C libraries, as those are not specified as python dependencies, so poetry2nix has a override file which adds them.

    Previously I very frequently had to update and contribute new packages there. I was a bit away from python as was assigned to work on a Go project for half a year and now starting to work on another python project and when tried to use it and things just worked. All I had to do was to use latest poetry2nix and my project then compiled to a working container.