They actually support right to repair laws. The joke is that they will make their hardware so difficult to repair that they are the only ones who can do it.
dandroid
joined 1 year ago
This is a good start, but I think there also needs to be a way to browse all the images stored and shred them.
This exact thing happened to me. They were canceling our project. :(
Luckily none of us lost our jobs. We all just got assigned to different projects/teams.
I despise Docker Desktop. Before I knew anything about docker or containers, all I knew was that it was in the required software list for my work for building our software. All I knew was that if it wasn't open, my build would fail and if it was open, my laptop would slow down to a crawl.
Eventually I took classes on Docker for work and learned quite a bit about it. I learned that I could use docker from command line with no UI, and I wouldn't take anywhere near the performance hit. I eventually linked my IDE docker runtime to podman running on WSL2. Now I take pretty much no noticable performance hit.
TL;DR: you can replace Docker Desktop with WSL2 command line commands and have no UI.
I always squash my commits before rebasing. Is your way easier? I never really seem to have a problem with merge conflicts.
Totally agreed the run time difference matters sometimes. In my experience it's hasn't been the case for scripts, as they are generally small in scope in comparison to C++ applications.
I'll take a look at Click. Something better than argparse definitely piques my interest, because while the features are great, it feels a little cumbersome at times.
So you're wasting hours of development time to save a couple of milliseconds of run time.
If that's your only criteria for choosing a language, you're gonna have a bad time.
Do you do any scripts beyond extremely simple ones?
I do a fuck ton of scripting in both bash and python. I never want to do string manipulation in bash. As soon as string manipulation is required, I automatically choose python for a script. Also, if I need named arguments or multiple levels of arguments for subcommands. You can use sys.argv for basic args, which isn't any harder than bash arguments, but for complex inputs, argparse is a godsend. It has a bit of a learning curve, but it can handle anything. Bash requires you to write complex arg handling manually with loops and reducing.
I don't use python too often, but I need to use it every once in a while. Every fucking time I get the red squiggly under "true" and I'm sitting there for a second like, "...the fuck??? Ohhhhh, right."
Every time.
Gaming support on Linux is the best it has ever been. Other than select games, nearly everything works now. It's mostly competitive multiplayer games that don't work because it's the kernel anticheat that is the issue. Notably, Call of Duty and Destiny 2 don't work. Halo does 100% work now, which is awesome. But if you mostly play single player games, you are probably totally fine.
Can we please not do that here?