HN user

grahamjameson

49 karma
Posts0
Comments18
View on HN
No posts found.

I hear this quite frequently and I’d have to disagree. While it’s certainly hard to complain about getting paid to ride the bench (I’ve been there myself), garden leave inhibits one’s freedom to work on what they find interesting. Not to mention missing out on bonus.

I find your comment overly optimistic. Review processes are already highly automated and effective, but even as they advance there will always (short of AGI) be (1) effective tricks to mask behavior from analysis and (2) a need for a human in the loop to verify findings.

I do agree that we need to continue to apply pressure to tear down walls around the garden as a means of protecting code as speech, including the ability to distribute and run it on our devices without burden.

Sex, sex-adjacent activities, extreme sports, van life / nomadic lifestyle are examples for which I know people who have either lost a job or experienced retaliation in a professional environment.

They are also all experiencing pressure to be criminalized and in certain places are already criminalized or otherwise regulated in a way that is harmful to individual liberty for a perceived gain in safety.

Lastly, I’ll add that cost of insurance, general ability to be insured, and the litigious nature of the USA apply a great deal of pressure to limit our ability to enrich our lives with risk.

Risk is an important ingredient to a fulfilling life. As we continue to de-risk our lives, we lose our ability to evaluate risk and aggressively criminalize what we do not understand because we perceive it to be dangerous.

There are many types of activities which, while not criminalized yet, are “anti-social” in certain environments and can cost you your job.

Perhaps a middle-of-the-road approach would be to use inline C like LuaJIT's FFI does? For instance:

  new_clib("/system/lib64/liblog.so", "log")
  ffi.cdef[[int __android_log_print(int priority, const char *tag, const char *msg);]]
  ffi.log.__android_log_print(5, "TEST_TAG", "Hello from FFI")
I can't say I'm familiar with Bun, but I've used a similar syntax to the example you provided of the current Bun syntax when working with Frida (https://frida.re). I agree it leaves something to be desired and indeed it would be cool if Aro could do this in the future.