emi2k01

If it's not a problem, then I would say it's rude for potential users and bad practice for developers.

The README transfers almost 100mb. If I'm on my phone with no wifi and I see an interesting repo as I'm a neovim user, I will just lose 100mb from my data plan with no warning. One doesn't expect that when visiting the README of a code repository.

Then what happens when they change something that makes the gifs obsolete? Will they add a commit with updated gifs that doubles the size of the repository? Most developers use

  git clone $URL

which copies the entire repo history, instead of using `--depth 1`. So now if someone wants to contribute a small change, they have to download hundreds of MBs of gifs.

I had to re-read it multiple times and I'm still not sure.

I think he's trying to say that programmers make more comprehensive tools for other engineering fields than the ones they use.

There's an interesting comment in that video that says the bird thinks it's an egg and it's trying to break it open.

I don't know if that's true but I wanted to point it out to hopefully get some answers here.

Then people found out how to embed images and it was suddenly ruined by porn :(

Reading `man env` in Linux shows that you can use:

  #!/usr/bin/env -S python $ARGS

For example:

  #!/usr/bin/env -S python -i
  
  print("Entering interactive mode...")

I'm not sure if it works in other OS.

It also prevents borrowing `inp` or `inp.phrase` as mutable which makes it useless for most cases.

Search is disabled for forked repositories in github. It's better to create a new repo and push the code if you want a fork.

Search in original repo works: https://github.com/mozilla/send/search?l=javascript

Around 3.5 of those pages are unsafe uses for implementing the same trait for garbage collection. The implementations seem very simple and the documentation mentions invariants that are easy to hold so it should be easy to recognize an unsound implementation. I think that it should be possible to not use unsafe at all for some of those but I only skimmed over the code so I'm not sure.

Most of the rest of unsafe uses are to skip rust checks that have already been asserted and for FFI which is unavoidable.

There are only a few unsafe uses whose invariants are not well defined. I only gave it a quick look but I doubt they're risky.

Even if an attacker manages to exploit ruffle, I wonder what could they do in a WASM sandbox in an isolated domain.