thln666

it's because you can no longer write off depreciation costs for taxes after 5 years.

unless I am mistaken, you missed that the datacenter infrastructure being a one-time cost. nope. those servers have about a 5 year lifetime and then are likely to be replaced. The buildings aren't the expensive part. The GPUs are.

so I think that's one big miss from this blog, or I don't understand datacenters as well as I think I do (which is always a possibility! hopefully someone will inform me if I am wrong)

pangolin

I need my government to be run by some functioning adults, is that on this website?

The whole purpose of the Dockerfile is not to create a reproducible environment. The purpose of a Dockerfile is to run a bunch of commands inside of a container and save the output. Those commands may or may not produce the same output every time they're run.

For example, if you have a debian base container that you run `apt install nginx` in, what version you actually get depends on a lot of different things including what the current version of nginx is inside of the remote repositories you're installing from _when the docker build command is executed_, not when the Dockerfile is written.

So, if you do "docker build ." today, and then the same thing 6 months from now, you will probably not get the same thing. Thus, Dockerfiles are not reproducible without a lot of extra work.

Nix flakes are not like that - they tag _exact_ versions of every input in the flake.lock, so a build 6 months from now will give you the _exact same system_ as you have today, given the same input. This is the same as like an npm lock file or a fully-specified python requirements.txt (where you have each package with an ==<version>).

So, you definitely can make Dockerfiles reproducible, but again, the Dockerfile itself is not made to do that.

Hope that helps your understanding here!

I mean, GM was producing the first "modern" EV 24 years ago (1996) - and are one of the biggest traditional auto manufacturers with both a history of producing EVs/hybrids as well as a plan to introduce a large number of EVs across their brands. It's definitely not as fast as we'd all like, but I think the indication that they know ICE is limited lifespan (for a lot of reasons) is definitely built into GM's history and future. It's no Tesla as far as EV volume, capability, and product line - but they're definitely working on it (like the slow multi-million-vehicle-production-per-year company they are). I think it's hard to argue that GM has known about this and ignored the problem, though.

Anyway, disclaimer: I work for Cruise and so I'm clearly a shill for GM, so you can just ignore a lot of what I say because I'm 100% biased.

seriously? pretty easily. somebody probably left a debug log message in place or something. guaranteed that this happens all the time and most people don't report it.

I have thinkpads of various kinds for work and home and run linux mostly. MBPs do suck.

This is why I signed up.

So...like pex but worse?

https://github.com/pantsbuild/pex

"- Compile your own version of 'screen' from the git sources. Most versions have a slow scrolling on a vertical split or even no vertical split at all"

Or you could just use tmux which afaict is superior to screen in almost every way. http://tmux.sourceforge.net/