Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] Readme feature clarification ("localhost free") #10510

Closed
ConnorKrammer opened this issue Aug 7, 2024 · 4 comments
Closed

[docs] Readme feature clarification ("localhost free") #10510

ConnorKrammer opened this issue Aug 7, 2024 · 4 comments
Labels
type: documentation Need to update the API documentation

Comments

@ConnorKrammer
Copy link

ConnorKrammer commented Aug 7, 2024

I'm looking to use Tauri for my next desktop application. In the readme, under the list of features, is the following bullet point:

  • Localhost free (🔥)

The flame suggests this is a fairly notable point of differentiation, but I haven't been able to figure out what it means. I've searched through the issues on GitHub, read over the website, gone through the getting started guide, but still don't know. I actually even checked the blame to figure out when that line was added to the readme and then cross-referenced release notes from around that time, but no luck. Not to suggest that what's not obvious to me isn't obvious to everyone else, but maybe this should be phrased differently, or hyperlinked to something that explains it. I'm at a loss.

Hope this feedback is helpful.

@ConnorKrammer ConnorKrammer added the type: documentation Need to update the API documentation label Aug 7, 2024
@anatawa12
Copy link
Contributor

I think "localhost free" means tauri doesn't create http(s) server for localhost to provide contents for webview.
(some webview-based ui framework depends on localhost http(s) sever launched internally, but tauri doesnt.)
It might be more obvious to use localhost sever free but this still is not obvious so I think it's better to explain with sentence somewhere.

@FabianLars
Copy link
Member

The above is correct. Instead of relying on localhost server that expose your frontend to all other processes we use native webview apis to inject the assets right before the webview requests hit the network stack.

@ConnorKrammer
Copy link
Author

Very helpful, thank you for the replies. Definitely didn't get that from the entry in the feature list; seems worth clarifying somehow.

@cryptoquick
Copy link

I'm not sure just linking to this issue is the proper fix for this, @amrbashir

Perhaps the feature can be described as, "Uses native webview rendering"

Oh, and I guess you can keep the 🔥 emoji.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: documentation Need to update the API documentation
Projects
None yet
Development

No branches or pull requests

5 participants