darkreader VS rust

change to light mode, and try out https://darkreader.org/

I was able to reproduce and reported this to Dark Reader https://github.com/darkreader/darkreader/issues/11952

I highly recommend utilizing a dark reader.

I totally forgot about the atrocious default HN theme. Yeah that's unreasonable, unreadable. A low-contrast light theme is literally equivalent to shining a flashlight in your eyes. Only unreasonable people do that to others (e.g. the police).

If you use Firefox, I recommend the Dark Reader[1] extension for taking care of all the websites that insist on destroying your eyes.

[1]: https://darkreader.org

i use https://darkreader.org/ for chrome and don't see flies 99% of the time

- very efficient to navigate(shortcuts, quick tab navigation, etc.) - Shortcuts - Terminal for easy to type commands - Tab Management - Quick Tab Navigation - Search Bar Integration - Bookmark Management - History Management - Smart Address Bar - Speed Dial - Back and forward Navigation - WM like behaviour for tabs - Floating search bar for quick searches - Powerful autocomplete in address bar(stored in-browser to avoid privacy issues) - privacy focus - Use of Duck Duck Go when privacy-focus is on - Built in Powerful Adblocker - Avoids the use of trackers - Possibility to block Trackers - Possibility to search with TOR - Option to enable or disable JS fully - Option to Disable Cookies - Encrypted DNS - Auto HTTPS upgrade - DNT(Do Not Track) by default - Adoption of G-Hacks - Built in Temp-mail for not frequently visited addresses - A slider for the amount of privacy-conviniency - Whilst doing so it selects and unselects some packages - History as a Module - Don't log certain websites to History - Creation of fake entries on History - Delete History tabs easily - By name - By category - open source - decentralized - compatible all OS - consumes low resources - minimalist - highly customizable - Dark Mode by Default - Characteristics of [Dark Reader](https://darkreader.org/) - Predefined Themes - Community Themes - Support for Wallpapers - Also the ability to configure it via .config files that can be edite - Ability to make the tabs semitransparent and either show the background or a custom wallpaper - fast - Modules - Written in almighty RUST - light - easy to use - Unbloated - Modern UI - advanced users characteristics -The option to cache websites so you can access them when you don't have internet connection, they would be stored locally (might not work on all websites) -Reader Mode: Selects only the text and offers the ability to speed read(maybe through the integration of Swift read) - Vertical Tabs Option - Using commands for faster navigation - Ability to open multiple tabs at once using a shortcut - Workspace Switching - Heavy Local Focus - Modular - Rename Downloads to something meaningful - Download folder differentiation

> There are online Rust compilers and interpreters already if you just want to rapid prototype and develop ideas in Rust

You are responding to one of the key developers of Rust early on[1], who's been working with the language for 14 years at that point.

[1] https://github.com/rust-lang/rust/graphs/contributors?from=2... and he's still #16 in commits overall today, despite almost no activity on the rust compiler since 2014.

If you haven't dipped your touch-typing fingers into Rust yet, you really owe it to yourself. Rust is a modern programming language with features that make it suitable not only for systems programming -- its original purpose, but just about any other environment, too; there are frameworks that let your build web services, web applications including user interfaces, software for embedded devices, machine learning solutions, and of course, command-line tools. Since a custom GitHub Action is essentially a command-line tool that interacts with the system through files and environment variables, Rust is perfectly suited for that as well.

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.