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

help-circle





  • If I’m updating the source code already I might as well build my service from it, I really don’t see how building a docker container afterward makes it easier considering the update can also break compatibility with the docker environment.

    Also adapting can be a pita when the package is built around a really specific environment. Like if I see that the dockerfile installs a MySQL database can I instead connect it to my PostgreSQL database or is it completely not compatible? That’s not really something the dockerfile would tell me.


  • I have a love/hate relationship with docker. On one side it’s convenient to have a single line start for your services. On the other side as a self-hoster it made some developers rely only on docker meaning that deploying the stack from source is just an undocumented mess.

    Also following the log4j vulnerability I tend to prioritize building from source as some docker package were updated far later than the source code was.












  • In other words, you might not want to trust them because they killed off a Pixel Pass that 25 people signed up for, a Google Podcasts app that was basically a browser in an app shell that was given a proper replacement, a niche business presentation screen in Jamboard, and Stadia…freaking Stadia. They gave you all of your money back and let you keep the controller, guys.

    It’s not a good look when right off the bat it dismisses what is valid concerns by treating the opposition like they’re just whining.