tias

"Leads to a bad search experience for users" is Google speak for "they are seeing ads served by other companies than Google"

Kagi has good search results and they are presented well. It also has some useful features like forbidding certain sites and prioritizing others. I like that by paying I'm the customer and not the product. And their "small web" initiative is commendable.

That said, I've been a customer for nine months on an annual subscription, and I will not be renewing. The first reason is that I find them just too expensive for what they do. The second is that, even being that expensive, they're not breaking even. That undermines my trust in their future as a search engine and makes me less interested in paying a little extra for a good cause.

It's wild that they are not breaking even with these prices. I've had an annual subscription since January and made nearly 5000 searches. Extrapolating to a year, I will have been paying about $0.17 per search. If that would go to the electricity bill then it corresponds to about 1 kWh of energy per search, enough to run a 50-watt laptop PC for 20 hours.

We continue to see softening demand and macro headwinds in our core business

Maybe if you didn't raise your prices to finance dumb investments, the demand for your core business wouldn't falter.

If anything I think people's poor economy is forcing them to get rid of luxuries like Dropbox, and the way for Dropbox to stay relevant is to let prices follow the economy of their customers down.

It was promoted to me as a contender for Slack / IRC, not for the kind of direct messaging app that ICQ / MSN messenger was.

And then Jabber came to fix it by introducing an open protocol, and Google started supporting it, and all was well. But when everybody was using Google Chat they severed the Jabber compatibility, locking everyone in to their platform. Now we're back wading around in enshittified shit and Jabber is dead.

Only because bugs are defined as errors in implementation details. You can still have errors in your design (sometimes referred to as design bugs).

It's not about "entrusting" to AI any more than I would be entrusting important code to a junior developer to just go off and push to production on his own. We still have code review, pair programming etc. As I said, I read the output code, point out issues with it, and in the end make manual adjustments to fit what I want. It's just a way of building up the bulk of the code more quickly and then you refine it.

I'll confess I only skimmed the article, but it seems like just a bunch of unsubstantiated opinions and I don't buy it.

Using AI generated code is like pair programming with a junior programmer. You tell the junior what to do and then you correct their mistakes by telling them how to do better. In my experience, explaining things to someone else makes you better at your craft. Typically this cycle includes me changing the code manually at the end, and then possibly feeding it back to ChatGPT for another cycle of changes.

Apart from letting me realize and test my ideas quicker, this allows me to raise the abstraction level of my thinking. I can spend more time on architecture and on seeing the bigger picture, and less time being blinded by the nitty gritty details. I would say it makes me both a faster and a better programmer.

Global warming is already achieving that goal. It's a self-regulating system.

I knew it!

Indeed

I'm 98% sure you can still log in again, it just invalidates the access token that Reddit has received from Google. The effect is that when you log in next time you end up at Google's authorization screen where you have to explicitly give Reddit access again.