![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
At least for me, there is a big difference between naming things at home and naming things for work.
Work “pet” machines get systematic names based on function, location, ownership and/or serial/asset numbers. There aren’t very many of them these days. If they are “cattle” then they get random names, and their build is ephemeral. If they go wrong or need an upgrade, they get rebuilt and their replacement build gets a new random name. Whether they are pets or cattle, the hostnames are secondary to tags and other metadata, and in most cases the tags are used to identify the machines in the first instance, because tags are far more flexible and descriptive than a hostname.
At home, where the number of machines is limited, I know all of them like the back of my hand, and it’s mostly just me touching them, whimsical names are where it’s at.
This is the end of official updates for them, they’re not bricked.
Older Chromebooks do have a shitty support lifecycle, it can’t be denied. Newer (post 2020 launch) Chromebooks come with at least 8 years of updates, although that’s from product launch, not from when you buy them. That is comparable to Apple’s support lifecycle.
It is possible to install ChromeOS Flex on out-of-support Chromebooks, though likely you will lose some features. You can also install generic Linux on them, but it’s got to be said it’s a slightly annoying experience.