• 0 Posts
  • 50 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • I must have missed that negative sentiment entirely. I played all three and had no complaints. Did some searching, and apparently a lot of the gripes were related to levels being cut down in size / broken down into pieces to allow for a console release (strict memory requirements). Also I think they changed engines for the 3rd game, or at least a lot of people complain that movement and controls were worse in DS. I guess ignorance is bliss, cause I enjoyed them all.



  • Like you, OP, I benefited hugely from a car extended warranty. Audi hatchback, 4 year factory warranty was extended to 8 years for like $2k? Didn’t seem like a lot to spend for the added insurance in case something catastrophic happened. And something catastrophic did happen! In year 5, a factory sparkplug came apart and bits of it got sucked through the cylinder, gouged the cylinder walls, got sucked through the turbo, shattered all the turbo fins.

    Without the warranty the car would have been a write-off. The entire engine plus turbo were replaced under warranty. They don’t make that particular engine anymore so the replacement was used but had lower mileage. A lot of parts connected the engine are considered single-use by Audi as well. Engine mount pads, bolts, nuts, hoses, clamps, etc., their policy is to replace those parts when the engine is replaced. The list of parts replaced was four pages long.

    All told, between all the parts and labour I’d estimate it was at least a $20k repair. Utterly worth the $2k I paid on the extended warranty. Oh, and I had a loaner for about six months while they were sourcing the replacement engine, so six months of putting wear on someone else’s vehicle. Probably the best $2k I’ve ever spent.







  • Not the person you replied to, but I’m in agreement with them. I did tech hiring for some years for junior roles, and it was quite common to see applicants with a complete alphabet soup of certifications. More often than not, these cert-heavy applicants would show a complete lack of ability to apply that knowledge. For example they might have a network cert of some kind, yet were unable to competently answer a basic hypothetical like “what steps would you take to diagnose a network connection issue?” I suspect a lot of these applicants crammed for their many certifications, memorized known answers to typical questions, but never actually made any effort to put the knowledge to work. There’s nothing inherently wrong with certifications, but from past experience I’m always wary when I see a CV that’s heavy on certs but light on experience (which could be work experience or school or personal projects).


  • That’s just what happens to CEOs of publicly traded companies when they have a bad year. And Intel had a really bad year in 2024. I’m certainly hoping that their GPUs become serious competition for AMD and Nvidia, because consumers win when there’s robust competition. I don’t think Pat’s ousting had anything to do with GPUs though. The vast majority of Intel’s revenue comes from CPU sales and the news there was mostly bad in 2024. The Arrow Lake launch was mostly a flop, there were all sorts of revelations about overvolting and corrosion issues in Raptor Lake (13th and 14th gen Intel Core) CPUs, broadly speaking Intel is getting spanked by AMD in the enthusiast market and AMD has also just recently taken the lead in datacenter CPU sales. Intel maintains a strong lead in corporate desktop and laptop sales, but the overall trend for their CPU business is quite negative.

    One of Intel’s historical strength was their vertical integration, they designed and manufactured the CPUs. However Intel lost the tech lead to TSMC quite a while ago. One of Pat’s big early announcements was “IDM 2.0” (“Integrated Device Manufacturing 2.0”), which was supposed to address those problems and beef up Intel’s ability to keep pace with TSMC. It suffered a lot of delays, and Intel had to outsource all Arrow Lake manufacturing to TSMC in an effort to keep pace with AMD. I’d argue that’s the main reason Pat got turfed. He took a big swing to get Intel’s integrated design and manufacturing strategy back on track, and for the most part did not succeed.


  • Being a private company has allowed Valve to take some really big swings. Steam Deck is paying off handsomely, but it came after the relative failure of the Steam Controller, Steam Link and Steam Machines. With their software business stable, they can allow themselves to take big risks on the hardware side, learn what does and doesn’t work, then try again. At a publically traded company, CEO Gabe Newell probably gets forced out long before they get to the Steam Deck.


  • However, it’s worth mentioning that WireGuard is UDP only.

    That’s a very good point, which I completely overlooked.

    If you want something that “just works” under all conditions, then you’re looking at OpenVPN. Bonus, if you want to marginally improve the chance that everything just works, even in the most restrictive places (like hotel wifi), have your VPN used port 443 for TCP and 53 for UDP. These are the most heavily used ports for web and DNS. Meaning you VPN traffic will just “blend in” with normal internet noise (disclaimer: yes, deep packet inspection exists, but rustic hotel wifi’s aren’t going to be using it ;)

    Also good advice. In my case the VPN runs on my home server, there are no UDP restrictions of any kind on my home network and WireGuard is great in that scenario. For a mobile VPN solution where the network is not under your control and could be locked down in any number of ways, you’re definitely right that OpenVPN will be much more reliable when configured as you suggest.


  • I use WireGuard personally. OpenVPN has been around a long time, and is very configurable. That can be a benefit if you need some specific configuration, but it can also mean more opportunities to configure your connection in a less-secure way (e.g. selecting on older, less strong encryption algorithm). WireGuard is much newer and supports fewer options. For example it only does one encryption algorithm, but it’s one of the latest and most secure. WireGuard also tends to have faster transfer speeds, I believe because many of OpenVPN’s design choices were made long ago. Those design choices made sense for the processors available at the time, but simply aren’t as performant on modern multi core CPUs. WireGuard’s more recent design does a better job of taking advantage of modern processors so it tends to win speed benchmarks by a significant margin. That’s the primary reason I went with WireGuard.

    In terms of vulnerabilities, it’s tough to say which is better. OpenVPN has the longer track record of course, but its code base is an order of magnitude larger than WireGuard’s. More eyes have been looking at OpenVPN’s code for more time, but there’s more than 10x more OpenVPN code to look at. My personal feeling is that a leaner codebase is generally better for security, simply because there’s fewer lines of code in which vulnerabilities can lurk.

    If you do opt for OpenVPN, I believe UDP is generally better for performance. TCP support is mainly there for scenarios where UDP is blocked, or on dodgy connections where TCP’s more proactive handling of dropped packets can reduce the time before a lost packet gets retransmitted.





  • There are lots of wild foods that are poisonous, but that didn’t stop our ancestors from figuring out ways to make them edible. In the case of bitter almonds I can find a reference to baking and boiling being effective methods of reducing cyanide content. Cold leaching might also work but it would take a lot more time.

    I have to imagine that dire necessity was a catalyst for these discoveries. I’m guessing the thought process was more like “These are bitter as shit and they killed Bill, but we’re gonna starve to death if we don’t find some food, so let me try boiling these to see if the bitter goes away.”