Kagi is good, but only for English language queries

I use it for Finnish all the time and it is comparable to Google I would say.

I find it great for Japanese, provided you search in the Japanese language mode.

How do you set it to search in Japanese language mode?

Second filter from the left on the results page is the location / language filter.

It's just a fun reference to a song/psa ad called "Dumb Ways To Die"

oh, wasn't aware of the song so i missed that entirely :)

I ran to the comments with this question

This markdown mirror is a partial solution to a problem that does not exist in "normal" Logseq (what's being rebranded to Logseq OG). The markdown files ARE the data (which syncs beautifully over Dropbox and the like.)

I am a Logseq user and I was under the impression that development had stalled or better, stabilized (frankly, most software does NOT need a constant stream of updates). Based on this post, it looks like they're back - and they've chugged some vibe juice.

Code is not spec. There is an implementation spectrum.

On one end, you have code that can perform only the behaviour explicitly declared in the spec, but has to be thrown away and rewritten for any new or updated spec.

On the other end, you have code that implements or anticipates a wide range of future possible specs including the given one.

The AI can operate on any point on this spectrum, but it's not very good at choosing. The more complex the software, the more such choices need to be made.

When the number of bad choices reaches a certain critical mass, even a skilled engineer becomes powerless to undo all the bad choices, and even a powerful model becomes unable to reduce it back to a coherent spec.

Turning you into a "reverse centaur" to borrow a term from Cory Doctorow

Sounds like a good system. To use the analogy from ths other comment, this would be like running an image through JPEG compression twice.

The issue happens then if you're updating the individual research files on a regular basis. (Or making a long series of commits on a starting code base.) Every edit has a chance of doing a drive-by cleanup on nearby lines. Over a long enough timeline, it'll ablate your logic into something featureless, like if you compress an image too many times.

I do remember early SourceForge. It remember it as very clean, simple and reliable, and popular.

Not popular. Core. It was the trusted place for open source software. Then it was ads. Then the day they bundled there was a MASS exodus. And the 14 people who ran their own source code interfaces scoffed and said "see. I told you." And we all said "yup" - we knew something would happen one day, but that was a worst-case-scenario that few thought was even a remote possibility.

> And the 14 people who ran their own source code interfaces scoffed and said "see. I told you." And we all said "yup" - we knew something would happen one day, but that was a worst-case-scenario that few thought was even a remote possibility.

And nobody learned their lesson and they all piled over to the next centralized system that offered "FREE!".

And so it goes.

I mean, we got ~15 years of great service out of them for free. I used to pay for my own servers in colo for all the stuff Github has been providing for free all that time. It'll suck to move, but I've done it before. It's hard to turn down the loss leader they want to give me, when it's a really good product. Now that it's stopped being a really good product, maybe it becomes easier to turn down, I dunno.

Promotional pricing? Are they saying that after the promotion, it will cost more than 7.5x??

Hmm, maybe they're discouraging copilot+Claude through pricing, nudging people to anthropic suite of tools. That sucks. I've been super happy with copilot+opus/sonnet.

Yup

Well fuck that then