Sarun Rattanasiri

@catwell I was late to the party and could not quite follow. Why did you suggest that the gem should be deprecated? What changed in the built-in `Process.spawn`? What do...

Hey, thanks a bunch for the explanation; that answered most of my questions. However, from a couple of dialogs ago, it seems that GitHub didn't use the gem anymore and...

That's it, thank you. Basically, Ruby is using `vfork` natively now. I just modified and ran a benchmark of `POSIX::Spawn` on my computer using `ruby:3-slim` Docker image on an Ubuntu...

ping: @QkiZMR want to assist on this? (probably with CI, GitHub Actions, maybe)

Wow!! That's news to me. I thought anyone could distribute a classic snap package. And the fact that Snap store is close-sourced; if I don't have prior knowledge about Snap,...

Oops! my bad I can avoid the error myself by detecting `keys.empty?` in my macro. ~~~ruby resolved_value, base_path = if keys.empty? [values.data, []] else [value, path.keys] end # use resolved_value...

I know my comment will be unpopular; I braced for ☹️. But, what's wrong with installing the AWS CLI? If you don't want it on the host, you can also...

@ZanoZ I believe "token ->" came from the SDCC compiler itself. In the compilation process, the compiler will parse and "tokenize" characters into "tokens", hence the message as shown. The...

Maybe, just maybe, the compiler got confused on the "tcb" token because of ```c typedef struct tcb tcb; ``` in os_task.h

I prefer the docker-compose way and removing both gems altogether. Just my 2 cents anyway.