mfrw

I find content written by Eli Bendersky pretty informative: https://eli.thegreenplace.net/

Using the commute time to invest in my social-skills and spending time with family in my opinion is one of the reasons why I am now leaning towards a permanent WFH. Before the pandemic I did not know what I was missing in life -- spending quality time with family/friends.

I am one of the Volunteers -- It's mind bending to observe how everything is going on with relatively little to no chaos.

I hope I do not jinx it by saying this :)

> Cscope is built in (:cs). The kernels I work on have a make target for tags, which is also built in.

You might also like `clangd` and `scripts/clang-tools/gen_compile_commands.py` if by kernel(s) you meant the linux kernel. It's pretty neat!

I wish more places adopt this culture.

An interesting paradox that I am thinking is, how can one give this information to people in Kazakhstan, given they do not have access to Internet in the first place :(

Thank you :)

I was starting to wonder if I am missing anything trivial.

I tried to take it for a spin using `make LLVM=1 -j$(nproc)`, but, it seems it only compiles for GCC. Has anyone compiled it using `LLVM=1` ?

This is going to the brave souls who were on call the week this happened! I am not sure if they can block me on firms internal chats :)

Jokes apart, a big kudos to those who were on call :)

As person who uses both Rust & Go at my $DAYJOB, I would say, both have their merits and demerits, I think, we should view them as tools instead of attaching ourselves to any particular language emotionally. I like to think them as different tools for different use-cases. Use the right tool for the right job. In my opinion, go does an excellent job at networking (TLS/HTTP) & quick cli apps while rust shreds text & does an amazing job at memory management (this is a figurative example; don't drone me if I missed your favorite feature).

It remains to bee seen, meanwhile Rob Pike did comment[0], we should refrain from changing libraries in 1.18 immediately after generics are in.

"The reason is simple and compelling: It's too much to do all at once, and we might get it wrong."

[0]: https://github.com/golang/go/issues/48918

A quick[0] 13min video on generics by Ian Lance Taylor.

[0]: https://www.youtube.com/watch?v=nr8EpUO9jhw

> Kendo doesn't have belts like most other martial arts, the principle being that seeing the color of someone's belt causes you to prejudge their ability.

TIL: This is a really interesting perspective; Thank You for this! I will use it from now to calm myself down. I, always either got mortified by the extreme skill of my juniors or by the incompetence of seniors — not sure if it’s the case with me or is it a general feeling.

The Kendo way at-least makes me ignore the titles :)

I completely agree. My choice of words was not not right.

I did not mean that the RCE of log4j is a memory safety issue, its just that, I would prefer to choose something where the probability of me having to wake up at the middle of the night and fix is less. Honestly, I would care less if it were memory safety or whatever, given I had to wake up at midnight :)

I am not among the ones who would blindly say 'rewrite it in rust', but given what happened with log4j, I would much rather choose a safe implementation given the memory safety provided by rust.

This also does not mean rust might not have its fair share of bugs; IMHO the probability is a little less.

Edit: I mentioned the log4j RCE as it was new & do not mean to imply that it would not have happened if we had a rust implementation. As the comments have mentioned, it would be the same in any language IMO

:( Apologies and corrected. Thank you!

Simon is genuinely one of the many folks that are represented by this xkcd [0] aptly. Thank You & and a huge shoutout to you and your software that a lot of us use day-in & day-out.

[0]: https://xkcd.com/2347/

This sandboxing is achieved via RLBox[0], which is a toolkit for sandboxing third-party libraries. It comprises of a WASM sandbox and an API which existing application can leverage. The research paper[1].

[0]: https://plsyssec.github.io/rlbox_sandboxing_api/sphinx/

[1]: https://arxiv.org/abs/2003.00572

>> Phrack! We're back! It was only five years ago that issue 0x45 was released.

I am no expert; but I would never bet my money that justice will be served :(

Aptly put by the author: See you in court @Apple

https://twitter.com/keleftheriou/status/1437845736951992321

> Reflections on Trusting Trust – Ken Thompson

I wish Ken writes more papers & documents.

Link to the full paper on arxiv: https://arxiv.org/abs/2103.02515

Apologies for a dupe [did not see that]

Thank you for this compilation. I think the demos are a cherry on top; it becomes an easy sell :) Thank you :)

on a tangential note: there is a bunch of tools re-written in rust, a handy non exhaustive list [1].

[1]: https://zaiste.net/posts/shell-commands-rust/

Highlights: A new short flag, -., has been added. It is an alias for the --hidden flag, which instructs ripgrep to search hidden files and directories.

BREAKING CHANGES: Binary detection output has changed slightly.

I recently saw a tweet of a Ph.D candidate, whose professor asked her 'How good are you with Coq?', and then the prof finally realized what he had said. I think its time to change the name, it might make people uncomfortable.

Yes... Updated my comment. It was misleading :(