perseus VS rust

The best part is that it doesn’t use a virtual DOM for its reactivity, which can lead to a significant increase in performance.  Perseus not only inherits some of the best aspects of existing web frameworks but also strives to surpass them. Perseus went stable on April 9, 2023 after one year of beta development -- this is just the beginning!

I actually made a small sample project some weeks ago using Axum + Perseus + Sycamore. The purpose was to show, that also unocss was possible instead of tailwindcss. But I recommend tailwindcss for now, because there is an easy to use Perseus Plugin for it. https://gitlab.com/kibsi-perseus-examples/perseus-sycamore-rest-example-unocss But it could maybe be of interest to you. There are also the official Perseus examples: https://github.com/framesurge/perseus/tree/main/examples/core

Perseus is a web development framework for the Rust programming language. https://framesurge.sh/perseus/en-US/

Perseus is a pure Rust web development framework with support for static site generation, server-side rendering, client-side rendering, reactive state, internationalization, capsules (sometimes called an 'islands architecture'), seamless deployment, custom API routes, and so much more! And, after a year of beta versions, v0.4.0 of it just went stable!

Personally, I would go for Perseus. https://framesurge.sh/perseus/en-US

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.