Ah, my bank. They're actually kind of bad all round and I am going to switch to something actually modern eventually but you know, switching banks is not something you do casually
Third, many of them are maintained by people with vested interests - for example they're an "awesome list of marketing automation tools" and the author is the owner of one such tool.
Ironically enough I just started an "Encylopedia of AI" project, and I've decided to generate all of the content with DeepSeek, with me being an editor/reviewer. I'm not really doing it for anyone except myself but I'm quite enjoying it so far. https://enkuklios.com/
Honestly it's time to get rid of C as a language used where security is a factor. Enough already. Why the hell is a lib like brotli that processes public general internet traffic, and maintained by google, not in rust?
Security is a factor everywhere. And C is everywhere. There's not going to be a "rewrite everything in Rust" project until after there is some legit penalty for selling / offering software in C that could be more secure in another language.
I think Mozilla got it right when they abandoned the effort to rewrite the entire browser in Rust and instead focused on analysis of which modules needed priority rewrites. If a module has historically had zero memory-related bugs, then there are other higher priority things to spend time on.
That said, Google Project Zero should have had Brotli on their radar. Hopefully they still have people and resources.
I’ll point out that Servo was always a research project — any thought of it replacing Gecko was an incredibly long-term stretch goal. It was _a lot_ more interested in “can we write a high-performance browser engine in Rust” (there’s a reason why it significantly predates Rust 1.0 — they were very much developed together!) and “can we implement parallelism in places where browsers historically have not” (because you have more guarantees of safety).
Chromium _has_ been replacing certain components with ones in safe languages, and it seems like that will continue slowly (with integrating them into the existing codebase, with web compatibility risk of any changes in behaviour, with the risk of performance and power regressions).
Sorry, I find the supply chain risks of Rust much more worrying than these memory safety issues. So how about we get rid of Rust? At least cargo is a problem.
Not really - gridification of swing usually defines a certain amount of swing and then gridifies to that exact amount - whether it's a pure triplet swing, something heavier, or lighter.
reply