Oh my god yes. Why the hell do I have to open the notification shade to see the number, especially when it gets low?
It shouldn't be that hard to say, automatically show the number under a certain percentage. If it's 10% I have around an hour left of medium usage. If it's under 5% I have anywhere from 30 minutes to 5.
Just show me the number motherfucker, at least when it's important!
You're right, but I think you underestimate the intersection of what's theoretically possible and desperation.
We'll probably see multiple different things. Some of the equipment will be repurposed for other cloud GPU workloads. We'll probably see some companies try to make adapters and drivers to get the server hardware compatible with consumer desktops (there's someone who did a writeup, either on hacker news or hack a day who got older server RAM working on a desktop with an adapter and Linux tomfoolery). Buy up the stuff being sold at a loss, strap their adapter on it, and sell for profit.
But on a low level, all this shit is turing complete. There will be performance losses and considerable overhead, but in theory translation layers and emulation should be able to be written to effectively convert GPU compute to whatever other format is needed.
If it's taking a total loss vs squeezing the last squirts of profit out, I think there's going to be attempts to squeeze.
Yeah, I think that's the running theory of the corporate backup plan if/when AI falls through and they need to find a use for all the data center resources.
Not really. The cords are all the same inside, the colors are just for convenient matching of the ends.
If both ports are the same color, and wire has the same color on both ends, you're fine. You can send yellow through a red cable. I've definitely had a few times where all I had were a couple of loose cable pairs and it works fine.
You could a little with the later component cables where there were separate ones for the different colors, but the "original" composite cables (yellow, red, and white) only had one video cable and the other two were left and right sound. You could get odd patterns in the static with the sound plugged into the video port, but that was about it. Before that was the single coaxial cable that carried video and sound together, so there wasn't easily available messing with that without damaging the cable or doing magnetic or RF shenanigans against an unshielded cable.
That said, if you get into messing with some of the old hardware in different ways, you can get some real wild effects from those old analog media standards/hardware/cables.
There's small communities online doing stuff with it. Search for analog glitch art, analog data moshing, and circuit bending (although that last one is more abusing where digital circuits and hardware are susceptible to analog style weirdness due to basic physics of how electric signals work "analogly" between components).
Good job putting to words one of the core issues I've had with using LLM chat for work. Stop trying to design an entire fucking system or solution and just answer the damn question I actually asked, by using natural language to search documentation and existing implementations.
I would tell it to only answer exactly what I asked, but sometimes I do get value from it "exploring" on occasion. It's just so much damn worse with it than my newest junior co-worker who is known on our team for getting hours deep into tangential rabbit holes before coming up for air and asking seemingly nonsequiteur questions.
Doesn't help the conversation that some LLM chat systems call minor customization of the prompt making an agent.
Under duress I use CoPilot Chat at work. No, the basic sad customization I did along the lines of "don't be sycophantic, always cite sources, use these specific official documentation sites as sources before searching outside of them and clearly call out when you search outside them" that customization isn't making a damn agent, it's adjusting the prompt and saving those changes you disingenuous marketing fucks!
Dating just about forever
Looks to me like an out of focus shot of Joey, the guy that wrote the "a softer world" comics, sitting on the ground.
It's more of an artsy webcomic than necessarily a comedic one, although there are plenty of funny ones. Some of them are more musings about the world than anything else, as I feel this one is.
This is a particular message that stuck with me in the more than a decade since I first read it, and it's damn good advice.
Fair enough. I work in IT but endpoint config and group policy isn't my area at work, so most of my experience is with my personal computers at home. I at least usually hear the latest bullshit Microsoft is pulling from our endpoint management/config guy.
I should also bear in mind that I stripped down and customized the hell out of the install media before I last installed Windows on any of my devices, and I've run a shit ton of other customization/privacy/debloat tools afterwards as well. Usually by examining the policy and registry edits or PowerShell code they run and just picking and choosing parts for myself. Lots of good tools out there, but none I trust to do exactly what I want with no oversight or investigation.
I'd still say that Group Policy is usually the best option for configuration shit sticking though, due to it being Microsoft's "business side" solution for endpoint config for quite a while now.
-
It's simple, just make more money. /j