After far too many hours using react, Svelte has become my favorite frontend framework. I’m seeing a lot of comments about how it stacks up in the LLM age. Prior to Opus 4.6-8 (and that era of model releases) they often struggled to get Svelte 4/5 code straight and mixed it up quite a bit.
But having used it A LOT this year for personal projects, large work initiatives, and one-off web tools. I’m happy to say all the modern llms seem to do just fine with it. They even handle the experimental features, like remote functions, very well. It’s mostly preference but I find reading Svelte code much more pleasant than React/Vue.
Svelte changed things up at every single version so that's what you get. I've been a fan/hater since v1. For me Claude still tried to write "export let" for props even if I specify Svelte 5 at times.
Yes, you're right, although there was a lot of churn in SvelteKit when it was in beta--maybe they had that in mind. Of course, it was marked as a beta, so it's hard to blame them too much. But I was using Kit heavily during that period and ended up getting frustrated by the whiplash, and then the addition of runes (which was announced in late 2023 even if it wasn't released until 2024) was what made me lose interest in Svelte. I still have some fondness for the framework though.
They explicitly mention that Svelte hasn't changed much since version 3? Svelte 5 did introduce runes but, as you say, still kept legacy code compatible.
I understand that making a game engine is often at odds with actually making a game, but does anyone know of good literature on building one from scratch? Ideally something like crafting interpreters but for an engine. It’s been on my list for quite a while.
I’m a very active climber, and record a lot of my climbs. I think at a glance there are two things that would make me hesitant to start using this. Firstly, my gym rotates sets weekly and re-recording each wall each week seems repetitive. Secondly and more importantly, I’m not sure how valuable information this would be. Maybe for outdoor problems, or system boards? It’s inarguably really cool, but I’m not sure how I’d actually incorporate into my sessions.
On route rotation, maybe the gym will be responsible for uploading the scan. My local gym uses an app to manage route. People view what route is available on a wall. It is just a label saying "red is a V4", no photos, and every month there is a leaderboard. People apparently use it. And occasionally people share their beta there.
For outdoor problems, I imagine it will be more like a map, and recording be taken with a drone. This is in contrast to the climbing magazine with plain photos of route.
I also think the usefulness decline as climbing ability increase. At the end of the day, climber just want to climb. But maybe there is some strava angle I can explore.
I feel like half of what I do on HN is talk about Kagi. I switch to Kagi in 2023, and haven't looked back. Between vim keybinds for navigating search, explicit AI opt-in, the ability to curate search (block sites, increase others), and more. It really lets me feel like I can control my search tool, and at least so far its felt like our interests are aligned, I give them money and they make sure search is as good as possible for me.
They're still ultimately scraping other engines pages to get the results though. The last time this was discussed an engineer on their team told me that they were building their own index internally, but I couldn't get any additional information about that and it doesn't appear to be in their docs.
My pushback on this idea and your previous comment in this thread is that a search engine is a service being provided to me.
I pay Kagi, they give me search results. It’s not an ecosystem. None of their competitors are all that much of an ecosystem, either.
If Kagi goes out of business tomorrow it’s really not my problem, with the exception of the prorated balance of the subscription.
The only thing that really matters is that running searches in Kagi is a better experience in Kagi than Google or Bing or DuckDuckGo or most of the rest. That’s what makes me pay for it.
I don’t really need to know how the sausage is made (except for the privacy aspect).
This. We are all too worried about the future. Like today's "I won't use Codeberg because tomorrow they could ban all repositories that contain Chinese characters." Well if that happens then you move. We all die in the end anyway.
I wouldn't be surprised to hear that this was always the plan for Kagi. Google has been rather distracted and complacent in their, former, core business. If Kagi is bootstrapping their indexing to emerge on the other end of this as the next "good" search, then good on them.
I'll continue to support them because it's a great experience.
What tier do you use for it? I would like to use Kagi, but it seems really expensive for the lower tiers. I may be overestimating how much I use search but it seems like it is pretty limiting.
I ended up quitting Kagi over that and built my own search engine for my own use. But if the comments here are correct that Kagi are trying to build their own index that replaces all the others, that would be great news. It seems lots of people still like Kagi regardless of that too.
For anyone trying to build their own, turns out SQLite can take you much further than it seems you should ever be able to. A metasearch layer fills in for everything else.
I am trying this. I noticed I only browse a subset of sites a lot. Also HN works wonders for finding links. But how do you get around all those bot measures/cloudflare nowadays? It seems only google IPs get a special pass.
Yep, discovering that you only need a subset of sites is the key. In my case, I still had my entire Firefox browsing history in its SQLite cache, so I tried to index every page I'd ever visited, and had a list of the domains I actually visit. It's the same insight Brave Search had - they used to be a metasearch engine, but they built their own index until they could serve 99% of queries directly, even though their index was vastly smaller than Google or Bing.
I struggle with indexing too. I don't do any crawling, just indexing from sitemap.xml files or URLs I add to the queue manually. Also I'm indexing from my own residential PC, not a hosted VPS. Something that helped me was Cloudflare's new crawler API. For all the sites where Cloudflare blocks you, just use their API instead:
Also for a quick index bootstrap, the Curlie database can be useful. It's the old DMOZ directory, the open Yahoo competitor, with 1.4 Million websites. A lot of the links are now very outdated, but it can be useful, and it's less than 500MB when converted to an SQLite database.
Unfortunately, that's nearly identical to the text from September 2024, with the only change being an increase in the number of external search sources:
I'm aware of their Teclis index, I used to be a paying API customer. Teclis is very small. It's primarily an index of indie blog websites (smallweb) mostly crawled via RSS feeds. That itself is a very cool idea, and a great supplemental index to have! But it isn't the kind of index that could ever replace their Brave / Yandex / SerpAPI dependencies. The Teclis API is even supplemented with results from Marginalia Search, a much larger index created by one person with less funding.
There's some technical info here on how Teclis is indexed, eg Readability.js for content extraction & Elasticsearch for the full-text indexing:
Kagi's short infoline about index distribution sounds new to me though. I would love to see a blog post from Kagi about that & where they're at with query coverage.
I’ve found the opposite. Most notably was when I joined an outage call at work. The call had been going for a few hours. They knew the issue, but didn’t have a fix. There were a dozen or two people on the call all searching for options (presumably all using Google). I went to Kagi and found an answer within a couple minutes that we ended up rolling out.
I’m just one person, and that’s just one incident, but it happened pretty early on after I switched to Kagi and had a pretty big impact on my perception of it.
I had been trying to get away from Google for many years, and with other options like DDG, I always felt I needed to go to Google for various searches, but so far I haven’t been back to Google at all in several years now.
Over the last 2 months I’ve started to hit AI limits. I don’t feel like I’m using it more than before, but my usage went from $1-2/month to $9.50… where I’m actively avoiding usage to not hit my $10 limit halfway through the month.
But having used it A LOT this year for personal projects, large work initiatives, and one-off web tools. I’m happy to say all the modern llms seem to do just fine with it. They even handle the experimental features, like remote functions, very well. It’s mostly preference but I find reading Svelte code much more pleasant than React/Vue.