CountVon

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.

We need a pithy, demeaning nickname to sum this up, something that'll really get under his thin skin. I'll suggest PINO, "President In Name Only." Open to suggestions tho!

As a Canadian, I'm all for targeting red states where possible but I fully expect the blow back to hit all Americans. Tariffs are a relatively blunt instrument. If we put a 25% tariff on softwood lumber for example, I don't think we get to say that only purchasers in red states have to pay it. Every American purchaser has to pay an extra 25% for those 2x4s, or car parts, or potash, or crude oil, or electricity, or aluminum, or steel, or raw minerals. Those purchasers will inevitably download that cost onto their customers, which means that ultimately American consumers collectively are going to foot the bill.

Some of these Canadian response measures will even come back to harm Canadians! There are plenty of instances where Canadian companies sell raw materials to US companies and then Canadian consumers buy back finished products that incorporate some of those materials. As such, some of the added cost of Canadian tariffs is going to be paid by Canadian consumers. Regular citizens on both sides of the border are in the some boat, and Trump put us there with his stupid, stupid choice. Canadian or American, we would all do well to remember that because I'm sure that Trump would love nothing more than to see us divided and hating one another.

I'm sorry for the economic damage that this fight is going to cause all of us, on both sides of the border. Please remember that Trump started this fight, and Canada will not roll over. I think Liberal leadership candidate Mark Carney summed it up best in this BBC interview. The whole interview is worth a watch, but the link goes to the highlight to which I'm referring. Here's the transcript of that highlight:

Interviewer: It's pretty clear that [Trump] thinks [Canada] can be pushed around.

Carney: We can't.

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.

Likely coffee that was grown somewhere else, roasted in Canada and later sold to someone in the US.

This bill might have been well-meaning, but it's honestly not realistic to put solar panels on every home. Some homes just aren't well sited to get full benefit from solar panels, especially when you're far from the equator. I would love to have solar panels on my house, and my government has reimbursement programs available for solar panel installs so I went seeking quotes. Unfortunately I was told point blank by multiple installers that the panels wouldn't offset their own cost in my situation. Too much tree shade, not enough roof slope facing the equator. Disappointing, but I'd rather see those panels get installed on homes that can make the most of them.

Except the car's HVAC system passes air through a filter. How much of a difference that makes is going to depend on the type of filter and whether it's been changed sufficiently often, but it's definitely doing more than nothing.

The next tech bubble, IMO.

Gosh, it's like companies in a capitalist economy have absolutely no moral center whatsoever and will do whatever they can get away with to maximize profits!