Next.js is a poor choice for a client-side application. It is first and foremost a server-side framework, and trying to force it to be client-side is to work against it. There are so many better options than Next.js for dedicated client-side front-ends.
In the past I've purchased a rail pass because I figured it'd be more economical but last trip we just got a couple of IC cards and just booked our shinkansen and that was honestly the best experience. The problem with the rail pass was that it could only be used on some services, and the IC card was usable on most. The most confusing thing is just figuring out which local transport companies have a slightly different network, but it was honestly not bad.
New Reddit is too. They were A/B testing it for a while, but now you can't use it without the login pop-up after a short timespan. The funny thing is, it has nothing to do with how much content you view. So if you really want to read something, you can hit F5 and scroll back down every time the pop-up is shown. Still not worth it. But honestly, Reddit content has taken such a plummeting nose dive over the last few years, this just feels like a final reminder that it's time to move on.
Cynically, I think the purpose is to inflate page view counts. You refresh 10x to read the comments, they report 10x user engagement, and high five each other over successfully meeting their KPIs.
I think gradual rollout is underrecognised as the utterly devious way of implementing user-hostile changes that it is. It doesn't take a lot of scrolling through the comments here to find instances of people who are unaffected by some change or another being inexplicably hostile towards posters who are, implicitly accusing them of anything from incompetence to drama-mongering and misinformation. In that way, some of those who would complain about a change are worn down early on, and by the time the change is rolled out to more people they have already resigned and moved on, preventing a critical mass of opposition from forming.
Yes, it's a kind of boiling the frog where instead of slowly cranking up the degree of enshittification you do it with the number of affected users instead. In both cases the goal is to avoid a critical mass of user outrage.
A/B tests in general should require informed consent just like any other study on human participants. But then most software developers don't care about ethics so this is nothing new.
That's the magic of A/B testing. You get to send an entire "B" group into paranoia and upset about the change they didn't want/like while everyone in "A" gets to gaslight B that B isn't experiencing what they're getting and that it would never happen to A...
To what end? We're discussing this on a post about the equivalent for another platform being (hopefully temporarily) shutdown so this will never be a reliable long term solution.
All the time? It wasn't working for me using tor-browser, nor Brave. I was only a reader of Reddit. I'm on fediverse/Lemmy, mainly https://old.lemmy.world which feels very familiar!
I've not taken the effort to understand fediverse yet, but it feels very old-internet.
I find this struggle with coding too. When Claude spits out a plan I have to really focus to not skim over the details. It's also difficult to parse the plan because I have to work backwards to determine if the high level context matches my understanding of what Claude will do.
Louis is quite vocal about transparency for consumers and openly sharing knowledge for people to be able to do repairs themselves or even set up a competing business.
I built a new main rig in November because I saw the memory prices going up. I overpaid about AUD$110 above its RRP. The same kit is now AUD$610 above RRP from the same retailer.
Here's hoping I can wait out the current shortage before any upgrades (I typically only upgrade every 5-7 years or so anyway) or replacements, because I do not plan to pay the new price.
Hacker news generally follows trends, and this is the current trend.
The discussion around coding agents nowadays is steering towards harnesses (which is probably a better description of what this is). "Agent" here is doing a lot of heavy lifting and has become a bit of a catch-all term to describe a model + harness + tooling + prompt + some other things that I've probably not thought about. The harness is a part that's being explored more as many believe it's where we can get some better performance out of the models.
This one in particular is from Vercel who provide a service to use models, so they have a vested interest in providing a harness.
reply