rust-sciter
project-error-handling
rust-sciter | project-error-handling | |
---|---|---|
6 | 10 | |
794 | 263 | |
0.0% | 0.0% | |
0.0 | 0.0 | |
almost 2 years ago | about 2 years ago | |
Rust | ||
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rust-sciter
- Hey Rustaceans! Got a question? Ask here (16/2023)!
- Rust 1.64 Became 10-20% Faster On Windows
-
Azure CTO: βIt's time to halt starting any new projects in C/C++ β
Most GUI apps don't need what Qt provides though. They mostly need stability and cross-platform support, so ... they should start with something like Tauri or Sciter, and if there is something they need natively they will be in a much better situation to pick their poison.
https://github.com/tauri-apps/tauri uses OS provided WebView
https://github.com/sciter-sdk/rust-sciter uses Sciter
-
Do you think the Rust is production ready for GUI in 2021?
I seriously advise against using rust-sciter. It uses a lot of unsafe code, some of which is invalid and directly causes Undefined Behavior; see for example issue #114. rust-sciter's author doesn't seem to have any interest in fixing those. Besides, the code is highly unidomatic and looks like it's been written to resemble C++ β this is in itself not wrong, but always a red flag.
-
Any stable crate to develop a cross-platform Rust desktop app?
I use https://github.com/sciter-sdk/rust-sciter in my project https://github.com/rustdesk/rustdesk
project-error-handling
-
Hey Rustaceans! Got a question? Ask here (16/2023)!
This actually is an example of where the compiler errors could (or should have) maybe provided more help or even the potential solution, it might be worth submitting this to the error handling group.
-
A guide to error handling in Rust
If anyone's interested in helping to shape the future of Rust's built-in error-handling story, there's an error handling project group that's been doing great work recently, e.g. the major effort to move the Error trait into libcore ( https://github.com/rust-lang/project-error-handling/issues/3 ) and stabilizing std::backtrace. You can follow along or get involved via the #project-error-handling channel on the Rust zulip: https://rust-lang.zulipchat.com/
-
Update on the effort to move the Error trait into core
Getting it into alloc would enable usage in a LOT more contexts, like WASM and kernel code. Does this need a distinct tracking issue outside the ticket for moving it to core or would that just add more administrata?
-
What do you NOT like about Rust?
without trolling https://github.com/rust-lang/project-error-handling exist and is far from having strong conclusion and anyway I will always favor enum Error anyway however I like the idea to have a opaque box in the enum for "this is a opaque error you can't deal with as a user of my api"
-
Possible ergonomic option for error handling: what features are needed for this to work?
IIRC, the Error Handling Project Group is aware of these ideas. If this kind of thing interests you and you want to contribute, you should look into getting involved with that group.
-
Rust: Enums to Wrap Multiple Errors
> you should have the underlying message of the std::io::Error
This is a point of debate[1] among the error-handling working group.
[1]: https://github.com/rust-lang/project-error-handling/issues/4...
-
Ergonomic error handling with Rust
Focusing on good error messages has permeated throughout the community. There's even the Error Handling Project Group if you weren't convinced how committed the language designers are to getting this right. There are a number of techniques we can use to make our errors more informative. Along the way, we will discuss the crates that can help.
-
A Small Rust 2021 Change Return Display From Main
The Error Handling Working Group is looking at potential breaking changes for embedded users. Maybe you could work within that group?
What are some alternatives?
SvelteKit - web development, streamlined
serenity - A Rust library for the Discord API.
Cursive - A Text User Interface library for the Rust programming language
PyO3 - Rust bindings for the Python interpreter
libui-rs - Rust bindings to the minimalist, native, cross-platform UI toolkit `libui`
eyre - A trait object based error handling type for easy idiomatic error handling and reporting in Rust applications
rustdesk - An open-source remote desktop, and alternative to TeamViewer.
goformat - Alternative to gofmt with configurable formatting style (indentation etc.)
Native Windows GUI - A light windows GUI toolkit for rust
rust-cpython - Rust <-> Python bindings
egui - egui: an easy-to-use immediate mode GUI in Rust that runs on both web and native
cargo-leptos - Build tool for Leptos (Rust)