After I read this article, I realized that I have a huge backlog of unplayed/partially played games in my steam library. Significant chunk of those games are from Indie devs. Probably enough games to last me a year or two. Plus, most of them seem like they will run just fine at max to high settings using my 3080 Ti on a 1440p display. Point is, I really need to stop looking for the next hardware refresh so I can keep playing newer big budget titles. This and current memory prices made it easy for me to forget about upgrading for the next 2-3 years.
Fair enough on that... I had just upgraded earlier in the year, so I'm set for the next 3-5 years at least, that said, I'll probably defer my usual mid-cycle gpu upgrade and hold onto my 9070xt for a while as well, I don't see GPU/Ram prices going back to normal for another 3+ years given how many data center rollouts are planned and mostly paid for in that timeframe. My bigger concern is actually going to be electricity costs in the face of those data center rollouts.
Not to mention actual AI fears since I've started playing with the latest Anthropic models (Claude Code), it's impressive and the field is still evolving rapidly. The job market is going to get worse IMO.
I got into ST about a year or so before samsung acquired them. Amazing ecosystem at the time and the ST community was great. I even taught my self groovy, so I could write my own device handlers. Then it went down hill couple of years after the acquisition. I still have my gen 2 ST hub and have been slowly trying to pivot towards HA. How easy is it to integrate ST into HA? I have a bunch older zwave wall switches and few other sensors that are tied into ST. But I really hate the ST app.
I was in the same boat at you and I found it super easy to use ST as the hub and HA as the brains until I decided to get Z-Wave/Zigbee dongles for my HA.
That said, I went to find the instructions to do it and it appears that Samsung broke the integration about a year ago and there still isn’t a solution. I’m sorry, it seems like I migrated fully just a few months before it stopped working and that explains the 1 device I still had on ST stopping working about a year ago (it wasn’t important and I never tracked it down).
I remember paying $250+ to some company out in CA and shipping my Xbox to them. Recommended by some friends. A week later it came back modded and a new HD installed. Along with a 10 page guide on how to use xbmc. Including mounting a remote windows share using smb. Or transfer the media files to the Xbox via FTP. This was around 2004. At the time, there wasn’t any easy way to play downloaded or ripped content on a TV from over the network. So a modded Xbox was a game changer.
The initial reaction was - What is that? How do you play the video? I happen to have a old VCR in storage and a USB 2.0 capture dongle. Hooked it up and showed them some old family videos. So their final comment was - why is the video quality so bad?
It's generally "how do I dial?", followed by them trying to press the holes in the dial, and, when told to rotate it, they rotate it to dial before picking up the handset.
I'm flattered, but you're only speculating, and at least for me this is not helpful.
It does not tell me what their reaction was, which is a little sad, because I am curious what happens when somebody for whom Facebook is ancient tech encounters video cassettes.
FWIW, I thought 8 inch floppies were weirdly big, but that's just a different form factor. It was normal to use floppies, tape or vinyl records for data and media storage. These days things are magically beamed through the sky in the most normal fashion. I think video tapes may seem a little weirder than just a larger box.
I played with this a bit today. Only downside is, no easy way to update containers yet. But on the other hand, no more dealing with macvlan or custom docker networks.
For some reason though that command updates all containers configured to auto-update (ex, "AutoUpdate=registry" in the quadlet file). It would be nice to be able to pass a container name after the command, but that is unsupported.
The idea is that your container image is the thing you want, and is (relatively) immutable, so you delete and create containers when you want things to change. If you need state you can do that with volume mounts, but the idea is that you don't need to 'update' a container, you just replace it with a new one.
That's also what docker compose does, under the hood. It doesn't 'update' a container, it just deletes it and recreates it with the new image and the same settings/name/ports/volumes/etc.
To the end user, this looks exactly the same as "updating".
If replacing a "regular" program that's just an executable and then restarting it is "updating", why isn't it the same for containers? Except theb the "executable" is the container image and the "running program" is the actual container.
Another level would be "immutable" distributions: would you say they don't "update", they just "download a fresh image to boot from"?
If we could already do it with some loadbalancer changes, I don't understand your comment that it was an incentive to move to containers.
Containers are separate from their deployment method. To be able to do those things with containers, some will go to docker, docker swarm, hashicorp nomad, or kubernetes.
So if people could already do these deployment methods, and given the HUGE organizational lift in training and platform investment for Ops to do that shift, your comment about those reasons being incentives to move to containers doesn't make sense.
I've been debating if I should move my frigate off an aging Unraid server to spare mini PC with Proxmox. The mini has a N97 with 16gb ram. How cameras do you have in your frigate instance on that N97? Just wondering if a N97 is capable of handling 4+ cameras. I do have a Coral TPU for inference & detection.
I have around 6 cameras, mostly 1080p, and about 8 GB RAM and 3 cores on the VM (plus Coral USB and Intel VAAPI). CPU usage is about 30 - 70% depending on how much activity there is. I also have other VMs on the machine running container services and misc stuff.
There are some camera stability issues which are probably WiFi related (2.4 GHz is overloaded) and Frigate also has its own issues (e.g. with detecting static objects as moving) but generally I’m happy with it. If I optimize my setup some more I could probably get it to a < 50% utilization.
Perfect thanks. I'll give the N97 a go and put it to good use as a dedicated frigate NVR box. It certainly has a much lower power draw than my Unraid server.
reply