Not even remotely true if you’re at all familiar with several massive hardware developments in the pipeline. People have been saying it’s the end of significant progress since 2010 and yet I’m playing what used to be 300w+ console games on a 2.5w A20 SoC. Ram will even come back down in 2-5 years. This is literally a company selling it. Ofc they’re going to embellish the demand and stretch their excessive revenue goals far into the future, they’re pumping stock.
You can lock unsupported drivers from being wiped at each upgrade, but I can highly recommend intel cards if you’re looking to switch to something with less maintenance. Sriov works a charm and they’re decent value for the money.
Matrix
Tailscale
Duck it!
🤔🤔🤔🤔🤔
Are we living in the same universe? In mine software doesn’t get patched all the time, in fact it’s usually a lack of patches that lead to any significant system compromise… Which happens time and time again. Also you’re on a thread that is advising hobbiests on how to configure and maintain their personal server, not the engineering meeting for a fortune 500. Yes, you can make ssh very secure. Yes, it’s very secure even by default. In the same regard, new vulnerabilities/exploits will be found, and it remains best practice not to expose ssh to raw internet unless absolutely necessary and with the considerations required to mitigate risk. Ssh isn’t even implemented identically on every device, so you literally cannot talk about it like you are. Idk why you’re arguing against the industry standard for best practices decided by people who have far more experience and engineering time than you or I.
I linked a relevant vulnerability, but even ignoring that, pragmatically, you feel they’d be targeting specific targets instead of just what they currently do? (That, by the way, is automating the compromise of vulnerable clients in mass scale to power botnets). Any service you open on your device to the internet is inherently risky. Ssh best practices are, and have been since the early days, not to expose it to the internet directly.
Doesn’t take that to leverage an unknown vulnerability in ssh like:
That’s why it’s common best practice to never expose ssh to raw internet if you can help it; but yes it’s not the most risky thing ever either.
Extreme surges in demand have happened before, and if you weren’t familiar the memory production market has actually always struggled with consistent long term demand, having several periods where they’d heavily cut production and investment. Which actually it’s worth saying there’s not much inherently special about Samsung/Sk/Micron beyond they had happened to have invested in the required R/D & Infrastructure to manufacture HBM at a time when it appeared to be far less lucrative. Memory was actually in such a surplus for the short time around covid prior to ai that they had implemented reduced production capacity. Now with the demand soaring in long term projections and a shortage in supply more will find it financially viable to accept the costs to enter the market, and the current 3 will ramp longterm supply even bringing full new fabs online. There’s scenarios where this isn’t the case, ofc, but it’s a general trend that has proven fairly reliable in modern industry and in specific the memory industry.
https://www.uncoveralpha.com/p/every-memory-cycle-ends-the-same
https://www.eetimes.com/dram-capex-to-plunge-28-in-2019/