doc VS MSRC-Security-Research

* list of list literals (1,2; 3,4) eqv ((1,2), (3,4));

to paraphrase Larry Walk “everyone wants the [semi] colon”

https://docs.raku.org/

amen to this … i recommend thinking about your problem in terms of effective data structures and then apply even a very simple DSL to handle access and transformations … fwiw the built in Grammars and Slang support in raku https://docs.raku.org are fantastic tools for this job.

When I was looking at the language, I didn't find the documentation "really poor". In fact I was impressed at how much of a one-stop-shop the official docs site was for both conceptual docs and API docs.

https://docs.raku.org/

The Raku Programming Language documentation already contains most (if not all) the documentation you need to deal with the issues you will confront in migrating Perl code to Raku. But, as documentation goes, the focus is on the factual differences. These blogs will try to go a little more in-depth about specific issues and provide a little more hands-on information based on my experience porting quite a lot of Perl code to Raku.

I will start working on the new version of Pod as a branch in https://github.com/raku/doc.

Well, performance has been improved by several orders of magnitude since the first release. So maybe it's time to look at https://raku.org again (or first have a look at its new documentation site https://docs.raku.org)

go to https://docs.raku.org/ and type "IO" into the search field. Behold the list that appears. Check out IO::Path or IO::Handle or whatever looks interesting. Maybe it's just me but I go "Ooh, look at all the things!".

Related: The Raku documentation does an excellent job explaining hashes/dictrionaries/associative arrays. If you've any issues, please submit a Github issue.

Raku has a lot of syntax. My first attempt at learning the language failed because I couldn't get past all the strange syntax I saw at https://docs.raku.org/. Sometimes I didn't know what the syntax was called, so I didn't know what to search for.

In the course of figuring this out, I realized that our docs also (slightly) misstate what \d means in a Regex, which led to this PR. So thanks for bringing all this up!

You’ll find more primary sources across different organizations that all arrive at the 60 - 70% number. But what really grinds my gears here is that you take a piece from the article you’re criticizing and pretend that it’s a quote from Matt Miller.

It’s actually quite easy to find a primary source here because the slides from the talk that the article is based on are available: https://github.com/microsoft/MSRC-Security-Research/blob/mas...

To quote from those slides: „~70% of the vulnerabilities addressed through a security update each year continue to be memory safety issues“.

> It's still bizarre though that Rust is capturing such ridiculous mindshare.

I don't think it's that bizarre. The two big headline features that bring Rust such popularity are: #1 "70% of bugs are memory-safety bugs" [1] and Rust can help solve those, and #2 C/C++ have a couple of package manager solutions - none of which have critical mass and Rust "comes with" cargo.

Those two make me really eager to continue experimenting with Rust.

> It seems to be a temporary low-level programming zeitgeist driven by YouTube and Reddit recommendation algorithms to an audience that has never done it and probably never will.

This is some weird gatekeep-y kinda thing. Most of us didn't start out with low-level programming. Wouldn't it have been odd and frustrating for someone to tell your younger self that you have "never written C and probably never will"?

[1] https://github.com/microsoft/MSRC-Security-Research

https://github.com/microsoft/MSRC-Security-Research/blob/mas...

Windows is likely a big task for the same reasons as SMAP (https://github.com/microsoft/MSRC-Security-Research/blob/mas...). XNU should be comparable to FreeBSD, which CheriBSD is a fork of, as both use Mach's VM for memory management and have a bunch of shared code in various places, but userspace is more of an unknown quite how much effort it'd be (you'll need to port Objective-C and, now, Swift, for example). For Chromium we have ported WebKit, so I'd imagine Blink isn't too dissimilar. V8 is likely interesting, though we have a version of WebKit's JSC JIT for Morello, which gives confidence in V8 being doable.

A related post from Google Security Blog[0]:

> "A recent study[1] found that "~70% of the vulnerabilities addressed through a security update each year continue to be memory safety issues.” Another analysis on security issues in the ubiquitous `curl` command line tool showed that 53 out of 95 bugs would have been completely prevented by using a memory-safe language. [...]"

[0]: https://security.googleblog.com/2021/02/mitigating-memory-sa...

[1]: https://github.com/Microsoft/MSRC-Security-Research/blob/mas...

Here is some of the internal advocacy going on at Microsoft.

- Managed languages if you can afford a GC

- Rust

- C++ with Core Guidelines

https://github.com/microsoft/MSRC-Security-Research/tree/mas...

Note that there are still some teams like Azure Sphere and Azure RTOS, which are only providing C based SDKs, so no everyone is on the same wave length.