go-readability VS Wails

I've had a lot of success by running HTML pages through mozilla's readability[0] tool (actually the go port of it[1]) before indexing it.

[0]: https://github.com/mozilla/readability

[1]: https://github.com/go-shiori/go-readability

https://github.com/go-shiori/go-readability https://github.com/mauidude/go-readability

I'm using https://github.com/go-shiori/go-readability -- a Go re-implementation of Mozilla's readability-js library. It does a pretty good job.

Two projects that do this with nearly identical output:

- https://github.com/eafer/rdrview

- https://github.com/go-shiori/go-readability

Pipe the filtered HTML output into your favorite textual web browser for an ideal reading experience.

This is basically the same tech stack of an app I’ve been planning to build, but deployed as a desktop application using Wails: https://github.com/wailsapp/wails

Wails 2.6k

The wails project does this when. You can check it out here https://github.com/wailsapp/wails/blob/master/v2/internal/typescriptify/typescriptify.go for inspection.

I have built Web front-ends (React or Svelte) with Go-backend. Embed in a web-view to make it a native desktop app, or get funky and give it native chrome/menus etc. [Wails](https://github.com/wailsapp/wails) is a good candidate to start if you want to cut on boiler plate.

Is that what wails is doing here? (On mobile)

In a "local" environment, where an executable can be provided to someone with the entire game contents. In this case, the game won't use WebSockets, and will instead use a Go/JS bridge (something like Wails) to connect.

Have you seen wails? https://github.com/wailsapp/wails

You should check out https://github.com/wailsapp/wails/pull/1959