websurfx VS rust-analyzer

GitHub release: https://github.com/neon-mmd/websurfx/releases/tag/v1.0.0

Sorry for being late to reach you out. Thanks for trying out Websurfx, but I can help you out in setting up Websurfx. Just a raise an issue here, or you can ask for help here at our discord, we would be glad in helping you out :).

Recently we decided to do error-handling and provide custom error-messages for the errors related to each engine code present under src/engines folder in one of my project websurfx when using error-stack and we wanted to use enums for it and we found that the error-stack project provides no guide, tutorial or example but thanks to one of our maintainers @xffxff, @xffxff provided a really cool solution to this problem and which helped me learn a lot so I decided to share with you all on what I learned from it in this post and how you can wrap errors with enums when using error-stack so stick till the end of the post.

Also, you can check out the docs for steps on how to do docker deployment. I have covered it over there in great depth.

git clone https://github.com/neon-mmd/websurfx.git

Before you look into the code, I would like to explain in brief what the code below does. The code below a function which builds a new random user-agent from the provided browsers and returns it as a string but it is too slow it takes 10 seconds to build and even with caching option enabled it takes around 5-7 seconds but I want to reduce the time it takes by as much as possible. Please provide me with some suggestions or code on how to improve this down in the comments or here in this issue I have opened in my project.

If you'd like to join the WebSurfx team and help shape the future of a privacy-centric search engine, please check out our project on GitHub: WebSurfx GitHub. Feel free to explore the code, open issues, or submit pull requests. Don't hesitate to introduce yourself and share your ideas!

go build 3.62s user 0.76s system 171% cpu 2.545 total

I was looking forward to parallel front-end[4], but I have not seen any improvement for these small changes.

[1]: https://github.com/rust-lang/rust-analyzer

For example, intelephense can show diagnostics in real time, there is no need to save the file to get new diagnostics. But rust-analyzer, the language server for rust, can only update diagnostics after saving the file.

6. Rust Analyzer

The rust-analyzer readme suggests you go here for support request. But even there, you'll need to provide more details to get useful help.

For example: https://github.com/rust-lang/rust-analyzer/blob/master/docs/...

> If you create an LSP, it will work best in VS Code.

Any editor can work just as well as (or even better than) VS Code.

So, apparently the reason why rust-analyzer, the LSP server for Rust does not have persistent caching is because it would make "optimizing initial passes less important".

All I want to know is: Will it have a build configuration pulldown?

I am not a Rust dev. It surely looks great.

However, from what I understand it seems to supply just a parser separate from the Rust compiler (https://github.com/rust-lang/rust-analyzer/tree/master/crate...) trying to keep up with Rust‘s development. So, in principle, it could have been just another treesitter parser plugin, too.

So, again, the LSP framework does not directly provide any magical benefit over a static parsing framework. All the semantic analysis capabilities stem from a good parser.

rust-analyzer > manual > helix > binary > rustup component add rust-analyzer