Monday, July 29
Daily News Stuff 29 July 2024
Bit Rot Edition
Bit Rot Edition
Top Story
- AMD's Zen 5 laptop chips are here. In particular, the (deep breath) Ryzen AI 9 HX 370.
Anandtech reviews the Asus Zenbook S 16.
Tom's Hardware reviews the Asus Zenbook S 16.
Notebook Check reviews the Asus Zenbook S 16.
And Phoronix reviews the Asus Zenbook S 16 - but this time under Linux.
You might be thinking that there are limited options available to the consumer at this precise moment, and you might be right.
This is a pretty good laptop and the benchmark scores are solid, but it lacks the Four Essential Keys so it is dead to me.
Tech News
- AMD's desktop CPU delay might not be due to an issue with the chips, but an issue with the labels on the chips. (Tom's Hardware)
Ryzen 5 9600X and Ryzen 7 9700X samples have been spotted marked as Ryzen 9. If that's all it is, then it's still a thousand times better than anything Intel has done.
- Like the latest report from Intel that the fatal CPU degradation problem affects mid-range 65W chips and not just the high-end parts previously listed. (Tom's Hardware)
So everything from the past two years could be toast, except the entry-level 13100 and 14100.What's troubling is that Intel has not and will not issue a recall for the affected CPUs. It also hasn’t halted processor sales pending the updated microcode rolling out.
Way to go, Intel. - Dragon Age: The Veilguard took this long because Bioware wanted to get it right. (WCCFTech)
The game looks terrible.
- The New Internet. (Tailscale)
Okay, it's basically a sales pitch. But it's a sales pitch written by an engineer who's been in the industry for 25 or 30 years and who has seen some shit, man, and kids these days, let me tell you...
And I'm here for that.
Posted by: Pixy Misa at
07:05 PM
| Comments (4)
| Add Comment
| Trackbacks (Suck)
Post contains 316 words, total size 3 kb.
1
Re: Tailscale - I was wondering about this the other day. I had been trying to think of ways to get computers to communicate with each other as peers. I actually run my own servers from my house and pay "business internet" to give me a static IP address. It sounds saner to me than paying AWS to rent me a processor by the instruction.
It also sounds like the sort of thing IPv6 was supposed to fix. Why isn't IPv6 fixing anything? Theoretically everyone can have their own static IP at that point for every computer we crank out.
It also sounds like the sort of thing IPv6 was supposed to fix. Why isn't IPv6 fixing anything? Theoretically everyone can have their own static IP at that point for every computer we crank out.
Posted by: madrocketsci at Monday, July 29 2024 09:50 PM (hRoyQ)
2
Well, I think with IPv6, you can have a /64 for every atom in the known universe. Also, I do agree with the whole "every node is a peer", sorta like the internet before the Web took over: everybody has a .plan, every node runs fingerd, and ftpd (at a bare minimum), and probably rsyncd for good measure. How-the-ever: the idea of using HTTPS for everything is silly. We have a thousand-some-odd various protocols, an awful lot of which have a secure version, and the rest could be extended. We don't need to just bodge everything through HTTPS! (any more like than the risible article I read the other day on using SSH for _everything_, including picking up dog shit and washing your car)
Posted by: normal at Monday, July 29 2024 11:18 PM (LADmw)
3
It's good adcopy, because I have a 'shut up, and take my money' reaction without thinking over whether I have an actual use case. I don't have a use case, or money, but it does still sound worth thinking about.
Posted by: PatBuckman at Tuesday, July 30 2024 03:13 AM (rcPLc)
4
Now that I'm thinking about it: How does routing work with IPv6 anyway? If your IP address is an arbitrary number that has nothing to do with the network topology, how do packets find their way across the network?
Posted by: madrocketsci at Tuesday, July 30 2024 08:27 AM (hRoyQ)
52kb generated in CPU 0.0224, elapsed 0.4919 seconds.
58 queries taking 0.4803 seconds, 349 records returned.
Powered by Minx 1.1.6c-pink.
58 queries taking 0.4803 seconds, 349 records returned.
Powered by Minx 1.1.6c-pink.