

If you are a company the size of Microsoft, you have more than enough resources to test absolutely everything.


If you are a company the size of Microsoft, you have more than enough resources to test absolutely everything.


Like other people have said, it’s going to depend on what you want to do with the NAS. If it’s going to be a pure NAS (ie network storage only), then using onboard will be fine. If you plan on doing other things (home assistant, media server, etc), I recommend going the virtual machine + HBA route.


I used a hodge-podge of chinesium parts and leftover drives to create a DAS system that hooks up to an HBA via DAC. I’m actually kinda surprised how stable it’s all been.


At this point, I’ve seen far more people being almost violently anti-rust than I’ve seen people being weirdly enthusiastic about rust. If Rust people are Jehovah’s Witnesses, then a lot of the anti-Rust people are ISIS.


This is equipment that uses all statically addressed devices. And ignoring the fact that IPv6 is simply unsupported on most of them, there are duplicate machines that share programs. Regardless of IP version you need NAT anyway if you want to be able to reach each of the duplicates from the plant network.


We use NAT all the time in industrial settings. Makes it so you can have select devices communicate with the plant level network, while keeping everything else common so that downtime is reduced when equipment inevitably fails.


Many people do this.
Many people are insane.


The loyal cult is the result of Stockholm syndrome.


If it happens after an hour of playing, it sounds like a heat issue. Restarting the game drops the load for a minute allowing things to cool.


Every application kind of needs two modes: a default mode where the user is railroaded into making the right decision, and an “I’m not an idiot and will actually read the documentation before/after trying to make things work” mode. If you stick the toggle for the two modes somewhere that you’d only find by reading the documentation, people will automatically categorize themselves into the mode the ought to be in.
I have a “server” cobbled together out of old PC parts. I have proxmox running on it and Home Assistant is one of the VMs running on that machine.


I assume lack of demand. In your own home, you’d be keeping the handle clean, and public washrooms often use the touchless sensor types.


People also just need to be more selective about where and how they automate.
For example, I wanted my coffee to automatically start in the morning. So instead of buying a “smart” coffee maker, I bought the dumbest possible one and a smart switch. Now, no matter what happens with that switch, the worst that can happen is I have to manually hit a button to get coffee.
I’ve been seeing it pop up more in embedded/PC based devices. Seems to be replacing Windows XP and the other embedded Windows versions. Guess Microsoft wants too much for those licenses.


I’m not asking everyone to be able to become a hardware specialist, but if you can’t even figure out “my computer gets hot” I’m not going to be able to trust anything you do. Identifying a heat issue does not take a rocket surgeon.


Could be a gen 5 nvme drive without adequate cooling. Them bastards can run hot. Especially the early gen 5 drives.


Yes, but this may be a symptom of an issue I’ve been seeing with younger programmers; they’ve siloed themselves so specifically into whatever programming they “specialize” in, that they become absolutely useless at dealing with absolutely anything else related to their job. And exasperating this issue is the fact that they’ve grown up with systems that “just work”. Windows, iOS, and android are all at the point where fucking around with hardware issues is very uncommon for the average person.
Asking this guy to solve a hardware problem is like asking hime to tune a carburetor. He likely has not the slightest clue how to start.


Measuring my server cluster
Personally, I just don’t ask questions I don’t want the answer to.


Masking the cost of the Windows license is my guess.
If what you currently have already works for you, why be concerned with the form factor of something designed for a slightly different use case?