tantivy VS Apache Cordova

Backend uses tantivy to index the web pages, sqlite3 to hold metadata / crawl queue

Tantivy is a very well made library and also follows alot of the best practices if you like search you'll like this: https://github.com/quickwit-inc/tantivy

tantivy - More of a search engine library than out of the box solution

Tantivy search engine.

You could try the Tantivy crate, with an n-gram tokenizer, which would split and index your text in sliding groups of n characters.

I had to look up the "tantivy" that README mentions. https://github.com/tantivy-search/tantivy. Might want to add a link to the project in your README.

We're using Rust for a domain-specific search engine. When I first learned Rust some years ago my first thought was that this language is perfect for heavy text processing. IMO, &str is that single killer feature that got me sold :) The search engine that we're building is based on https://github.com/tantivy-search/tantivy.

Well spotted. Like IPFS, there's a comment about that here: https://github.com/tantivy-search/tantivy/pull/1067#issuecomment-853139923 that points to the distributed wikipedia mirror project https://github.com/ipfs/distributed-wikipedia-mirror/issues/76

Anyone have experience with/opinions on Apache Cordova? [1]

It seems like it would solve most of the PWA issues. Although I vaguely recall reading that Apple is not too fond of apps that are basically just wrapped web views.

[1] https://cordova.apache.org/

Has anyone tried pwa builder?[2]

Thank you for any insights!

[0]https://cordova.apache.org/

A little over a decade ago, I worked on the open-source project Apache Cordova/Adobe PhoneGap, first at IBM and later at Adobe. Apache Cordova enables you to build mobile applications using HTML, CSS and JavaScript while targeting multiple platforms with one code base. In today’s technology landscape, mobile is dominated by iOS and Android. In the early 2010’s we were awash in mobile platforms from BlackBerry, Microsoft, Firefox, Tizen, etc. Targeting multiple platforms, including the web, from one codebase was a game changer for overworked development teams.

There are layers that offer access to native APIs like capacitor, cordova and nativescript. Apparently sometimes multiple of them should be used, but I didn't understand what are the differences even after reading the announcement. These seem to be frontend agnostic technologies and Capacitor is apparently the more modern choice at the moment.

To be honest, we have not only Capacitor but also Cordova which Capacitor is based on but because Capacitor is more popular, has better community, deals with some problems better, and works beautifully with Ionic Framework I will tell more in a second, I simply recommend Capacitor.

Apache Cordova is an example of this. It is also useful if you need to access native code (the camera, database, etc), or to use just as a WebView Container as an application to deploy to the Play store/ App Store

I've had a lot of success with Vue + Cordova. https://cordova.apache.org/

Ratchet, Ionic, Cordova.