TehPers

There is a book bundle on Humble Bundle right now that goes into security and hacking, if that’s what you’re interested in.

You’re unlikely to receive any support, at least publicly, for how to do anything potentially illegal. I would recommend just not doing anything illegal or unethical anyway. If you’re interested from a security perspective, find a cybersec community, and you may get more support there.

If in PHP or JS I make a change, hit F5, and get an error, that’s not any better than the IDE already showing it beforehand.

This is even worse because it can happen in prod without you ever triggering this case. For some projects, it doesn’t matter because the impact of a bug is small. For most, you put a subpar, buggy experience in front of your users, waste more time looking for the cause and debugging later with upset users, and at worst cause actual damages (depending on the project anyway).

Types aren’t unit tests. Unit tests only test a discrete set of inputs and outputs for correctness, and can miss cases that aren’t tested for.

In sound type systems, they are closer to formal verification. The compiler guarantees the properties you expect of the type hold.

As for the rest of the article, do what works best for you in your projects, but if I need to work with you, I’m going to ask for types. I need to know what types the interface expects to receive. Names are not enough. Document them, use type hints, whatever, just put them somewhere because I’m not psychic and I don’t know what you thought about when writing the function.

There’s a lot of bold claims being made. No segfaults, no memory leaks, etc. I’m curious to see how that’s implemented.

Also:

it’s safer than Rust because it lacks an “unsafe” keyword

lol