• 0 Posts
  • 220 Comments
Joined 7 months ago
cake
Cake day: March 8th, 2024

help-circle
  • Isn’t this pretty much the same system Google was intending to implement on Chrome before backtracking? That’s my understanding anyway.

    Ultimately the issue is that we’ve gone to extremes. The response to the data market that runs the Internet is now that many people are against ANY amount of information being dislodged from users to anybody else. That is obviously way more strict than pre-internet standards, when people’s location data was widely available and TV advertising ran a whole lot of live reporting and segmentation data, but it has become the goal.

    Mozilla (and Apple, and for a bit Google), are suggesting to go back to a world where someone quietly aggregates some info without tracking individuals in excruciating detail and now advertisers don’t want to lose the granularity and resell ability of the spy-level data gathering… and users don’t want to give up even aggregated info.

    We’ve scorched the earth so badly there is no path forward, so we stay where we are. I have no moral stance on this, but it seems to be what’s happening.





  • Let me agree with you explicitly on loving the return to a sane power configuration here. I was watching Hardware Unboxed’s retest of this after the patches and it takes almost fifteen minutes of them reiterating that the 9700X and the 14700K are tied for performance and price before they even mention the bombshell that the 9700X is doing that with about half the wattage.

    The fact that we keep pushing reviews and benchmarks focused strictly on pedal-to-the-metal overclocked performance and nothing else is such a disgrace. I made the mistake to buy into a 13700K and I have it under lower than out of box power limits manually both to prevent longevity issues and because this damn computer is more effective as a hair dryer than anything else.

    We don’t mention it much because Intel was in the process of catching on actual fire at the same time, but the way this generation has been marketed, presented to reviewers, supported and eventually reviewed has been a massive trainwreck, considering the performance of the actual product.


  • He shipped enough clunkers (and terrible design decisions) that I never bought the mythification of Jobs.

    In any case, the Deck is a different beast. For one, it’s the second attempt. Remember Steam Machines? But also, it’s very much an iteration on pre-existing products where its biggest asset is pushing having an endless budget and first party control of the platform to use scale for a pricing advantage.

    It does prove that the system itself is not the problem, in case we hadn’t picked up on that with Android and ChromeOS. The issue is having a do-everything free system where some of the do-everything requires you to intervene. That’s not how most people use Windows (or Android, or ChromeOS), and it’s definitely not how you use any part of SteamOS unless you want to tinker past the official support, either. That’s the big lesson, I think. Valve isn’t even trying to push Linux, beyond their Microsoft blood feud. As with Google, it’s just a convenient stepping stone in their product design.

    What the mainline Linux developer community can learn from it, IMO, is that for onboarding coupling the software and hardware very closely is important and Linux should find a way to do that on more product categories, even if it is by partnering with manufacturers that won’t do it themselves.




  • So an interesting thing about this is that the reasons Gemini sucks are… kind of entirely unrelated to LLM stuff. It’s just a terrible assistant.

    And I get the overlap there, it’s probably hard to keep a LLM reined in enough to let it have access to a bunch of the stuff that Assistant did, maybe. But still, why Gemini is unable to take notes seems entirely unrelated to any AI crap, that’s probably the top thing a chatbot should be great at. In fact, in things like those, related to just integrating a set of actions in an app, the LLM should just be the text parser. Assistant was already doing enough machine learning stuff to handle text commands, nothing there is fundamentally different.

    So yeah, I’m confused by how much Gemini sucks at things that have nothing to do with its chatbotty stuff, and if Google is going to start phasing out Assistant I sure hope they fix those parts at least. I use Assistant for note taking almost exclusively (because frankly, who cares about interacting with your phone using voice for anything else, barring perhaps a quick search). Gemini has one job and zero reasons why it can’t do it. And it still really can’t do it.


  • I genuinely think Linux misses a beat by not having a widely available distro that is a) very closely tied to specific hardware and b) mostly focused on web browsing and media watching. It’s kinda nuts and a knock on Linux devs that Google is running away with that segment through both Android and ChromeOS. My parents aren’t on Windows anymore but for convenience purposes the device that does that for them is a Samsung tablet.


  • I keep trying to explain how Linux advocacy gets the challenges of mainstream Linux usage wrong and, while I appreciate the fresh take here, I’m afraid that’s still the case.

    Effectively this guide is: lightly compromise your Windows experience for a while until you’re ready, followed by “here’s a bunch of alien concepts you don’t know or care about and actively disprove the idea that it’s all about the app alternatives.”

    I understand why this doesn’t read that way to the “community”, but parse it as an outsider for a moment. What’s a snap? Why are they bad? Why would I hate updates? Aren’t updates automatic as they are in Windows? Why would I ever pick the hardware-incompatible distros? What’s the tradeoff supposed to be, does that imply there is a downside to Mint over Ubuntu? It sure feels like I need to think about this picking a distro thing a lot more than the headline suggested. Also, what’s a DE and how is that different to a distro? Did they just say I need a virtual machine to test these DE things before I can find one that works? WTF is that about?

    Look, I keep trying to articulate the key misunderstanding and it’s genuinely hard. I think the best way to put it is that all these “switch to Linux, it’s fun!” guides are all trying to onboard users to a world of fun tinkering as a hobby. And that’s great, it IS fun to tinker as a hobby, to some people. But that’s not the reason people use Windows.

    If you’re on Windows and mildly frustrated about whatever MS is doing that week, the thing you want is a one button install that does everything for you, works first time and requires zero tinkering in the first place. App substitutes are whatever, UI changes and different choices in different DEs are trivial to adapt to (honestly, it’s all mostly Windows-like or Mac-like, clearly normies don’t particularly struggle with that). But if you’re out there introducing even a hint of arguments about multiple technical choices, competing standards for app packages or VMs being used to test out different desktop environments you’re kinda missing the point of what’s keeping the average user from stepping away from their mainstream commercial OS.

    In fairness, this isn’t the guide’s fault, it’s all intrinsic to the Linux desktop ecosystem. It IS more cumbersome and convoluted from that perspective. If you ask me, the real advice I would have for a Windows user that wants to consider swapping would be: get a device that comes with a dedicated Linux setup out of the box. Seriously, go get a Steam Deck, go get a System76 laptop, a Raspberry Pi or whatever else you can find out there that has some flavor of Linux built specifically for it and use that for a bit. That bypasses 100% of this crap and just works out of the box, the way Android or ChromeOS work out of the box. You’ll get to know whether that’s for you much quicker, more organically and with much less of a hassle that way… at the cost of needing new hardware. But hey, on the plus side, new hardware!




  • Oh, I absolutely could have. It would lose a couple of cores, but the 13th gen is pretty linear, it would have performed more or less the same.

    Thing is, I couldn’t have known that then, could I? Chip reviews aren’t aiming at normalizing for temps, everybody is reviewing for moar pahwah. So is there a way for me to know that gimping this chip to run silently basically gets me a slightly overclocked 13600K? Not really. Do I know, even at this point, that getting a 13600K wouldn’t deliver the same performance but require my fans to be back to sounding noticeable? I don’t know that.

    Because the actual performance of these is not to a reliable spec other than “run flat out and see how much heat your thermal solution can soak” there is no good way to evaluate these for applications that aren’t just that without buying them and checking. Maybe I could have saved a hundred bucks. Maybe not. Who knows?

    This is less of a problem if you buy laptops, but for casual DIY I frankly find the current status quo absurd.




  • “Clearly damaged” is an interesting problem. The CPU would crash 100% of the time on the default settings for the motherboard, but if you remember, they issued a patch already.

    I patched. And guess what, with the new Intel Defaults it doesn’t crash anymore. But it suddenly runs very hot instead. Like, weird hot. On a liquid cooling system it’s thermal throttling when before it wouldn’t come even close. Won’t crash, though.

    So is it human error? Did I incorrectly mount my cooling? I’d say probably not, considering it ran cool enough pre-patch until it became unstable and it runs cool enough now with a manual downclock. But is that enough for Intel to issue a replacement if the system isn’t unstable? More importantly, do I want to have that fight with them now or to wait and see if their upcoming patch, which allegedly will fix whatever incorrect voltage requests the CPU is making, fixes the overheating issue? Because I work on this thing, I can’t just chuck it in a box, send it to Intel and wait. I need to be up and running immediately.

    So yeah, it sucks either way, but it would suck a lot less if Intel was willing to flag a range of CPUs as being eligible for a recall.

    As I see it right now, the order of operations is to wait for the upcoming patch, retest the default settings after the patch and if the behavior seems incorrect contact Intel for a replacement. I just wish they would make it clearer what that process is going to be and who is eligible for one.



  • I mean, happy for you, but in the real world a 200 extra dollars for a 400 dollar part is a huge price spike.

    Never mind that, be happy for me, I actually went for a higher spec than that when I got this PC because I figured I’d get at least one CPU upgrade out of this motherboard, since it was early days of DDR5 and it seemed like I’d be able to both buy faster RAM and a faster CPU to keep my device up to date. So yeah, it was more expensive than that.

    And hey, caveat emptor, futureproofing is a risky, expensive game on PCs. I was ready for a new technology to make me upgrade anyway, if we suddenly figured out endless storage or instant RAM or whatever. Doesn’t mean it isn’t crappy to suddenly make upgrading my CPU almost twice as expensive because Intel sucks at their one job.


  • The article is… not wrong, but oversimplifying. There seem to be multiple faults at play here, some would continue to degrade, others would prevent you from recovering some performance threshold, but may be prevented from further damage, others may be solved. Yes, degradation of the chip may be irreversible, if it’s due to the oxidation problem or due to the incorrect voltages having cuased damage, but presumably in some cases the chip would continue to work stable and not degenerate further with the microcode fixes.

    But yes, agreed, the situation sucks and Intel should be out there disclosing a range of affected chips by at least the confirmed physical defect and allowing a streamlined recall of affected devices, not saying “start an RMA process and we’ll look into it”.