Zanfa

> This has changed recently

I've probably heard "this time is different" on the topic of PC laptops catching up to Macs a hundred times over the last decade, but it never is...

It's hard to rebuild trust after selling a computer (without a CD drive) without networking drivers and no indication of which wireless chipset it has, but including a CD with said drivers.

Google's search AI clearly trades accuracy for speed and it shows. It frequently draws the exact opposite conclusions from the sources it references.

Behold the View.java[0] at 34k lines of human code. IIRC it’s slimmed down a bit these days and used to be more.

[0] https://android.googlesource.com/platform/frameworks/base/+/...

Yes. Most (even cheap-ish) greenhouse kits come with them, at least the ones I've seen around here.

> What's always conveniently left out of lists like this is the greater context in which it occurred. Any state will go to great lengths to protect themselves and ensure their survival.

Putin isn’t worried about Russia’s survival or livelihoods. The country would’ve been an even richer Norway with all the natural resources and opportunity to trade with both mature European and emerging Asian countries. Instead they can’t even go a decade without invading any neighboring countries or a week of not threatening nuclear annihilation. It’s a national inferiority complex.

When I first unboxed a new V15, I thought I got a cheap knockoff instead of the real thing. That’s how cheap Dyson plastics look and feel.

Doesn't this usually just mean saying "I take full responsibility" and then firing a bunch of unrelated people?

But you can do equally horrible inheritance-y things with embedded structs.

I will never understand the obsession to build terrible SPAs to replace existing UIs, that are, without exception, worse than the original.

But I guess Reddit had a good run and all things must come to an end.

Wish they spent some AI tokens on that abomination to fix at least some of the countless issues it has, because their human engineers definitely won’t.

To be fair, induction doesn’t heat the sides of the pan at all. So carbon steel pans are more annoying to use and keep uniformly seasoned. Woks don’t really work by default either. It’s also more susceptible to slightly warped pans exacerbating uneven heating.

I’m skeptical about the reasoning being regulations. There are still a few Italian manufacturers who have a combined oven & stovetop models (“range” in US terms) including induction, but they’re really expensive and with questionable reliability / warranty support. I think all manufacturers just care about cutting costs and putting out a “sleak” design.

I can’t wait for knobs to make a comeback.

This! The only electric (induction or otherwise) stovetops are either bottom of the barrel portable or top of the line commercial models. Everything in between is capacitive touch garbage.

And can’t forget Metaverse and the $70B Meta sunk into it either.

I have a similar one. Is Claude Code (web and/or VS Code) still a buggy mess? Pretty much every single agent loop bugs out and requires a hard refresh, which sometimes still doesn’t help. And they have an effectively infinite LLM budget and unreleased models to fix the issues.

The problem is still long periods (up to weeks) of single-digit percentage of nominal capacity of power generation from wind farms. Overbuilding doesn’t help much, so a non-renewable option still needs to be available.

> In fact, the complexity of Chat Messages and Notifications synchronisation is one of the prime reasons why React exists.

Which makes it even more ironic that in the 10 years since React was announced in 2013 and when I quit Facebook, they never managed to fix the original state synchronization bug that they demonstrated in the original React announcement for more than a few months at a time at best.

I'm sure technically it wasn't a singular bug over the years and the causes were complex, but React did fuck all in relation to the unread message counter being correct.

It hasn't even been a few weeks since I had AI use a button + onClick handler for navigation instead of a simple anchor tag...

Not to mention that effectively reviewing code is a much more difficult skill than writing it. Without a good mental map of how it affects other parts of the system, it’s basically a rubber stamping ceremony.

Github’s poor PR UI doesn’t help either, there’s limited tooling to navigate around the codebase not directly changed (but affected) to identify and highlight problems.

> Over time the gems will rise to the top

I’m not sure this can be assumed. Discovery was already one of the biggest hurdles when releases were bottlenecked by human output. Increasing output 10x is only going to make it worse.

Same as with Google, where they’ve lost the SEO war against AI spammers and valuable content has become close to impossible to find.

This seems exactly backwards. Most commits should not exist, because the majority of people can't already help themselves from committing "wip" "fix lint", let alone anything more granular.

I don't know what NPM is doing, but yarn installs deps much faster than NPM

Can you elaborate about the practical value of having the history of back and forth, in a PR or even in the commit log? In my 20ish years of experience, I can’t recall a single instance where I’ve solved something thanks to having this work-in-progress state persisted in the repo history.

It’s exclusively been the other way around where having a smaller number of larger squished commits (post merge) that’s made the project be more maintainable.

It’s not that. The sort of issues all of the above have caused are fundamental, eg not using anchor tags for navigation. It’s not in any way easier to use a button or div with an onclick handler. It’s also not easier to serve megabytes of JS to render 5kb of comments.

> You hate BAD react SPAs that break the fundamentals of how the web works.

But that’s all of them? If Github, Reddit, LinkedIn and Facebook and others are unable to build SPAs that don’t constantly break the fundamentals while also choking the browser, maybe it is a tech problem.

Not surprising. It’s placed exactly where the regular search results used to be (when navigating away from image results) and muscle memory is strong. Haven’t clicked it intentionally once though.

There are external devices that can be attached to the camera to record gyro data, e.g https://docs.gyroflow.xyz/app/advanced-usage/using-external-... I just ordered one a few weeks ago and haven't received it yet, so can't talk about personal experience, but there's no technical reason it couldn't work well.

It's been awhile, but the best experience I've had desoldering ICs with many pins was with JBCs hot air extractors. They're little metal funnels you put around the component you want to desolder to contain hot air, with a tiny suction cup to lift the part once solder starts to melt.

JBCs stations are expensive though, but you should be able to use just the heat deflectors and a pair of tweezers, rather than a vacuum pump as long as you already have a hot air station.

> Outright lie about the problem and the scope of it.

One of my favorites was “EU is banning juice”, when the definition of juice was being standardized and local producers of fruit-flavored sugar water couldn’t keep selling their beverages as “juice” anymore.

> It’s always been interesting to me that multi-million and even billion dollar tech companies don’t have perfect websites in terms of UX.

This, but for online shops, especially clothing. Horrendously buggy, laggy, with broken navigation (especially when navigating back), filters that don't work on > 95% of online stores. Why they wouldn't fix their primary (or at the very least highest margin) income stream is beyond me, but I've had to abandon so many shopping carts just because the checkout flow is literally broken.