Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
i'm using https://github.com/awslabs/aws-sdk-rust heavily and was wondering if there was a more specific community (subreddit, Discord server, etc) of Rust x AWS developers?
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.
Invisible imports (e.g. traits). In Python, everything is fully namespaced (unless you from import * in which case all bets are off). It's always explicit where a name is coming from. C is the opposite: #include lets you refer to anything defined in the headers with no namespacing. That's why a common strategy (include what you use) has an associated code style: after every non-std #include you have a comment saying which of its definitions you are using. Of course, Rust is much less implicit, but I still sometimes struggle with traits. For example, you can use tokio::net::TcpStream, but you need to also use tokio::io::AsyncReadExt for the .read trait to be defined on TcpStream. This makes it hard (for me) to answer questions like "what traits are currently available in this scope?" and "why is this module being imported?"
Dev deps can't be optional https://github.com/rust-lang/cargo/issues/1596.
I've been working on krnl which uses it.
Leptos is a SolidJS-like framework with excellent performance. It has a great server-side story as well with server-side rendering & client-side hydration as well as what they call "server functions"; essentially define a function server-side and it can be called client-side without having to deal with http and API design. Also great tooling story with cargo-leptos, leptosfmt (as well as leptos-language-server)
There are others, like Sycamore, similar story as Leptos but imo Leptos is (currently) more ergonomic.
Leptos is a SolidJS-like framework with excellent performance. It has a great server-side story as well with server-side rendering & client-side hydration as well as what they call "server functions"; essentially define a function server-side and it can be called client-side without having to deal with http and API design. Also great tooling story with cargo-leptos, leptosfmt (as well as leptos-language-server)
Leptos is a SolidJS-like framework with excellent performance. It has a great server-side story as well with server-side rendering & client-side hydration as well as what they call "server functions"; essentially define a function server-side and it can be called client-side without having to deal with http and API design. Also great tooling story with cargo-leptos, leptosfmt (as well as leptos-language-server)
Dioxus is a React-like framework, also with excellent performance. It has great platform support on web, desktop, mobile and TUI. Also has server-side rendering & client-side hydration, but also "LiveView" similar to Phoenix LiveView (Elixir) or Laravel LiveWire (PHP). Tooling is very good, just like with Leptos.
Leptos is a SolidJS-like framework with excellent performance. It has a great server-side story as well with server-side rendering & client-side hydration as well as what they call "server functions"; essentially define a function server-side and it can be called client-side without having to deal with http and API design. Also great tooling story with cargo-leptos, leptosfmt (as well as leptos-language-server)
There is also [Vulkano](https://github.com/vulkano-rs/vulkano). It has a safe high level api and lower level layers, all the way down to [ash](https://github.com/ash-rs/ash) which is more or less raw vulkan. It's more explicit and verbose than [wgpu](https://github.com/gfx-rs/wgpu) though, so maybe try wgpu first and see how you like it.
There is also [Vulkano](https://github.com/vulkano-rs/vulkano). It has a safe high level api and lower level layers, all the way down to [ash](https://github.com/ash-rs/ash) which is more or less raw vulkan. It's more explicit and verbose than [wgpu](https://github.com/gfx-rs/wgpu) though, so maybe try wgpu first and see how you like it.
There is also [Vulkano](https://github.com/vulkano-rs/vulkano). It has a safe high level api and lower level layers, all the way down to [ash](https://github.com/ash-rs/ash) which is more or less raw vulkan. It's more explicit and verbose than [wgpu](https://github.com/gfx-rs/wgpu) though, so maybe try wgpu first and see how you like it.